Target Software Installation: Difference between revisions

From ArmadeusWiki
No edit summary
No edit summary
 
(188 intermediate revisions by 17 users not shown)
Line 1: Line 1:
===Flash memory partitions===
On this page you will learn how to update (from U-Boot) the Flash's partitions of your APF module storing the Linux, rootfs and U-Boot software images.
{| cellspacing=5 cellpadding=5 border=0 width=100%
|- style="background:black; color:white; font-size:16px"
! width="66%" | Address range !! type
|- align="center"
|0x10000000 - 0x10040000 ( 256KB )
| U-Boot
|- align="center"
|0x10040000 - 0x10060000 ( 128KB )
| U-Boot environment variables
|- align="center"
|0x10060000 - 0x100A0000 ( 256KB )
| FPGA bitfile
|- align="center"
|0x100A0000 - 0x10220000 ( 1.5MB )
| Linux kernel image
|- align="center"
|0x10220000 - end of flash ( ~6MB / 8MB flash )
| Root filesystem
|}


==Configure U-Boot==
==Configure U-Boot==


There is a set of variables you can customize to your needs.
===Environment variables===
The commande '''printenv''' show you most of them and their current state.
U-Boot can be customized in a flexible way with the use of "environment variables/scripts".
Use the command '''setenv''' to change one of these variable.
The command '''printenv''' shows you most of them and their current value:
For instance:
<pre class="apf">
  setenv ipaddr 192.168.0.3
BIOS> printenv
Use the command '''saveenv''' to save the state of your environment variables in flash memory.
bootcmd=run jffsboot
 
bootdelay=20
In order to use network features with u-boot you have to set the network environment variables:
baudrate=115200
  setenv netmask=255.255.255.0 (default value should be fine in most situations)
ethaddr=
  setenv ipaddr 192.168.0.3
autoload=no
  setenv serverip=192.168.0.5 (the IP adresse of your tftp host server to download update files )
...
  setenv rootpath "/tftpboot/root" (to boot linux over nfs)
