Msc8156 ethernet boot

[Jim95]

Hello,

I have generate a srec file using the ELF2xx and SREC2xx utility.

AndI have configurate my pc ipadress (10.0.0.1), the dhcp server and the tftpserver using the Ethernet Boot Test pdf.

But when try the boot the board, everything is ok until the first data block is sending by the tftp server, that produced a checksum error (code : 003FEFFD).

I think it's because the tftp server cut a reccord in two parts.

I am using Codewarrior 10.1.8, DHCPTurbo (dhcp server), TFTPTurbo (tftp server) and Ethereal (ethernet sniffer).

Do someone know a solution to avoid this ?

[AndrewinApps · Accepted solution]

Hello Jim95,

Have you ensured that your srec file is only on 1 file?

It is perfectly fine and normal to send an SREC over multiple packets, the big issue is that you must remove all carriage returns from the file. 

Otherwise, from the pcap capture, it appears that things are running fine up to that point, so the boot process was correctly initiated.

Regards,

-Andrew

[Jim95]

Hello Andrew,

Thank you for your response.

I removed the carriage returns, it  works well when I only use sc100-elf2xx.

But when I use sc100-elf2xx and sc100-srec2xx some reccords need to be written in the DDR1, that is not initialized, and the boot-loader stop.

Regards

Jimmy

[AndrewinApps]

Hello Jimmy,

Using DDR requires running a boot patch. If you need this, please create an SR via the Freescale support page.

Regards,

-Andrew

[ldg]

Is a two-stage process like this possible?

1) Simple Ethernet Boot loads a small stub of DDR initialization code

2) stub initializes DDR and re-enters the boot ROM

3) boot ROM resumes Simple Ethernet Boot and loads main image into DDR

In theory this is simple but hinges on the re-entrancy of the boot ROM in Simple Ethernet Boot mode. If this isn't possible, what prevents it?

[AndrewinApps]

This would require doing a DDR initialization boot patch running out of EEPROM.

Simple ethernet boot jumping back into the BootROM is not something we support.