- Image of Garbled Message
- screen1.png (31.69 KiB) Viewed 7114 times
SB72Monitor Recovery Problems
SB72Monitor Recovery Problems
Due to the SB72 not operating I wanted to restore the monitor. Following the instructions in the SB72MonitorRecovery.pdf, a Hard reset gives garbled text and no nb> prompt. How can one restore the SB72. I am using windows XP
Re: SB72Monitor Recovery Problems
First thing I would check is your baud rate. Looks wrong. Try them all in MTTTY
Re: SB72Monitor Recovery Problems
I have tried all the baud rates and still no change.
Re: SB72Monitor Recovery Problems
Do you have it connected in to a netburner development board and power supply?
Are you using RS-232 or TTL?
How did the problem occur? Did you download a new app, were you writing to flash memory, did power go away during a download, etc.
Are you using RS-232 or TTL?
How did the problem occur? Did you download a new app, were you writing to flash memory, did power go away during a download, etc.
Re: SB72Monitor Recovery Problems
I agree with the others, this looks like a baud rate error. It is possible to set the baud rate to any value in the configuration record, it is not limited to the standard RS-232 baud rates. The ways you could have changed the baud parameter are from the monitor settings menu, the IP setup tool or if your application wrote to the configuration record sector of the flash.
Does your module boot to your application? Is there any Ethernet functionality? Can you see the board in IPSetup? If you can this would be the easiest way for you to change the serial baud rate setting.
Another option would be to look at the UART TX line with a logic analyzer or oscilloscope. If you find that the baud rate is strange then you will then need to have a PC serial port allows for non-standard RS-232 baud rates. My PCI-e serial card must have custom baud rates configured through the device properties:
Device Manger > Ports > Right click one of the com ports > properties > advanced tab > adv baudrates button
Not all serial ports support this.
If you can't get Ethernet or Serial communication working with the module then the only recovery option is BDM programming. You can contact NetBurner support for RMA information.
-Larry
Does your module boot to your application? Is there any Ethernet functionality? Can you see the board in IPSetup? If you can this would be the easiest way for you to change the serial baud rate setting.
Another option would be to look at the UART TX line with a logic analyzer or oscilloscope. If you find that the baud rate is strange then you will then need to have a PC serial port allows for non-standard RS-232 baud rates. My PCI-e serial card must have custom baud rates configured through the device properties:
Device Manger > Ports > Right click one of the com ports > properties > advanced tab > adv baudrates button
Not all serial ports support this.
If you can't get Ethernet or Serial communication working with the module then the only recovery option is BDM programming. You can contact NetBurner support for RMA information.
-Larry
Re: SB72Monitor Recovery Problems
I have been able to see the monitor screen in normal text. When booting up I have the choice to press A. When I do this there is no communication to the device. I have tried both Mtty and Hyperterminal and both programs do not communicate with the device. The operating system is XP and the SB72 module being tested is brand new.
Re: SB72Monitor Recovery Problems
Hi,
How did you recover the serial output?
You said that there is no output if you press 'A' to enter the boot monitor, what happens if you don't press anything and let the application attempt to boot? If the application does nothing after the boot message in both cases then you should test the serial output from your PC. You can do this by putting a jumper on your serial cable RX/TX lines to make a loop-back, then ensure that you can see the transmitted chars in MTTTY.
Make sure that you do a hard power cycle can press 'A' on the first boot. A soft reset after the first boot may not work correctly depending on the failure mode of your application.
What exactly is your application doing that makes it crash? Does it write to flash?
How did you recover the serial output?
You said that there is no output if you press 'A' to enter the boot monitor, what happens if you don't press anything and let the application attempt to boot? If the application does nothing after the boot message in both cases then you should test the serial output from your PC. You can do this by putting a jumper on your serial cable RX/TX lines to make a loop-back, then ensure that you can see the transmitted chars in MTTTY.
Make sure that you do a hard power cycle can press 'A' on the first boot. A soft reset after the first boot may not work correctly depending on the failure mode of your application.
What exactly is your application doing that makes it crash? Does it write to flash?