Wiki

Below is the source of this page. To edit this source as well as other pages on the wiki, you must login.
===== Yocto Linux 2.2.0 Quickstart Guide for ADSP-SC594 =====
<note important>This version is under development</note>
<note important>The following instructions are for the ADSP-SC594-EZKIT development board (the EV-SC594-SOM System-on-Module (SOM) board attached to the EV-SOMCRR-EZKIT carrier board). For instructions for other processors and development boards please refer to [[resources:tools-software:linuxdsp:releaselandingpages:2.2.0|Linux for ADSP-SC5xx Processors 2.2.0 (develop)]]</note>

===== Setting Up Your Host PC =====
The build system is currently supported on host PCs running Ubuntu 20.04 LTS 64-bit.

\\
==== Installing Required Packages ====
In order to build and deploy Linux to your ADSP-SC594-EZKIT development board you will need to install the following packages on your host PC. 

<code>
$ sudo apt-get update
$ sudo apt-get install -y gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev xterm u-boot-tools openssl curl tftpd-hpa python
</code>


\\
==== Installing CrossCore Embedded Studio ====
CrossCore Embedded Studio contains OpenOCD which is used to transfer U-Boot into RAM for the first initial boot of the device.  The tools are created for 32-bit architecture and therefore requires a 32-bit libz package to run.  Download and install it.

<code>
$ wget https://download.analog.com/tools/CrossCoreEmbeddedStudio/Releases/Release_2.11.0/adi-CrossCoreEmbeddedStudio-linux-x86-2.11.0.deb
$ sudo dpkg -i ./adi-CrossCoreEmbeddedStudio-linux-x86-2.11.0.deb
$ sudo apt install lib32z1
</code>

\\
==== Configuring TFTP Service====
A TFTP server on the host is used to transfer images to the development board.
Install and configure.

<code>
$ sudo vi /etc/default/tftpd-hpa

#Replace the existing file with the following
TFTP_USERNAME="tftp"
TFTP_DIRECTORY="/tftpboot"
TFTP_ADDRESS="0.0.0.0:69"
TFTP_OPTIONS="--secure"
#End of File

$ sudo mkdir /tftpboot
$ sudo chmod 777 /tftpboot
$ sudo service tftpd-hpa restart
</code>

\\
==== Configure Minicom ====
In order to communicate with the U-Boot bootloader, a UART connection must be made between the host PC and the development board. It is recommended that you use minicom to do this. Minicom must be configured to connect to U-Boot correctly.

On the host PC open a terminal and execute the following commands:

<code>
$ sudo apt-get install -y minicom
$ sudo minicom -s

            +-----[configuration]------+
            | Filenames and paths      |
            | File transfer protocols  |
            | Serial port setup        |
            | Modem and dialing        |
            | Screen and keyboard      |
            | Save setup as dfl        |
            | Save setup as..          |
            | Exit                     |
            | Exit from Minicom        |
            +--------------------------+


# Select Serial port setup
     Set Serial Device to /dev/ttyUSB0
     Set Bps/Par/Bits to 115200 8N1
     Set Hardware Flow Control to No
     
     Close the Serial port setup option by press Esc
 Select Save setup as dfl
 Select Exit
</code>

<note>''/dev/ttyUSB0'' might not correspond to the serial port of the board on every system. You can determine which ''/dev'' entry your board uses by running ''ls -l /dev/ttyUSB*'' twice, once when the serial port of the board is plugged in, and once when it isn't.</note>

</code>

\\
==== Installing the Sources ==== 
The example is fully contained in the Analog Devices Yocto Linux github repositories.

To install the sources: 
<wrap hide>TODO: Make sure its the correct repo, branch, manifest file etc</wrap>
<code>
$ mkdir ~/gxp
$ cd ~/gxp
$ mkdir bin
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ./bin/repo
$ chmod a+x ./bin/repo
$ ./bin/repo init \
   -u https://github.com/analogdevicesinc/lnxdsp-repo-manifest.git \
   -b develop/yocto-2.2.0 \
   -m develop-yocto-2.2.0.xml
$ ./bin/repo sync
</code>

