Target Software Installation - Revision history

KevinJ at 13:12, 3 October 2025

2025-10-03T13:12:13Z

@@ Line 184: / Line 184: @@
 </pre>
 ** [[APF6]]: [[U-Boot UMS on APF6|U-Boot UMS]]
 ==Update U-Boot==

KevinJ at 13:06, 3 October 2025

2025-10-03T13:06:30Z

@@ Line 194: / Line 194: @@
 * You can make some trials with the ''firmware/leds/blinking_led/bin/'' files.
 <br>
 ==Update U-Boot==

KevinJ: /* FPGA firmware installation */

2025-10-03T13:03:13Z

FPGA firmware installation

← Older revision		Revision as of 15:03, 3 October 2025
Line 196:		Line 196:

	==FPGA firmware installation==		==FPGA firmware installation==
	~~=== APF9328, APF27 and APF51 ===~~
	* instal/copy your firmware to /tftpboot
	** manually: <pre class="host"> $ cp myfirmware.bin /tftpboot/apfXX-firmware.bin (where apfXX is the name of your board: apf27, apf51 or apf9328)</pre>
	** using the armadeus BSP:
	~~:<pre class="host"> $ make menuconfig</pre>~~
	~~:<pre class="config">Package Selection for the target ---> Armadeus specific tools/utilities ---></pre>~~

	~~:you can specify the path to the FPGA firmware:~~
	~~<pre class="config">~~
	~~[*] FPGA Firmware~~
	~~Firmware to install (Install a custom FPGA firmware) --->~~
	~~($(TOPDIR)/../firmware/leds/blinking_led/bin/blinking_led_apf27_200k.bit) FPGA binary file path~~
	~~[*] Export this file to Buildroot images folder~~
	~~</pre>~~
	~~:<pre class="host"> $ cp buildroot/output/images/* /tftpboot </pre>~~
	* Download and test your firmware image with:
	~~<pre class="apf">~~
	~~BIOS> run download_firmware~~
	~~BIOS> run load_firmware~~
	~~</pre>~~
	* When you are satisfied with your firmware, you can write it in flash make it "autoloaded" at power up:
	{{Warning\| '''Before''' setting the firmware_autoload variable, be sure that your FPGA binary file is correct. If not, your board will '''hang up''' at U-Boot start and you will need to cancel the fpga download to take control of the board. see note below}}
	~~<pre class="apf">~~
	~~BIOS> run update_firmware~~
	~~BIOS> setenv firmware_autoload 1~~
	~~BIOS> saveenv~~
	~~</pre>~~

	{{Note \| (U-Boot 2012.04) you can manually cancel the firmware autoload using the following procedure: keeping <CTRL-C> pressed on the console and power up the board will start the board without downloading the FPGA firmware - This procedure can be helpfull if you have programmed a broken firmware }}

	=== APF6_SP ===		=== APF6_SP ===

KevinJ: /* FPGA firmware test */

2025-10-03T12:16:35Z

FPGA firmware test

@@ Line 194: / Line 194: @@
 * You can make some trials with the ''firmware/leds/blinking_led/bin/'' files.
 <br>
 ==FPGA firmware installation==

FabienM: /* Update U-Boot, kernel and rootfs images all at once */

2021-09-09T07:46:32Z

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

← Older revision		Revision as of 09:46, 9 September 2021
Line 338:		Line 338:

	Advanced informations can be found at the [[BootLoader]] wiki page.		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>

			See [[How_to_use_vanilla_kernel_on_APF51]] for more informations.
			}}


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

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

2019-01-10T10:33:04Z

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

← Older revision		Revision as of 12:33, 10 January 2019
Line 383:		Line 383:

	===APF27 / U-Boot 2011.12 and newer release - Flash memory partitions===		===APF27 / U-Boot 2011.12 and newer release - Flash memory partitions===
			* It's safer to not touch sectors marked as red ;-)

	{\| border="1" cellpadding="5" cellspacing="0" summary="APF27 Flash memory partitions"		{\| border="1" cellpadding="5" cellspacing="0" summary="APF27 Flash memory partitions"
	\|- style="background:#efefef;" align="center"		\|- style="background:#efefef;" align="center"
	! width="60%" \|NAND flash address range !!Type		! width="60%" \|NAND flash address range !!Type
	\|- align="center"		\|- style="background:#ffcccc;" align="center"
	\|0x00000000 - 0x000FFFFF (1MiB, including NAND SPL and spare memory for bad blocks)		\|0x00000000 - 0x000FFFFF (1MiB, including NAND SPL and spare memory for bad blocks)
	\|U-Boot image		\|U-Boot image
Line 405:		Line 407:
	\|Linux kernel image (kernel)		\|Linux kernel image (kernel)
	\|- align="center"		\|- align="center"
	\|0x00800000 - ~~End of FLASH~~ (>~248MB)		\|0x00800000 - 0xff7ffff (>~248MB)
	\|Root filesystem (rootfs)		\|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>		<br>

JulienB: /* Linux kernel installation */

2019-01-10T09:47:04Z

Linux kernel installation

← Older revision		Revision as of 11:47, 10 January 2019
Line 88:		Line 88:
	BIOS> printenv update_kernel		BIOS> printenv update_kernel
	</pre>		</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 ~~transfered~~ size value is less than the ones specified here [[#Flash_memory_partitions\|Flash Memory Partitions]]		{{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]]
	}}		}}

Line 114:		Line 114:

	----		----
	Check that ~~transfered~~ size value is less than the ones specified here [[#Flash_memory_partitions\|Flash Memory Partitions]]		Check that transferred size value is less than the ones specified here [[#Flash_memory_partitions\|Flash Memory Partitions]]
	<pre class="apf">		<pre class="apf">
	Bytes transferred = 1313216 (1409c0 hex)		Bytes transferred = 1313216 (1409c0 hex)

JulienB: /* Linux kernel installation */

2019-01-10T09:46:26Z

Linux kernel installation

← Older revision		Revision as of 11:46, 10 January 2019
Line 70:		Line 70:

	==Linux kernel installation==		==Linux kernel installation==
	~~XX, in the following chapters, has to be replaced by your board name~~

	* Check that your Armadeus kernel image size is smaller than the U-Boot partition (see [[#Flash_memory_partitions\|Flash Memory Partitions]] for size allowances):		* Check that your Armadeus kernel image size is smaller than the U-Boot partition (see [[#Flash_memory_partitions\|Flash Memory Partitions]] for size allowances):

FabienM: /* Network configuration */

2017-07-06T07:13:48Z

Network configuration

← Older revision		Revision as of 09:13, 6 July 2017
Line 34:		Line 34:

	===Network configuration===		===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:		In order to use the U-Boot's network features, you have to set the network environment variables:
	<pre class="apf">		<pre class="apf">

Jorasse: /* Network configuration */

2017-01-27T13:57:16Z

Network configuration

← Older revision		Revision as of 15:57, 27 January 2017
Line 43:		Line 43:
	</pre>		</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.		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 make sure you have selected Bridge Mode for the network adaptor, otherwise the U-Boot cannot talk to your host.		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">		<pre class="apf">
	BIOS> dhcp		BIOS> dhcp