PDA

View Full Version : MiniPod not responding


dklofas
01-03-07, 02:45 PM
I'm a total newbie to the MiniPod and Forth. I wrote my first test program, downloaded it through NMITerm and ran it through NMITerm. This program to blinks the red led.

Then I added an autostart directive and reset the power. The MiniPod isn't responding to the NMITerm, nor running the blinker code. I have searched through the documentation endlessly for a hardware reset because it doesn't seem to be responding through the the serial at all. Is there a hardware reset of any sort / a way to force it to respond to the NMITerm?

Thanks
Andrew

Dave
01-03-07, 03:43 PM
Hello Andrew,

To remove a program from flash that has taken over the Minpod, jumper the SCLK pin to ground. SCLK is located on the J9 connector, pin 6, and can be tied to pin one of J9 for this operation. Once jumpered, type SCRUB into the terminal, and the program will then be removed. Disconnect the jumper and then normal operation can continue.

Some information regarding this is in the Autostart note (http://www.newmicros.com/store/product_manual/autostart.pdf) on the Pods Download page (http://www.newmicros.com/store/product_details/download.html) though not showing specific pins for the Minpod.

pickle
04-08-08, 03:53 PM
When I power my minipod up, the IsoMax prints and I can enter a command but the command line hangs up. Also, I jumpered pin 6 and pin 1 on J9 and that didn't help.

Did I fry my micro?

RMDumse
04-08-08, 04:08 PM
Maybe. But an awful lot of code runs just to get the log on message to run, so it wouldn't be my first expectation the processor was fried. Be sure the terminal window isn't locked up. Restart NMITerm. Check your serial wiring. Maybe your cable from the PC transmit line broke or came loose.

Does the board do anything? Echo characters as you type SCRUB? Or does it work until you hit enter?

Two ways to go from here. You can send us the board, and we can try to reload the kernel. or you can buy a license copy with a signed agreement and JTAG, and reload the kernel yourself.

Or maybe it is fried and that won't help.

If you've got a little time, I'd suggest let us look at it. Contact nmiproduction@newmicros.com for a RMA so we can track it.