\\
===== Building the Image =====
==== Preparing the buildtool ====
Yocto requires the environment to be configured before building is possible.  A setup-environment script in the gxp folder contains all the required environment settings for your build target.
Source the setup script for your board:
<code>
$ source setup-environment -m adsp-sc594-som-ezkit
</code>

Sourcing the script will configure your build environment and create a build folder along with a local build configuration file.  See the Yocto Manual for further details.

<note important>Note that the build environment needs to be sourced once only before building.  If later working in a different terminal the setup-environment script should be sourced again.  If sourcing the setup-environment script is done without specifying the machine Yocto will reuse the previous configuration settings and retain any changes made to the files in the conf folder.</note>

\\

==== Building the example ====
You can build three different versions of the root filesystem; minimal, ramdisk and full.
To build the example images invoke bitbake from within the build directory created previously.

<code>
$ bitbake adsp-sc5xx-minimal
$ bitbake adsp-sc5xx-ramdisk
$ bitbake adsp-sc5xx-full
</code>

When the build completes you will see a warning that the ELF binary has relocations in .text. It is OK to ignore this warning

<note>Building a Linux distribution with Yocto is a significantly demanding process, both in CPU and network usage. A full build from scratch is estimated to take around 170 minutes for an 11th Gen Intel Core i5-11500T with 16 GB of RAM and a stable, fast Internet connection. This estimate can go up significantly for a poorer Internet connection or CPU resources, so set aside plenty of time for a clean build.</note>


==== Running U-Boot on the Board for the first time====

<note>It's always good practice to erase the contents of ''/tftpboot/'' before running and/or flashing a new build of U-Boot or Linux. You can do so by executing ''rm /tftpboot/*'' before proceeding</note>

Copy the U-Boot SPL and Proper elf files to the tftp directory:

<code>
$ cp tmp/deploy/images/adsp-sc594-som-ezkit/u-boot-spl-sc594-som-ezkit.elf /tftpboot/ 
$ cp tmp/deploy/images/adsp-sc594-som-ezkit/u-boot-proper-sc594-som-ezkit.elf /tftpboot/
</code>

Before installing the software on to the development board, ensure that the following cables are connected:
  * Board connected to network via ethernet cable using J13 connector.
  * Board connected to host PC using USB micro cable, connected to USB/UART port on the development board
  * Board connected to the ICE 1000 or ICE 2000 via the DEBUG port on the board
  * ICE is also connected to host PC via USB mini cable

{{:resources:tools-software:linuxdsp:docs:quickstartguide:adsp-sc594-som-ezkit.jpg?400|}}



  * On the SOMCRR-EZKIT is a set of micro switches labelled SW1.  These should all be set to the OFF position before continuing.

{{:resources:tools-software:linuxdsp:docs:quickstartguide:adsp-sc594-som-ezkit-switches.jpg?400|}}

  * The Power jumper JP1 on the EV-SC594-SOM board should be fitted so that it shorts the two pins closest to the edge.  This will enable the routing of power from the SOMCRR-EZKIT.
{{:resources:tools-software:linuxdsp:docs:quickstartguide:adsp-sc594-som-ezkit-power-selector.jpg?400|}}

  * The BOOT MODE selector on the EV-SC594-SOM board should be turned to "0".

{{:resources:tools-software:linuxdsp:docs:quickstartguide:adsp-sc594-som-ezkit-bootmode-fault.jpg?400|}}

<note>
The FAULT LED on the board will come on the first time the device is powered on.  This is due to the 
BootROM failing to find a valid image stored in QSPI.  Once the QSPI has been correctly programmed this will no longer be the case.
</note>

The console output from U-Boot and later on Linux will appear on the USB serial port configured in minicom earlier so open up minicom.
  ;''**Terminal1: minicom**''
  :<code>$ sudo minicom </code>
  
In a separate console launch OpenOCD and connect to the development board.


  ;''**Terminal2: OpenOCD**''
  :<code>
