MOD5282 Boot Malfunction

[ecasey]

Help!

I was trying to change the IP address of a MOD5282 on a MOD DEV 100 V1.12 board using the IPSetup utility. I blanked out the IP and Mask fields and then pressed the Set button. The MOD5282 disappeared from the "Select a Unit" window and would not respond to MTTTY on the USB connection either. Not even after reset or power down. I connected it to a serial port and all I get is a repeat of

• Trap occured
  Vector=05FMT =00 SR =2700 FS =00
  Faulted PC = FFC004EC
  D0:00000000 003F4800 00000018 00000000 00002700 10924F50 91C61551 13B010DF
  A0:FFFFAAAA FFC04094 20000464 FFC00274 FFC00512 FFC00FCA 200007FC 20000640

over and over. It starts immediately on reset and cannot be interruped. I tried Shift-A on reset, but there is no delay, the message just starts up.

Is there any way to get this back?

Ed

[rnixon]

Blanked out meaning no numbers, or did you enter in 0's? What is powering the board, usb or wall supply? If usb, exactly what type of usb connection, meaning direct to desktop/tower computer, computer monitor, laptop, etc? Just wondering if maybe your usb connection doesn't have enough current supply to handle a draw when the flash is being programmed.

[ecasey]

I blanked out the fields; did not enter numbers or zeros; I was trying to get it to reboot and acquire an address via DHCP (evidently not the right approach). It was USB powered through a powered hub (wall wart), with plenty of power. I have been using it this way for a year now with out incident.

Does IPSetup operate through the USB serial or over TCP?
Ed

[rnixon]

IPSetup works through the network, not usb or serial. Choosing between dhcp and static IPs is usually handled in your application code. In all the examples near the beginning of UserMain() there will be something like: if (EthernetIP == 0). If true, then there is a call to dhcp, if false, then is uses the address as static. So if your app supports it, writing 0's would be the right thing to do. But I wouldn't expect spaces to be a problem either. You might have to contact them through support to see what is going on when blank fields are used. It may or may not have to do with what happened.

[tod]

I can't tell if you tried it but it's worth doing a cold boot. Power down, power up and break into the monitor before the first trap can occur. In your case it might not help if the trap is happening immediately even after a cold boot but I thought I would suggest it just in case.

[ecasey]

Thanks tod and rnixon,

There is no delay between a cold boot and the trap, so I can't break in. I started a support ticket. I will report what they advise.

In the mean time, be careful with IPSetup. I am using NNDK version 2.53. It could be a bug. If so, it has big teeth.

[ecasey]

Here is an update:

I contacted Support and they tried to duplicate what happened, but couldn't.
They sent me the s19 file for the MOD5282 boot monitor and the pin-out for the BDM interface.
I have a P&E Micro U-MultiLink that will work as a BDM Loader.
Here's the process:

1. Build an adapter to go from the U-MultiLink pin-out (26-pins) to the MOD5282 pin-out (20-pins).
2. Connect up the U-MultiLink and Flash the boot monitor s19 file to the address at the start of that file.
3. Disconnect the U-MultiLink cable.
4. Connect to the board using Mttty via a serial cable.
4. Re-boot the board: I got a "Bad Checksum" error and the "nb>" prompt.
5 Type "setup".
6. Choose "8" to change it to boot to Application.
7. Pressed "s" to save, it told me it had no MAC address and prompted for one.
8. Keyed in the MAC from the sticker on the board, saved it
9. Loaded the "DBFactory_APP.s19" file.

Then it booted properly.

It seems to work fine now, and as a bonus, it uses DHCP now. Case closed!

Ed