Cannot leave Alternate Image Monitor

[jintadhee]

I am not sure what went wrong to my MCF5441x, after I flash a new app.
I show "nb>" prompt and with the following message:

Boot record is Valid
Welcome to the Netburner Alternate Boot Monitor Command Program
Netburner MCF5441x Alternate Image Monitor V1.00 May 29 2012 15:25:39
HELP for help
nb>

I try to re-flash it with "MOD54415FactoryApp_APP.s19" using command "FLA".
After a while later, it shows "Download failed".
I have tried a few time. Still the same result.

What can I do to make it work again.

Please help.

[rnixon]

Can you see the device in IPSetup?

[dciliske]

Clarification: If you can find the device on IPSetup, then you can use autoupdate to upload the factory image. If you cannot find the device via IPSetup, then there is a possibility that there is a hardware fault present [img]somewhere[/img].

So, the questions to address in this situation are:

1. Can you find the device via IPSetup?
2. Can you reflash the device using Autoupdate, while in the fallback monitor?
3. Is there anything connected to the Flexbus of the module?
4. Is the device in the dev carrier board or a custom board?

Judging from past experience, I'm going to guess you have something else on the Flexbus lines, which are not in high-z, tying one or more line high or low. This will interfere with access the modules flash, and hence prevent you from reflashing the unit/corrupting the flash.

-Dan

[jintadhee]

Thank you for all your help.

I finally fix it by using "setup" command in "nb>" prompt via serial port.
I saw that somehow the setting was corrupted.
The MAC address was invalid.
Yesterday, I corrected the MAC address using "setup" command but do nothing else.

With unknown reason, the "Boot to Monitor" was selected.
Switch to "Boot to Application" correct the problem.

[dciliske]

You may have corrected the issue for now, but have you determined what caused this failure in the first place? If you haven't, you will run into much worse problems down the road when the device fails after being deployed...

[jintadhee]

Dan,

You are definitely correct.

The original problem caused by my custom board.
The story is:

I tested the MOD54415 on Dev-70 Kit. Everything work fine.
Then, I remove the MOD54415 from Dev-70 and plug into my custom board.
At that time, I did not monitor the serial port. I just connected NBEclipse
and it seems no problem. Then I try to debug the MOD54415, NBEclipse try to Autoupdate as usual but failed.
So, I plug in a serial port, reset the MOD54415 and saw that all setting on the MOD54415 are gone and the MOD54415 stay in "nb>" prompt. I re-assigned the MAC address (because somehow it has been erased).
After rest the MOD54415, IPSetup show that MOD54415 is in Alternate Image Monitor mode.

Then I remove the MOD54415 and put it back to the Dev-70 kit.
The MOD54415, still in Alternate Image Monitor mode.
This is the starting point of my original post.

Now, I understand that my custom board is the real issue.
I need to find out and fix this problem.

So, I re-create the issue similar to the original post and monitor serial port to see any unusual behavior which may be a clue lead to the cause of all problem.

These are the serial port output:

Boot record INVALID Csum:6DAA
Reset Jumper Detected
nb>Welcome to the Netburner Alternate Boot Monitor Command Program
Netburner MCF5441x Alternate Image Monitor V1.00 May 29 2012 15:25:39
HELP for help

One more information which may be useful is:
After the "Boot record INVALID Csum" above occur, without trying to write anything down to FLASH/EEPROM,
if I remove the MOD54415 from the custom board and put it back in to the Dev-70.
The MOD54415 come back to work again (no settings lost).
This shows that the issue is originally happen to the data/address bus or RAM or RESET SYSTEM of the MOD54415.
As Dan mentioned, tying or short of the Flexbus lines will interfere with access the modules flash.

Does "Reset Jumper Detected" mean anything to you ?
I believe that it may be the problem at the Flexbus line as Dan mentioned.
But I would like to reduce scope down if possible.
If anybody can tell that "Reset Jumper Detected" has any meaning (or it just the way NetBurner telling that it detect bad check sum and reboot system into Alternate Boot Monitor mode),
Please let me know.

Thank you so much,
Jin