$ cd /opt/analog/cces/2.11.0/ARM/openocd/share/openocd/scripts 
$ sudo /opt/analog/cces/2.11.0/ARM/openocd/bin/openocd -f interface/<ICE>.cfg -f board/ev-sc594-som.cfg</code>
Where ''<ICE>'' should be replaced with ''ice1000'' or ''ice2000'' depending on your hardware.
When successful you should see a message similar to the console output below
<code>
Open On-Chip Debugger (Analog Devices CCES 2.11.0)  OpenOCD 0.10.0-gd1ba667 (2022-04-13-15:58)
Licensed under GNU GPL v2
Report bugs to <processor.tools.support@analog.com>
Info : only one transport option; autoselect 'jtag'
adapter speed: 5000 kHz

Info : halt and restart using CTI
adspsc59x_a55_init
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : ICE-1000 firmware version is 1.0.2
Info : clock speed 5000 kHz
Info : JTAG tap: adspsc594.adjc tap/device found: 0x0282e0cb (mfg: 0x065 (Analog Devices), part: 0x282e, ver: 0x0)
Info : JTAG tap: adspsc594.cpu enabled
Info : DAP adspsc594.cpu DPIDR indicates ADIv6 protocol is being used
Info : adspsc594.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : starting gdb server for adspsc594.cpu on 3333
Info : Listening on port 3333 for gdb connections
</code>

In a third console window launch GDB and type ''target extended-remote :3333''. This will make GDB to connect to the gdbserver on the local host using port 3333. Then, load the U-Boot SPL into RAM by typing ''load u-boot-spl-sc594-som-ezkit.elf'' and hit Ctrl+C to interrupt.
  ;''**Terminal3: GDB**''
  : <code>
$ cd /tftpboot
$ /opt/analog/cces/2.11.0/ARM/arm-none-eabi/bin/arm-none-eabi-gdb u-boot-proper-sc594-som-ezkit.elf 
...
(gdb) target extended-remote :3333
Remote debugging using :3333
0x000000000000352c in ?? ()
(gdb) load
Loading section .text, size 0x150 lma 0x96000000
Loading section .efi_runtime, size 0xfb0 lma 0x96000150
Loading section .text_rest, size 0x5ad94 lma 0x96001800
Loading section .rodata, size 0x12f1c lma 0x9605c594
Loading section .hash, size 0x18 lma 0x9606f4b8
Loading section .dtb.init.rodata, size 0xac0 lma 0x9606f4d0
Loading section .data, size 0x47e8 lma 0x9606ff90
Loading section .got, size 0x8 lma 0x96074778
Loading section .got.plt, size 0x18 lma 0x96074780
Loading section .u_boot_list, size 0x2800 lma 0x96074798
Loading section .efi_runtime_rel, size 0x1b0 lma 0x96076f98
Loading section .rela.dyn, size 0xb700 lma 0x96077148
Start address 0x96000000, load size 532800
Transfer rate: 29 KB/sec, 12685 bytes/write.
(gdb) c
Continuing.
</code>

At this point U-Boot will now be running in RAM on your target board. You should see U-Boot booting in the minicom console (Terminal 1). Press a key to interrupt the boot process before the countdown terminates:
  ;''**Terminal1: minicom**''
  :  <code>
U-Boot SPL 2020.10 (Aug 23 2022 - 13:09:23 +0000)
ADI Boot Mode: 0 (JTAG/BOOTROM)
SPL execution has completed.  Please load U-Boot Proper via JTAG

U-Boot 2020.10 (Aug 23 2022 - 13:09:23 +0000)

Model: ADI sc594-som-ezkit
       Watchdog enabled
I2C:   ready
DRAM:  224 MiB
MMC:   mmc@310C7000: 0
Loading Environment from SPIFlash...
SF: Detected is25lp512 with page size 256 Bytes, erase size 64 KiB, total 64 MiB
OK
In:    serial@0x31003000
Out:   serial@0x31003000
Err:   serial@0x31003000
Net:   eth0: eth@0x31040000
Hit any key to stop autoboot:  0
=>
</code>

\\
==== Booting the minimal image from QSPI ====
The U-Boot console is used to copy U-Boot (SPL and Proper), the minimal root filesystem image and the fitImage (which contains the kernel image and dtb file) into RAM and then write them to Flash. Copy the required files from <BUILD DIR>/tmp/deploy/images to your /tftpboot directory.

