corrupt IsoMax or bad chip?

[Chubs]

(IsoPod V2)

How can I tell if I have a corrupted kernel (IsoMax), or if
I have damaged the pod by offseting the power
connection by one pin inboard
(Pw-->Gnd & Gnd-->Reset)?



Thanks,
chubs

[RMDumse]

If you want to send it back we can try it out for you.

Generally with a JTAG cable and the kernel (available by non disclosure fee and small charge) you can download and reflash the kernel. You know pretty quick if it will talk under JTAG, you're probably alright, and if it won't... it won't.

[Chubs]

I have the jtag cable. I will need to purchase another kernel.
I am not familiar with the jtag, but I am familiar with parallel IO
and the evaluation of memory blocks.

Where can I get more info on reflashing the IsoPod and other jtag ops?

thanks,
chubs

[nmitech]

Chubs,
If your kernel is corrupted, simply put a jumper on pin 2(GND) & 4(SCLK) of J5 (IsoPod_V2) and reset or recycle the power to bypass the bad autostart and you will get the IsoMax prompt back. Next enter SCRUB to remove the corrupted program then remove the jumper and reset the system to start from fresh. If you don't get any response with the option above, Reflash is your last option to find out if the hardware is damaged.

To reflash your IsoMax kernel, makesure you have the Jtag-cable-10P and sign the license agreement to recieve the Srecord just in case have not do so. Here is the instruction how to flash with the Jtag cable, http://www.newmicros.com/isopod/appnotes/JTAG_note.txt

[Chubs]

(IsoPodV2)
The machine I am working on is running Win ME OS.
LTP1's base address at 378. I think everything on
the PC-end is ok (no "command converter" error).

I'm trying to do memory dump but 805 fails to go
into debug mode.
Below, do you see any error on my end?

Thanks,
chubs


C:\WINDOWS\Desktop\JTAG>flash_over_jtag flash805.cfg -vx0x0:0x1000

DSP56F800 Flash loader. Compiled on May 16 2003, 07:34:53.
version Epsilon 0.4
(c) Motorola 2001 - 2002, MCSL
Partial Copyright 2000-2002, Zloba Alexander
JTAG IR path length: 4
JTAG DR path length: 1 (BYPASS)
IDCode status: 0x9
Jtag ID: 0x11f2501d
Debug Request status: 0x9
Enable OnCE status: 0x9, polls left: 10
Enable OnCE status: 0x9, polls left: 9
Enable OnCE status: 0x9, polls left: 8
Enable OnCE status: 0x9, polls left: 7
Enable OnCE status: 0x9, polls left: 6
Enable OnCE status: 0x9, polls left: 5
Enable OnCE status: 0x9, polls left: 4
Enable OnCE status: 0x9, polls left: 3
Enable OnCE status: 0x9, polls left: 2
Enable OnCE status: 0x9, polls left: 1
Enable OnCE status: 0x9, polls left: 0
Target chip refused to enter Debug mode!
The target was reset, the application is running

[RMDumse]

That sure looks like the chip got clobbered, as in, dead. If you can't talk through the JTAG, then the chip cannot be recovered.

Would you like to send it in for repairs?

[Chubs]

I might do an upgrade to the ServoPod.
I could use the extra memory, and the
RS232 on the V2 has been a bit of a hassel.

What's the additional cost to have ServoPod
configured with out the RS232 translator, and or jumper
to select TTL<--->RS232 ?



Thanks,

chubs

[nmitech]

Both IsoPod V2 and ServoPod have RS-232 driver on the second serial port. To configure it for TTL, it requires afew cuts and jumpers. There is no extra charge for TTL modification. Keep in mind, you can only have one without another because there is no physical jumper onboard to switch is back to RS-232.

[heathkit]

I have a isopod v1 return this exact same output whenever I try to flash it. Any idea what causes this? I find it interesting that some of the values returned seem to be valid - the chip isn't completely unresponsive.

Are you guys in Dallas? Could I bring it in soon?

[nmitech]

If the reset signal stays low, board will not respond and you will see that message. Could be the serial DTR signal held it low when you run the Terminal program. Try to unplug the serial cable when you flash. This most likely happens on Isopod V1 only.

Yes, we are here in Dallas, TX. Please give us a call in advance. You can contact Chris Vond. (or B.C.) at 214-339-2204 to setup a schedule.

Please bring your Jtag cable along. Thanks!

[heathkit]

Well, I took the isoPod into New Micros today, and they flashed it right off, no problems. I took it home and sure enough, had the same problem I'd been having earlier.

Turns out my power supply is fried. So, if anyone is experiencing this issue, make sure that's the first thing you check.