Changes between Version 7 and Version 8 of Boards/Zynq - Zedboard

Timestamp:

02/09/17 01:56:47 (7 years ago)

Author:

Chris Johns

Comment:

Add RTEMS application details.

Boards/Zynq - Zedboard

@@ -67 +67 @@
 I do not used the Xilinx version of U-Boot they provide on Github. I also do not use any binary builds available for download.
 
+== U-Boot License ==
+
+U-Boot is license under GPL-2 which means you will need to make the source code for U-Boot available to users of your product. Please check the GPL-2 license to make sure you can use U-Boot and what you need to do to meet the license.
+
 == Building U-Boot ==
 
@@ -124 +128 @@
 '''Note:'''
 1. The `bootfile` is the file name used by the TFTP protocol. The path is relative to the top level path the TFTP server is configured to serve file from. This path is available to the development host machines so the executable can be updated after a build.
-1. The `loadaddr` must match the static address the RTEMS executable is built with.
+1. The `loadaddr` is the address U-Boot loads the image before it is relocated to the address RTEMS is built with. This value needs to be valid RAM and it is best if it does not overlap with the image's final located address.
 1. The subnet is `10.10.5.0/24` and it has a DHCP server. The `dhcp;` command tells U-Boot to get an IP address using the DHCP protocol and optionally download an executable using the TFTP protocol. I do not define a boot file in the DHCP server so it can vary for each board on networking that is net booting.
 1. The TFTP server IP address is manually set to `10.10.5.1`. 
@@ -153 +157 @@
 = RTEMS Application =
 
-TDB
+The RTEMS executable is an ELF format file and U-Boot requires custom image format which means you need to convert the RTEMS ELF executable file to the custom image format.
+
+The following script is an example of how you perform this conversion:
 
 {{{
@@ -173 +179 @@
   -d "$EXE_NAME.gz" "$EXE_NAME.img"
 }}}
+
+'''Note:'''
+1. The `arm-rtems4.12-objcopy` is part of the RTEMS ARM binutils package built by the RSB.
+1. The `START_ADDR` the base address the RTEMS executable is linked too. This is set in the RTEMS BSP code for the !ZedBoard and Microzed board.
+1. The `ENTRY_ADDR` is the entry point to the RTEMS executable. This again is BSP specific. For the ZedBoard the entry point is the base address.
+1. The RTEMS executable is stripped of any debugging information and converted to a binary image and then compressed. Stripping the executable or debugging information does not effect your ability to debug the application because debugging uses the ELF image which still contains the debugging information.
+1. The host tool `mkimage` is built as part of U-Boot. You can find it under `toos/mkimage`. You need to copy it somewhere in your path or add a path so it can be executed.