<code>
$ cp tmp/deploy/images/adsp-sc594-som-ezkit/stage1-boot.ldr /tftpboot/
$ cp tmp/deploy/images/adsp-sc594-som-ezkit/stage2-boot.ldr /tftpboot/
$ cp tmp/deploy/images/adsp-sc594-som-ezkit/fitImage /tftpboot/
$ cp tmp/deploy/images/adsp-sc594-som-ezkit/adsp-sc5xx-minimal-adsp-sc594-som-ezkit.jffs2 /tftpboot
</code>

\\
In the U-Boot console, set the IP address of the Host Linux PC that hosts the binary files on TFTP. Also, set the same address to the variable ''serverip''
  ;''**Terminal1: minicom**''
  :  
<code>
=> setenv tftpserverip <SERVERIP>
=> setenv serverip <SERVERIP>
</code> 

<note>To find the IP address of your host Linux PC you can issue the ''ip addr'' command from the shell or console.</note>

If your network **supports** DHCP, run:
<code>
=> run update_qspi_sc594
</code>

If your network **does NOT support** DHCP, in the U-Boot console configure the board IP address and remove the "run init_ethernet;" from the "update_spi_sc594" command.
<code>
=> setenv ipaddr <IPADDR>
=> edit update_spi_sc594
=> edit: <remove "run init_ethernet;" from here> sf probe ${sfdev}; sf erase 0 ${sfsize}; run update_spi_uboot; run update_spi_fit; run update_spi_rfs; sleep 3; saveenv
=> run update_qspi_sc594 
</code>
After removing "run init_ethernet;" from update_spi_sc594, issue the "run update_qspi_sc594" command as above.

<note>If flashing a board that had been previously programmed, it's good to erase the whole flash before as sometimes previous U-Boot installations might leave remnants. You can do that by typing ''=> sf probe 2:1; sf erase 0 ${sfsize}'' on the U-Boot prompt before proceeding to the following instructions</note>

You should see output similar to the following.
<code>
=> run update_qspi_sc594
PHY 0x00: OUI = 0x80028, Model = 0x23, Rev = 0x01, 100baseT, FDX
SF: Detected is25lp512 with page size 256 Bytes, erase size 64 KiB, total 64 MiB
SF: 67108864 bytes @ 0x0 Erased: OK
Speed: 1000, full duplex
Using eth@0x31040000 device
TFTP from server 10.37.33.116; our IP address is 10.37.33.113
Filename 'stage1-boot.ldr'.
Load address: 0x96000000
Loading: ######
         3.6 MiB/s
done
Bytes transferred = 79480 (13678 hex)
SF: Detected is25lp512 with page size 256 Bytes, erase size 64 KiB, total 64 MiB
device 0 offset 0x0, size 0x13678
SF: 79480 bytes @ 0x0 Written: OK
Speed: 1000, full duplex
Using eth@0x31040000 device
TFTP from server 10.37.33.116; our IP address is 10.37.33.113
Filename 'stage2-boot.ldr'.
Load address: 0x96000000
Loading: #########################################
         5.2 MiB/s
done
Bytes transferred = 592288 (909a0 hex)
SF: Detected is25lp512 with page size 256 Bytes, erase size 64 KiB, total 64 MiB
device 0 offset 0x20000, size 0x909a0
SF: 592288 bytes @ 0x20000 Written: OK
Speed: 1000, full duplex
Using eth@0x31040000 device
TFTP from server 10.37.33.116; our IP address is 10.37.33.113
Filename 'fitImage'.
Load address: 0x96000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################################################
         5.6 MiB/s
done
Bytes transferred = 14149218 (d7e662 hex)
SF: Detected is25lp512 with page size 256 Bytes, erase size 64 KiB, total 64 MiB
device 0 offset 0x160000, size 0xd7e662
SF: 14149218 bytes @ 0x160000 Written: OK
Speed: 1000, full duplex
Using eth@0x31040000 device
TFTP from server 10.37.33.116; our IP address is 10.37.33.113
Filename 'adsp-sc5xx-minimal-adsp-sc594-som-ezkit.jffs2'.
Load address: 0x96000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##############################
         5.6 MiB/s
