MOD54415 Boot Recovery

[keckrl]

My MOD54415 is failing to boot its application:

nb>Boot record INVALID Csum:2899

Configured IP = 0.0.0.0
Configured Mask = 0.0.0.148
MAC Address= e9:3a:81:82:75:11
ýnb>Welcome to the Netburner Alternate Boot Monitor Command Program


Netburner MCF5441x Alternate Image Monitor V1.03 Oct 26 2013 16:25:49
HELP for help
nb>

Autoupdate sees it, but when I run Autoupdate to set it back to the factory app, Autoupdate hangs with Perecent Complete showing no progress.
At this point the monitor no longer responds and I have to reset to get it back.

Neburner tools are 2.6.7. I presently have the MOD54415 mounted in a MOD-DEV-70. Dev system is Windows 7, 64 bit.
How do I recover?

[ecasey]

I think you will have to load a known good app through the UPS or serial port.
Follow the instructions at section 4.3.2 in the DocumentationOverview.pdf in the "docs" folder in the nburn directory at page 15 for downloading to flash memory. The app you load should be one that includes the "EnableAutoUpdate();" line in the main.cpp file. Usually the factory demo program will work.

Ed

[keckrl]

I tried the serial download using the factory app (over the USB port on the MOD-DEV-70).
At the end of the download I see
******Er

If I Reset, I get:

Boot record INVALID Csum:2CBB

Configured IP = 0.0.0.0
Configured Mask = 0.0.0.0
MAC Address= e9:03:f4:07:d6:11

If I reset again I get:

Boot record INVALID Csum:2899

Configured IP = 0.0.0.0
Configured Mask = 0.0.0.148
MAC Address= e9:3a:81:82:75:11
ýnb>Welcome to the Netburner Alternate Boot Monitor Command Program


Netburner MCF5441x Alternate Image Monitor V1.03 Oct 26 2013 16:25:49
HELP for help
nb>

I've tried this multiple times and the exact checksum and whether it goes into the monitor on the first reset or not varies. But it does not end up working.
So I'm still stuck.

[dciliske]

Short the alternate reset jumper (TP1, next to the Ethernet port) and perform a cold boot. Continue shorting the jumper until the prompt appears. This will ensure that you are using the backup config record in the alternate boot monitor. Now you should be able to update over AutoIP correctly. Also, depending on the age of the Alternate monitor image, (aka, pre Q2 2013) there could be a latency bug which can corrupt the serial download. If this is the case you need to do a serial download, you will need to perform a native boot and abort to the monitor. This will give you the base monitor, without network connectivity. This monitor will not have the latency issue.

[Edit]: Take a look at this guide for getting to the alternate boot monitor: http://forum.embeddedethernet.com/viewt ... f=3&t=1655

-Dan

[keckrl]

I finally got it back.
I tried powering the MOD-DEV-70 with an external supply rather than using USB power. Did the FLA command. That still ended with:
*****Er
but after a reset it booted the factory app.

So it appears that powering the MOD54415/MOD-DEV-70 via USB maybe marginal.

[keckrl]

Note to dciliske:

I had tried doing the TP1 short when I posted my first message. But Autoupdate hung (or if I waited long enough, timed out).
It was at that time powered by USB, so that may have been the problem.

[dciliske]

Was this off of a laptop perchance?

[keckrl]

No. It is/was connected to a powered hub, in turn connected to a desktop.

[rnixon]

A good test would be to plug the dev board directly into your desktop's USB connector and see if the results are different. The powered hub may not be providing enough power (more is required during flash programming).