The last 80 bytes (0x5003FFB0 -> 0x5004000) are the "Sercomm trailer" (SercommRedBootTrailer?). This seems unimportant but for one component; the MAC address, which must live in the six bytes from 0x5003FFB0. For example, in RedBoot

to:

The last 80 bytes (0x5003FFB0 -> 0x5004000) are the "Sercomm trailer" (Sercomm RedBoot trailer). This seems unimportant but for one component; the MAC address, which must live in the six bytes from 0x5003FFB0. For example, in RedBoot

Changed lines 82-83 from:

Use [[http://www.wienand.org/junkcode/python/padredboot.py | padredboot.py] to pad out the redboot.bin to the required 256K and write in a MAC address. Usage is

to:

Use padredboot.py to pad out the redboot.bin to the required 256K and write in a MAC address. Usage is

the build should whizz by, and install/bin/redboot.bin is almost ready to go

Edit default values

The file ecos.ecc in the build directory can be edited to override default values, such as the boot script and the IP address/port to listen on by default. Run ecosconfig tree after editing to update, and then rebuild

Getting it to boot

In a few words, we should be able to just copy over the new redboot image and overwrite the old one.

Redboot needs to live in the 256K from 0x50000000 -> 0x50040000 (thus, the redboot image must be less than 256K!)

The last 80 bytes (0x5003FFB0 -> 0x5004000) are the "Sercomm trailer" (SercommRedBootTrailer?). This seems unimportant but for one component; the MAC address, which must live in the six bytes from 0x5003FFB0. For example, in RedBoot