done
Bytes transferred = 30015488 (1ca0000 hex)
SF: Detected is25lp512 with page size 256 Bytes, erase size 64 KiB, total 64 MiB
device 0 offset 0x1000000, size 0x1ca0000
SF: 30015488 bytes @ 0x1000000 Written: OK
Saving Environment to SPIFlash... Erasing SPI flash...Writing to SPI flash...done
OK
=>
</code>

The U-Boot image, root filesystem and Linux kernel are now stored in QSPI. Adjust the BOOT MODE selector to **position 1** and press the RESET button, the board should boot into Linux.

<code>
...
[  OK  ] Started Login Service.
[  OK  ] Reached target Multi-User System.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.


     @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@  @@@@@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@     @@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@        @@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@            @@@@@@@@@@@@@@@@@@@
     @@@@@@@@               @@@@@@@@@@@@@@@@
     @@@@@@@@                   @@@@@@@@@@@@
     @@@@@@@@                     @@@@@@@@@@
     @@@@@@@@                        @@@@@@@
     @@@@@@@@                     @@@@@@@@@@
     @@@@@@@@                   @@@@@@@@@@@@
     @@@@@@@@               @@@@@@@@@@@@@@@@
     @@@@@@@@            @@@@@@@@@@@@@@@@@@@
     @@@@@@@@        @@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@     @@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@  @@@@@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

        Analog Devices Yocto Distribution
                 www.analog.com
              www.yoctoproject.org

adsp-sc594-som-ezkit login: root
Password: adi
root@adsp-sc594-som-ezkit:~# 
</code>
The username is **root** and the password is **adi**.

==== Booting Linux from the USB Mass Storage ====
=== Formating USB stick ===
Frist step is to format USB stick to U-Boot supported formats. 

To format the USB stick, follow the commands below. The example code in this section assumes that the USB device is reported to be /dev/sdb. Ensure that you change these commands to use your device. 
<code>
$ sudo fdisk /dev/sdb
/* Create primary partition 1, 256M size*/
Command (m for help): n
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-3887103, default 2048): PRESS ENTER
Last sector, +sectors or +size{K,M,G} (2048-3887103, default 3887103): PRESS ENTER

/* Save partition */
Command (m for help): w
</code>

Format the USB stick to EXT4 filesystem
<code>
$ sudo mkfs.ext4 /dev/sdb1
</code>
=== Writing kernel and rootfs image to USB Mass Storage ===

<code>
$ mkdir ~/mnt
$ sudo mount -t ext4 /dev/sdb1 ~/mnt
$ sudo mkdir ~/mnt/boot
$ sudo cp tmp/deploy/images/adsp-sc594-ezkit/adsp-sc5xx-ramdisk-adsp-sc594-som-ezkit.cpio.xz.u-boot ~/mnt/boot/ramdisk.cpio.xz.u-boot
$ sudo cp tmp/deploy/images/adsp-sc594-ezkit/fitImage ~/mnt/boot/
$ sudo tar -xf tmp/deploy/images/adsp-sc594-ezkit/adsp-sc5xx-minimal-adsp-sc594-ezkit.tar.xz -C ~/mnt
$ sudo umount ~/mnt
</code>

=== Booting Linux from USB Mass Storage ===

To boot from ADSP-SC594-EZKIT run commands from u-boot

<code>
setenv usbload 'ext4load usb 0 ${initramaddr} /boot/${initramfile}; ext4load usb 0 ${loadaddr} /boot/${imagefile};'
setenv usbboot 'usb start; run usbload; run ramargs; bootm ${loadaddr} ${initramaddr};'
run usbboot
</code>