</pre>
The command '''setenv''' is used to change these variables. For example, to set the IP address (don't do it yet):
<pre class="apf">
  BIOS> setenv ipaddr 192.168.0.10
</pre>
The command '''saveenv''' is used to save the state of your environment variables in FLASH memory; that way they will be available at next boot:
<pre class="apf">
BIOS> saveenv
Saving Environment to Flash...
. done
Un-Protected 1 sectors
  Erasing Flash...
. done
Erased 1 sectors
  Writing to Flash... done
  . done
  Protected 1 sectors
</pre>


You can use the '''dhcp''' command to configure these variable from your dhcp server. Probably you will have to adjust the '''serverip''' variable manually.
===Network configuration===
{{Note| You have to install [[Communicate#TFTP_server_installation | tftpboot on your host development]] computer}}


In order to use the U-Boot's network features, you have to set the network environment variables:
<pre class="apf">
BIOS> setenv netmask 255.255.255.0                (this default value should be fine in most situations)
BIOS> setenv ipaddr 192.168.0.10
BIOS> setenv serverip 192.168.0.2                (the IP address of your tftp server/PC hosting the files to download)
BIOS> setenv rootpath "/tftpboot/apf9328-root"    (to boot Linux over NFS)
BIOS> setenv consoledev ttymxc0
</pre>
You can use the '''dhcp''' command to configure these variables from your DHCP server. You probably will have to adjust the '''serverip''' variable manually.
If you use VirtualBox or VMware make sure you have selected Bridge Mode for the network adaptor, otherwise the U-Boot cannot talk to your host.
<pre class="apf">
  BIOS> dhcp
  BIOS> dhcp
  dm9000 i/o: 0x15c00000, id: 0x90000a46
  dm9000 i/o: 0x15c00000, id: 0x90000a46
Line 42: Line 52:
  operating at 100M full duplex mode
  operating at 100M full duplex mode
  BOOTP broadcast 1
  BOOTP broadcast 1
  DHCP client bound to address 192.168.0.3
  DHCP client bound to address 192.168.0.10
  BIOS>setenv serverip=192.168.0.5
  BIOS> setenv serverip 192.168.0.2
  BIOS>saveenv
  BIOS> saveenv
</pre>
Do not forget to save your changes in FLASH, to have them available at next power up:
<pre class="apf">
BIOS> saveenv
</pre>
In case of troubles you can use the following U-Boot script to reset the variables to the "factory"/default settings:
<pre class="apf">
BIOS> run flash_reset_env
</pre>
or
<pre class="apf">
BIOS> env default -f -a; saveenv
</pre>
 
==Linux kernel installation==
 
* Check that your Armadeus kernel image size is smaller than the U-Boot partition (see [[#Flash_memory_partitions|Flash Memory Partitions]] for size allowances):
<pre class="host">
[armadeus]$ ls -al buildroot/output/images/
</pre>
* If yes, copy it to your TFTP server directory (here ''/tftpboot/''):
<pre class="host">
[armadeus]$ cp buildroot/output/images/* /tftpboot/
</pre>
===Linux kernel update script===
* This is the recommended method and the easiest one. The automatic 'update_kernel' scripts downloads the image and flash it in the same go:
<pre class="apf">
BIOS> run update_kernel
</pre>
* To know what ''update_kernel'' script is doing you can display its content:
<pre class="apf">
BIOS> printenv update_kernel
</pre>
{{Warning|If the loaded kernel image is too large, the following operation can destroy data that are stored after the partition limits (e.g. RootFS) - Check that transferred size value is less than the ones specified here [[#Flash_memory_partitions|Flash Memory Partitions]]
}}
 
===Other Linux kernel update method===
* Load kernel image with U-Boot through network:
<pre class="apf">
BIOS> run download_kernel
</pre>
or with the serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
    ''Ctrl+Altgr+\+c to access kermit command line then:''
(/home/.../) C-Kermit>send /tftpboot/XX-linux.bin
    ''After download is completed, you can type the c command to reconnect to the terminal:''
(/home/.../) C-Kermit>c
Connecting to /dev/ttyUSB0, speed 115200
  Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size      = 0x<size of XX-linux.bin> = .... Bytes
## Start Addr      = 0x08000000
BIOS> setenv filesize <size of XX-linux.bin>
</pre>
 
----
Check that transferred size value is less than the ones specified here [[#Flash_memory_partitions|Flash Memory Partitions]]
<pre class="apf">
Bytes transferred = 1313216 (1409c0 hex)
</pre>
----
 
* You can test your new kernel image without flashing it with; if so you will have to reload it again after test:
** '''Please note''': The ''bootm'' command is not supported by [[APF51]] boards yet; directly flash the kernel with the below commands instead
<pre class="apf">
BIOS> bootm
</pre>
* a U-Boot script exists to ease kernel image loading through Ethernet:
<pre class="apf">
BIOS> run download_kernel
</pre>
* After kernel image has been downloaded into RAM memory, you can flash it with:
<pre class="apf">
BIOS> run flash_kernel
</pre>
* If you only want to try a new kernel without flashing the kernel image you can launch it directly from RAM (U-Boot 2011.12):
<pre class="apf">
BIOS> setenv bootargs console=${consoledev},${baudrate} ${mtdparts};run addubifsargs addipargs; bootm
(the kernel image you want to try must have been loaded at ${loadaddr})
</pre>
* '''Please note''': The ''bootm'' command is not supported by [[APF51]] boards yet; directly flash the kernel with the below commands
 
==rootfs installation==
 
* Check that your Armadeus rootfs image size is smaller than the rootfs partition (see [[#Flash_memory_partitions|Flash Memory Partitions]] for size allowances):
<pre class="host">
$ ls -al buildroot/output/images/
...
$ cp buildroot/output/images/* /tftpboot/
</pre>
* Load rootfs image with U-Boot through network:
<pre class="apf">
BIOS> run update_rootfs
</pre>
 
* or serial line:
<pre class="apf">
BIOS> loadb ${loadaddr}
    ''Ctrl+Altgr+\+c to access kermit command line then...''
(/home/.../) C-Kermit>send path_to_your_host_buildroot_dir/XX-rootfs.ubi
    ''After download is completed, you can type the c command to reconnect to the terminal:''
(/home/.../) C-Kermit>c
Connecting to /dev/ttyUSB0, speed 115200
Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size      = 0x<size of rootfs>
## Start Addr      = 0x........
BIOS> setenv filesize <size of rootfs>
BIOS> run flash_rootfs
</pre>
 
* Now you should be ready to test Linux:
<pre class="apf">
BIOS> boot
</pre>
 
* For large rootfs (bigger than the available RAM on your system) please use the method which suit your board:
** [[APF9328]]: none :-(
** [[APF27]]/[[APF28]]/[[APF51]]:
<pre class="apf">
BIOS> nand erase.part rootfs
BIOS> tftpboot ${rootfs_addr} ${board_name}-rootfs.ubi nand
</pre>
** [[APF6]]: [[U-Boot UMS on APF6|U-Boot UMS]]
 
==Update U-Boot==
* Check that your Armadeus U-Boot image size is smaller than the u-boot partition (see [[#Flash_memory_partitions|Flash Memory Partitions]] for size allowances) and copy all the binary images to your TFTP server directory:
<pre class="host">
[armadeus]$ ls -al buildroot/output/images/
...
[armadeus]$ cp buildroot/output/images/* /tftpboot/
</pre>
 
===U-Boot update script===
* This is the recommended method and the easiest one. The automatic 'update_uboot' scripts downloads the image and flash it in the same go:
<pre class="apf">
BIOS> run update_uboot
</pre>
 
* Reset your board and check if you need to update your environment variables:
<pre class="apf">
BIOS> reset
U-Boot 2011.12 ..
...
*** Warning - Environment version change suggests: run flash_reset_env; reset
BIOS> run flash_reset_env; reset
</pre>
In such a case you may have to update your network environment variables (see [[#Configure_U-Boot|Configure U-Boot]])
===Other U-Boot update method===
You can use the following commands to download U-boot in RAM:<br>
*With Ethernet and a TFTP server:
<pre class="apf">
BIOS> run download_uboot
</pre>
*With Ethernet and a NFS server:
<pre class="apf">
BIOS> nfs ${loadaddr} host_ip_addr:/nfs_path_to_buildroot/apfXX-u-boot{.bin|-nand.bin|.sb}
</pre>
*With kermit and the serial/RS232 line
<pre class="apf">
BIOS> loadb ${loadaddr}
    <CTRL><ALT GR>\
    c
    send path_to_buildroot/apfXX-u-boot{.bin|-nand.bin|.sb}
    c<ENTER>
Connecting to /dev/ttyUSB0, speed 115200
  Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size      = 0x<size of U-Boot> = .... Bytes
## Start Addr      = 0x08000000
BIOS> setenv filesize <size of U-Boot>
</pre>
 
Then you can use the U-Boot command/script 'flash_uboot' to tranfert the new U-Boot from RAM to Flash memory:
<pre class="apf">
BIOS> run flash_uboot
</pre>
 
Advanced informations can be found at the [[BootLoader]] wiki page.
 
{{Note | '''APF51'''
 
When updating your board from a legacy version of Armadeus BSP you should set the `fdt_addr_r` environment var to boot correctly:
<pre class="apf">
BIOS> setenv fdt_addr_r 91000000
</pre>


Do not forget to save your changes in flash with '''saveenv''' to have them available at power up.
See [[How_to_use_vanilla_kernel_on_APF51]] for more informations.
}}


===Linux kernel installation===


First check your kernel size is smaller than the armadeus kernel partiiton (ex 1MB) How ??????????????????????????
==Update U-Boot, kernel and rootfs images all at once==
Load kernel image with u-boot through network:
* Copy all the binary images to your TFTP server directory:
    BIOS> tftpboot 08000000 pathtoyourhostedbuildrootdir/linux-kernel-2.6.12-arm.bin
<pre class="host">
or serial line:
[armadeus]$ cp buildroot/output/images/* /tftpboot/  
    BIOS> loadb 08000000
</pre>
    Ctrl+Altgr+c to access kermit command line then...
    send pathtoyourhostedbuildrootdir/linux-kernel-2.6.12-arm.bin
    the you can type the c command to reconnect to the terminal


Flash kernel image with:
* The automatic 'update_all' scripts downloads each image and flash it in the same go:
    BIOS> run flash_kernel
<pre class="apf">
<span style="color:red">
BIOS> run update_all
!!! WARNING!! If the new kernel is too large, this operation can destroy data that is stored behind the kernel (e.g. rootfs) !!!
</pre>
</span>
Check that Bytes transferred = 1040676 (fe124 hex) value is less than 0xfffff  ????????????????????????,


* Reset your board to check that wour board is correctly updated.


===Linux rootfs installation===
{{Note |When updating your board from a legacy version of Armadeus BSP you should update U-Boot first to update the environment variables before any other partition update ( see [[#Update_U-Boot|Update U-Boot]]) }}
Load rootfs image with u-boot through network:
    BIOS> tftpboot 08000000 pathtoyourhostedbuildrootdir/rootfs.arm_nofpu.jffs2
or serial line:
    BIOS> loadb 08000000
    Ctrl+Altgr+\+c to access kermit command line then...
    send pathtoyourhostedbuildrootdir/rootfs.arm_nofpu.jffs2
the you can type the c command to reconnect to the terminal


Flash rootfs image with:
==Flash memory partitions==
    BIOS> run flash_rootfs
* Old Flash partitionning (pre armadeus-5.0) is kept [[Talk:Target_Software_Installation|here]].
 
===APF9328 / U-Boot 2011.12 and newer release - Flash memory partitions===
{| border="1" cellpadding="5" cellspacing="0" summary="APF9328 Flash memory partitions"
|- style="background:#efefef;" align="center"
! width="60%" |Address range (index from FLASH physical @ 0x10000000) !!Type
|- align="center"
|0x000000 - 0x03FFFF ( 256KB )
|U-Boot image
|- align="center"
|0x040000 - 0x5FFFF ( 128KB )
|U-Boot environment variables (primary partition: env)
|- align="center"
|0x060000 - 0x7FFFF ( 128KB )
|U-Boot environment variables (redundant partition: env2)
|- align="center"
|0x080000 - 0xBFFFF ( 256KB )
|FPGA bitfile (firmware)
|- align="center"
|0x0C0000 - 0x2BFFFF ( 2MB )
|Linux kernel image (kernel)
|- align="center"
|0x2C0000 - End of FLASH ( ~5.5 MB or ~13.5 MB  )
|Root filesystem (rootfs)
|}
<br>


Now you should be ready to test linux:
===APF27  / U-Boot 2011.12 and newer release - Flash memory partitions===
    BIOS> boot
* It's safer to not touch sectors marked as red ;-)


===FPGA firmware installation===
{| border="1" cellpadding="5" cellspacing="0" summary="APF27 Flash memory partitions"
|- style="background:#efefef;" align="center"
! width="60%" |NAND flash address range !!Type
|- style="background:#ffcccc;" align="center"
|0x00000000 - 0x000FFFFF (1MiB, including NAND SPL and spare memory for bad blocks)
|U-Boot image
|- align="center"
|0x00100000 - 0x0017FFFF (512kB)
|U-Boot environment variables (primary partition: env)
|- align="center"
|0x00180000 - 0x001FFFFF (512kB)
|U-Boot environment variables (redundant partition: env2)
|- align="center"
|0x00200000 - 0x0027FFFF (512KB)
|FPGA bitfile (firmware)
|- align="center"
|0x00280000 - 0x002FFFFF (512kB)
|DeviceTree Block partition (dtb)
|- align="center"
|0x00300000 - 0x007FFFFF (5MB)
|Linux kernel image (kernel)
|- align="center"
|0x00800000 - 0xff7ffff (>~248MB)
|Root filesystem (rootfs)
|- style="background:#ffcccc;" align="center"
|0xff800000 - End of FLASH (512KB)
|U-Boot NAND bad blocks table. Sectors mark as bad, don't touch !!
|}
<br>


The FPGA firmwares are in the armadeus/software/firmware tree
===APF28 / U-Boot 2011.12 and newer release - Flash memory partitions===
You can make some trials with the armadeus/software/firmware/ps2/ps2_top.bin file
{| border="1" cellpadding="5" cellspacing="0" summary="APF28 Flash memory partitions"
!!! check your file size is smaller than the firmware partition size (AKA 256KB)
|- style="background:#efefef;" align="center"
! width="60%" |NAND flash address range !!Type
|- align="center"
|0x00000000 - 0x002FFFFF (3MB, including NAND SPL and spare memory for bad blocks)
|U-Boot
|- align="center"
|0x00300000 - 0x0037FFFF (512kB)
|U-Boot environment variables (primary partition: env)
|- align="center"
|0x00380000 - 0x003FFFFF (512kB)
|U-Boot environment variables (redundant partition: env2)
|- align="center"
|0x00400000 - 0x0047FFFF (512kB)
|DeviceTree Block partition (dtb)
|- align="center"
|0x00480000 - 0x004FFFFF (512kB)
|Reserved for a futur splash screen (splash)
|- align="center"
|0x00500000 - 0x00CFFFFF (8MB)
|Linux kernel image (kernel)
|- align="center"
|0x00D00000 - End of FLASH (>~243MB)
|Root filesystem (rootfs)
|}
<br>


Load FPGA firmware image file with u-boot through network:
===APF51 / U-Boot 2011.12 and newer release - Flash memory partitions===
    BIOS> tftpboot 08000000 pathtoyourhostedfirmwaredir/fpgafirmware.bin
{| border="1" cellpadding="5" cellspacing="0" summary="APF51 Flash memory partitions"
or serial line:
|- style="background:#efefef;" align="center"
    BIOS> loadb 08000000
!  width="60%" |NAND flash address range !!Type
    Ctrl+Altgr+\+c to access kermit command line then...
|- align="center"
    C-Kermit> send pathtoyourhostedfirmwaredir/fpgafirmware.bin
|0x00000000 - 0x000FFFFF (1MB, including NAND SPL and spare memory for bad blocks)
then you can type the c command to reconnect to the terminal
| U-Boot image
|- align="center"
|0x00100000 - 0x0017FFFF (512kB)
|U-Boot environment variables (primary partition: env)
|- align="center"
|0x00180000 - 0x001FFFFF (512kB)
|U-Boot environment variables (redundant partition: env2)
|- align="center"
|0x00200000 - 0x002FFFFF (1MB)
|FPGA bitfile
|- align="center"
|0x00300000 - 0x0037FFFF (512kB)
|DeviceTree Block partition (dtb)
|- align="center"
|0x00380000 - 0x003FFFFF (512kB)
|Reserved for a futur splash screen (splash)
|- align="center"
|0x00400000 - 0x00BFFFFF (8MB)
|Linux kernel image (kernel)
|- align="center"
|0x00C00000 - End of FLASH (>~500MB)
|Root filesystem (rootfs)
|}


Flash firmware image with:
===APF6===
    BIOS> run flash_firmware
[[APF6]] has an [[eMMC]].


Test your new FPGA firmware:
===OPOS6UL===
    BIOS> fpga load 0 ${firmware_addr} ${firmware_len}
[[OPOS6UL]] has an [[EMMC OPOS6UL|eMMC]].


When your are satisfied with your firmware you can make it autoloaded at power up:
[[Category:System Update]]
    BIOS> setenv firmware_autoload 1
    BIOS> saveenv

Latest revision as of 15:12, 3 October 2025

On this page you will learn how to update (from U-Boot) the Flash's partitions of your APF module storing the Linux, rootfs and U-Boot software images.

Configure U-Boot

Environment variables

U-Boot can be customized in a flexible way with the use of "environment variables/scripts". The command printenv shows you most of them and their current value: 

 BIOS> printenv
 bootcmd=run jffsboot
 bootdelay=20
 baudrate=115200
 ethaddr=
 autoload=no
 ...

The command setenv is used to change these variables. For example, to set the IP address (don't do it yet): 

 BIOS> setenv ipaddr 192.168.0.10

The command saveenv is used to save the state of your environment variables in FLASH memory; that way they will be available at next boot: 

 BIOS> saveenv
 Saving Environment to Flash...
 . done
 Un-Protected 1 sectors
 Erasing Flash...
 . done
 Erased 1 sectors
 Writing to Flash... done
 . done
 Protected 1 sectors

Network configuration

Note Note: You have to install tftpboot on your host development computer


In order to use the U-Boot's network features, you have to set the network environment variables: 

 BIOS> setenv netmask 255.255.255.0                (this default value should be fine in most situations)
 BIOS> setenv ipaddr 192.168.0.10 
 BIOS> setenv serverip 192.168.0.2                 (the IP address of your tftp server/PC hosting the files to download)
 BIOS> setenv rootpath "/tftpboot/apf9328-root"    (to boot Linux over NFS)
 BIOS> setenv consoledev ttymxc0

You can use the dhcp command to configure these variables from your DHCP server. You probably will have to adjust the serverip variable manually. If you use VirtualBox or VMware make sure you have selected Bridge Mode for the network adaptor, otherwise the U-Boot cannot talk to your host. 

 BIOS> dhcp
 dm9000 i/o: 0x15c00000, id: 0x90000a46
 MAC: 00:0e:32:00:00:01
 operating at 100M full duplex mode
 BOOTP broadcast 1
 DHCP client bound to address 192.168.0.10
 BIOS> setenv serverip 192.168.0.2
 BIOS> saveenv

Do not forget to save your changes in FLASH, to have them available at next power up: 

 BIOS> saveenv

In case of troubles you can use the following U-Boot script to reset the variables to the "factory"/default settings: 

 BIOS> run flash_reset_env

or 

 BIOS> env default -f -a; saveenv

Linux kernel installation

  • Check that your Armadeus kernel image size is smaller than the U-Boot partition (see Flash Memory Partitions for size allowances):
 [armadeus]$ ls -al buildroot/output/images/
  • If yes, copy it to your TFTP server directory (here /tftpboot/):
 [armadeus]$ cp buildroot/output/images/* /tftpboot/

Linux kernel update script

  • This is the recommended method and the easiest one. The automatic 'update_kernel' scripts downloads the image and flash it in the same go:
 BIOS> run update_kernel
  • To know what update_kernel script is doing you can display its content:
 BIOS> printenv update_kernel
Warning Warning: If the loaded kernel image is too large, the following operation can destroy data that are stored after the partition limits (e.g. RootFS) - Check that transferred size value is less than the ones specified here Flash Memory Partitions


Other Linux kernel update method

  • Load kernel image with U-Boot through network:
 BIOS> run download_kernel

or with the serial line: 

 BIOS> loadb ${loadaddr}
     ''Ctrl+Altgr+\+c to access kermit command line then:''
 (/home/.../) C-Kermit>send /tftpboot/XX-linux.bin
     ''After download is completed, you can type the c command to reconnect to the terminal:''
 (/home/.../) C-Kermit>c
 Connecting to /dev/ttyUSB0, speed 115200
  Escape character: Ctrl-\ (ASCII 28, FS): enabled
 Type the escape character followed by C to get back,
 or followed by ? to see other options.
 ----------------------------------------------------
 ## Total Size      = 0x<size of XX-linux.bin> = .... Bytes
 ## Start Addr      = 0x08000000
 BIOS> setenv filesize <size of XX-linux.bin>

Check that transferred size value is less than the ones specified here Flash Memory Partitions 

 Bytes transferred = 1313216 (1409c0 hex)
  • You can test your new kernel image without flashing it with; if so you will have to reload it again after test:
    • Please note: The bootm command is not supported by APF51 boards yet; directly flash the kernel with the below commands instead
 BIOS> bootm
  • a U-Boot script exists to ease kernel image loading through Ethernet:
 BIOS> run download_kernel
  • After kernel image has been downloaded into RAM memory, you can flash it with:
 BIOS> run flash_kernel
  • If you only want to try a new kernel without flashing the kernel image you can launch it directly from RAM (U-Boot 2011.12):
 BIOS> setenv bootargs console=${consoledev},${baudrate} ${mtdparts};run addubifsargs addipargs; bootm
(the kernel image you want to try must have been loaded at ${loadaddr})
  • Please note: The bootm command is not supported by APF51 boards yet; directly flash the kernel with the below commands

rootfs installation

  • Check that your Armadeus rootfs image size is smaller than the rootfs partition (see Flash Memory Partitions for size allowances):
 $ ls -al buildroot/output/images/
 ...
 $ cp buildroot/output/images/* /tftpboot/
  • Load rootfs image with U-Boot through network:
 BIOS> run update_rootfs
  • or serial line:
BIOS> loadb ${loadaddr}
    ''Ctrl+Altgr+\+c to access kermit command line then...''
(/home/.../) C-Kermit>send path_to_your_host_buildroot_dir/XX-rootfs.ubi
    ''After download is completed, you can type the c command to reconnect to the terminal:''
(/home/.../) C-Kermit>c
Connecting to /dev/ttyUSB0, speed 115200
 Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size      = 0x<size of rootfs>
## Start Addr      = 0x........
BIOS> setenv filesize <size of rootfs>
BIOS> run flash_rootfs
  • Now you should be ready to test Linux:
 BIOS> boot
  • For large rootfs (bigger than the available RAM on your system) please use the method which suit your board: 
 BIOS> nand erase.part rootfs
 BIOS> tftpboot ${rootfs_addr} ${board_name}-rootfs.ubi nand

Update U-Boot

  • Check that your Armadeus U-Boot image size is smaller than the u-boot partition (see Flash Memory Partitions for size allowances) and copy all the binary images to your TFTP server directory:
 [armadeus]$ ls -al buildroot/output/images/
 ...
 [armadeus]$ cp buildroot/output/images/* /tftpboot/

U-Boot update script

  • This is the recommended method and the easiest one. The automatic 'update_uboot' scripts downloads the image and flash it in the same go:
 BIOS> run update_uboot
  • Reset your board and check if you need to update your environment variables:
 BIOS> reset
 U-Boot 2011.12 ..
 ...
 *** Warning - Environment version change suggests: run flash_reset_env; reset
 BIOS> run flash_reset_env; reset

In such a case you may have to update your network environment variables (see Configure U-Boot)

Other U-Boot update method

You can use the following commands to download U-boot in RAM:

  • With Ethernet and a TFTP server:
 BIOS> run download_uboot
  • With Ethernet and a NFS server:
 BIOS> nfs ${loadaddr} host_ip_addr:/nfs_path_to_buildroot/apfXX-u-boot{.bin|-nand.bin|.sb}
  • With kermit and the serial/RS232 line
 BIOS> loadb ${loadaddr}
    <CTRL><ALT GR>\
    c
    send path_to_buildroot/apfXX-u-boot{.bin|-nand.bin|.sb}
    c<ENTER>
 Connecting to /dev/ttyUSB0, speed 115200
  Escape character: Ctrl-\ (ASCII 28, FS): enabled
 Type the escape character followed by C to get back,
 or followed by ? to see other options.
 ----------------------------------------------------
 ## Total Size      = 0x<size of U-Boot> = .... Bytes
 ## Start Addr      = 0x08000000
 BIOS> setenv filesize <size of U-Boot>

Then you can use the U-Boot command/script 'flash_uboot' to tranfert the new U-Boot from RAM to Flash memory: 

 BIOS> run flash_uboot

Advanced informations can be found at the BootLoader wiki page.

Note Note: APF51

When updating your board from a legacy version of Armadeus BSP you should set the `fdt_addr_r` environment var to boot correctly: 

BIOS> setenv fdt_addr_r 91000000

See How_to_use_vanilla_kernel_on_APF51 for more informations.


Update U-Boot, kernel and rootfs images all at once

  • Copy all the binary images to your TFTP server directory:
 [armadeus]$ cp buildroot/output/images/* /tftpboot/
  • The automatic 'update_all' scripts downloads each image and flash it in the same go:
 BIOS> run update_all
  • Reset your board to check that wour board is correctly updated.
Note Note: When updating your board from a legacy version of Armadeus BSP you should update U-Boot first to update the environment variables before any other partition update ( see Update U-Boot)


Flash memory partitions

  • Old Flash partitionning (pre armadeus-5.0) is kept here.

APF9328 / U-Boot 2011.12 and newer release - Flash memory partitions

Address range (index from FLASH physical @ 0x10000000) Type
0x000000 - 0x03FFFF ( 256KB ) U-Boot image
0x040000 - 0x5FFFF ( 128KB ) U-Boot environment variables (primary partition: env)
0x060000 - 0x7FFFF ( 128KB ) U-Boot environment variables (redundant partition: env2)
0x080000 - 0xBFFFF ( 256KB ) FPGA bitfile (firmware)
0x0C0000 - 0x2BFFFF ( 2MB ) Linux kernel image (kernel)
0x2C0000 - End of FLASH ( ~5.5 MB or ~13.5 MB ) Root filesystem (rootfs)


APF27 / U-Boot 2011.12 and newer release - Flash memory partitions

  • It's safer to not touch sectors marked as red ;-)
NAND flash address range Type
0x00000000 - 0x000FFFFF (1MiB, including NAND SPL and spare memory for bad blocks) U-Boot image
0x00100000 - 0x0017FFFF (512kB) U-Boot environment variables (primary partition: env)
0x00180000 - 0x001FFFFF (512kB) U-Boot environment variables (redundant partition: env2)
0x00200000 - 0x0027FFFF (512KB) FPGA bitfile (firmware)
0x00280000 - 0x002FFFFF (512kB) DeviceTree Block partition (dtb)
0x00300000 - 0x007FFFFF (5MB) Linux kernel image (kernel)
0x00800000 - 0xff7ffff (>~248MB) Root filesystem (rootfs)
0xff800000 - End of FLASH (512KB) U-Boot NAND bad blocks table. Sectors mark as bad, don't touch !!


APF28 / U-Boot 2011.12 and newer release - Flash memory partitions

NAND flash address range Type
0x00000000 - 0x002FFFFF (3MB, including NAND SPL and spare memory for bad blocks) U-Boot
0x00300000 - 0x0037FFFF (512kB) U-Boot environment variables (primary partition: env)
0x00380000 - 0x003FFFFF (512kB) U-Boot environment variables (redundant partition: env2)
0x00400000 - 0x0047FFFF (512kB) DeviceTree Block partition (dtb)
0x00480000 - 0x004FFFFF (512kB) Reserved for a futur splash screen (splash)
0x00500000 - 0x00CFFFFF (8MB) Linux kernel image (kernel)
0x00D00000 - End of FLASH (>~243MB) Root filesystem (rootfs)


APF51 / U-Boot 2011.12 and newer release - Flash memory partitions

NAND flash address range Type
0x00000000 - 0x000FFFFF (1MB, including NAND SPL and spare memory for bad blocks) U-Boot image
0x00100000 - 0x0017FFFF (512kB) U-Boot environment variables (primary partition: env)
0x00180000 - 0x001FFFFF (512kB) U-Boot environment variables (redundant partition: env2)
0x00200000 - 0x002FFFFF (1MB) FPGA bitfile
0x00300000 - 0x0037FFFF (512kB) DeviceTree Block partition (dtb)
0x00380000 - 0x003FFFFF (512kB) Reserved for a futur splash screen (splash)
0x00400000 - 0x00BFFFFF (8MB) Linux kernel image (kernel)
0x00C00000 - End of FLASH (>~500MB) Root filesystem (rootfs)

APF6

APF6 has an eMMC.

OPOS6UL

OPOS6UL has an eMMC.

Retrieved from "http://wikilegacy.armadeus.com/index.php?title=Target_Software_Installation&oldid=15216"