=== Booting rootfs from USB stick ===
Follow the steps to prepare USB stick in chapter above [[resources:tools-software:linuxdsp:docs:quickstartguide:quickstart_sc594_2_2_0#booting_linux_from_the_usb_stick|Yocto Linux 2.2.0 Quickstart Guide for ADSP-SC594]]. Set environment variables in U-boot

<code>
setenv usbargs 'setenv bootargs root=/dev/sda1 rw rootfstype=ext4 rootwait earlycon=adi_uart,0x31003000 console=ttySC0,115200'
setenv usbload 'ext4load usb 0 ${loadaddr} /boot/${imagefile};'
setenv usbboot 'usb start; run usbload; run usbargs; bootm ${loadaddr};'
</code>

And type to boot
<code>
run usbboot
</code>

Now the rootfs is set to your USB stick and amount of space equals of size of partition on USB stick. 

\\
==== Booting Linux Using TFTP ====
In order to boot Linux, the TFTP server should be setup as [[resources/tools-software/linuxdsp/docs/quickstartguide/quickstart_sc594#configuring_tftp_service|above]] and (for both NFS and RAM boot) a copy of the kernel image and dtb file should be copied into the **/tftpboot** directory.

<code>
$ cp tmp/deploy/images/adsp-sc594-som-ezkit/Image /tftpboot
$ cp tmp/deploy/images/adsp-sc594-som-ezkit/sc594-som-ezkit.dtb /tftpboot
</code>

\\
=== RAM Boot ===
For RAM boot a copy of the image containing the filesystem needs copied to the /tftpboot directory.
<code>
$ cp tmp/deploy/images/adsp-sc594-som-ezkit/adsp-sc5xx-ramdisk-adsp-sc594-som-ezkit.cpio.xz.u-boot /tftpboot/ramdisk.cpio.xz.u-boot
</code>

\\
=== NFS Boot ===
For NFS boot we use the Network File System which is stored in local Ubuntu Host. This is suggested when you do application development. To setup the NFS server:
<code>
$ sudo apt-get install nfs-kernel-server
$ sudo vi /etc/exports

#Add following commands
/romfs *(rw,sync,no_root_squash,no_subtree_check)

$ sudo mkdir /romfs/
$ sudo chmod 777 /romfs/
$ sudo service nfs-kernel-server start
</code>

We can verify that the NFS service is running by executing
<code>
$ sudo service nfs-kernel-server status
</code>
The output will indicate that the server is active, i.e.
<code>
● nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
    Drop-In: /run/systemd/generator/nfs-server.service.d
             └─order-with-mounts.conf
     Active: active (exited) since Tue 2022-09-06 14:38:31 BST; 3 months 14 days ago
   Main PID: 953 (code=exited, status=0/SUCCESS)
      Tasks: 0 (limit: 18797)
     Memory: 0B
     CGroup: /system.slice/nfs-server.service

Sep 06 14:38:29 $YOUR_HOSTNAME systemd[1]: Starting NFS server and services...
Sep 06 14:38:31 $YOUR_HOSTNAME systemd[1]: Finished NFS server and services.
</code>

If it's reported as inactive, wait a few moments and check the status again.

The root filesystem should then be copied to /romfs.
<code>
$ sudo tar -xf tmp/deploy/images/adsp-sc594-som-ezkit/adsp-sc5xx-full-adsp-sc594-som-ezkit.tar.xz -C /romfs
</code>

\\
=== Booting into Linux from TFTP ===
Next, on the target, from u-boot, run one of the following command:
<code>
=> run ramboot
 or
=> run nfsboot
......
......
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.


     @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@  @@@@@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@     @@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@        @@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@            @@@@@@@@@@@@@@@@@@@
     @@@@@@@@               @@@@@@@@@@@@@@@@
     @@@@@@@@                   @@@@@@@@@@@@
     @@@@@@@@                     @@@@@@@@@@
     @@@@@@@@                        @@@@@@@
     @@@@@@@@                     @@@@@@@@@@
     @@@@@@@@                   @@@@@@@@@@@@
     @@@@@@@@               @@@@@@@@@@@@@@@@
     @@@@@@@@            @@@@@@@@@@@@@@@@@@@
     @@@@@@@@        @@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@     @@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@  @@@@@@@@@@@@@@@@@@@@@@@@@@@@@
     @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

        Analog Devices Yocto Distribution
                 www.analog.com
              www.yoctoproject.org

adsp-sc594-som-ezkit login: root
Password: adi
root@adsp-sc594-som-ezkit:~# 
</code>

\\
==== Building the SDK ====
To build the SDK follow the instructions here [[:resources:tools-software:linuxdsp:docs:quickstartguide:building-the-sdk|Building the SDK]].

\\


\\
Analog Devices Wiki

Page Tools
