Servopod Isomax upgrade failed

[RonaldW]

Hello,
I have a servopod with Isomax 0.6. The pod seems to work just fine.
I just recieved a JTAG cable from newmicros since I have a license to upgrade isomax to version 0.82
I have tried the flash utility both on an XP and Win98 machine. On both machines I get the message "TARGET CHIP REFUSED TO ENTER DEBUG MODE! THE TARGET WAS RESET, THE APPLICATION IS RUNNING".

Other text in the command window are:
JTAG IR PATH LENGTH: 256
JTAG DR PATH LENGTH: 256 (bypass)
IDCODE status: 0xf
JTAG ID: 0xffffffff
Debug request status: 0xf

I have reset the system and used SCRUB but to no avail. What am i doing wrong ?

Thanx,

Ron

[RMDumse]

Oh, I have that happen every now and then. Sometimes I have the JTAG connector rotated 180 degrees. Sometimes I forget to power the board when I'm trying to flash it. What else? Are you sure the JTAG is on the right parallel port? Have you ever successfully flashed a board before?

The Win 98 system is more likely to be cooperative. The XP is a bit tricky, because it doesn't allow direct hardware access.

I use an XP laptop for all my development, but it's been years since I set it up. Maybe LC will be in Tuesday, and have some more ideas.

[RonaldW]

Yep,
I tried the JTAG connector both ways and checked the parallel port (lpt1 #378). I even used the -p0 option. I made sure to power the board also by connecting the serial port and NMITERM.

Is there an easy way to check (debug) the cable ? Since I bougth the cable from Newmicros I do not want to mess with it to much.

Ron

[RMDumse]

One thing I haven't heard you explicitly say was if the target board was powered. The JTAG cable doesn't supply power, so if you try to FLASH an unpowered board, you'll get the result you mention.

However, if you were hooked up via NMITerm and talking to the board before trying to FLASH it, that' would be a good indication it was powered.

It is difficult to check a cable. Our production folks test every product before it goes into a shipping box, but those cables do sometimes come loose from shaking of shipment and manipulation. Probably the easiest way to "check" it would be to send you another one. I will notify sales.

[nmitech]

Beside the Power required that Randy mentioned, you may try to run the driver_remove program and reboot your system. This works for my XP system after several tries.

Besure you have the Srecord file, v082-2.s and the flash803.cfg file in the same folder with the flash_over_jtag program. This is a must.
Note: The flash803.cfg file can be used for MiniPod(DSP56F803), and IsoPod(DSP56F805) CPU.

[nmitech]

Sorry, i missed your 1st post.
So the Srecord file, v082-7.s and the flash807.cfg file need to be in the same folder with the flash_over_jtag program.

[RonaldW]

Thanks for the support people, but I am sorry to say, still to no avail. I tried a third machine (XP), made sure power was on, tried the jtag cable two ways but here are the results:

E:\SERVOPOD>flash_over_jtag flah807.cfg v082-7.s
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
I/O port driver started
JTAG IR path length: 256
JTAG DR path length: 256 (BYPASS)
IDCode status: 0xf
Jtag ID: 0xffffffff
Debug Request status: 0xf
Enable OnCE status: 0xf, polls left: 10
Enable OnCE status: 0xf, polls left: 9
Enable OnCE status: 0xf, polls left: 8
Enable OnCE status: 0xf, polls left: 7
Enable OnCE status: 0xf, polls left: 6
Enable OnCE status: 0xf, polls left: 5
Enable OnCE status: 0xf, polls left: 4
Enable OnCE status: 0xf, polls left: 3
Enable OnCE status: 0xf, polls left: 2
Enable OnCE status: 0xf, polls left: 1
Enable OnCE status: 0xf, polls left: 0
Target chip refused to enter Debug mode!
The target was reset, the application is running

As you can see, the drivers run correctly and all the files are in the directory I run from. Any suggestions?

Ronald

[Dave]

There is an error in the command line entered :

E:\SERVOPOD>flash_over_jtag flah807.cfg v082-7.s

should be :

E:\SERVOPOD>flash_over_jtag flash807.cfg v082-7.s

with a missing s in the cfg configuration file name.

Also, the red line of the ribbon cable of the JTAG should be closest to pin 1 of the JTAG connection of the ServoPod.

[RonaldW]

You have sharp eyes. Thanks for looking but this is not the problem since I have tried it several times with the correct setting.

Please don't give up. I appreciate all the help !!

Regards
Ron

[nmitech]

There is not much info about Freescale (motorola) JTAG driver provided on the flash_over_jtag.pdf file. So it's hard to debug nor tell what going on other than showing afew error messages. I post several test messages here so maybe we can figure out something based on the messages responded when i execute the JTAG driver.

First, here is the successful flash mesage look like,

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
I/O port driver started
JTAG IR path length: 4
JTAG DR path length: 1 (BYPASS)
IDCode status: 0x1
Jtag ID: 0x1f2701d
Debug Request status: 0xd
Enable OnCE status: 0xd, polls left: 10
Enable OnCE successful, target chip is in Debug mode
5 flash blocks defined in the config file.
S-record ID: PROGRAM&DATA
Data @ 0x40 ignored
Data @ 0x40 ignored
Data @ 0x40 ignored
" " "
" " "
Data @ 0x9A ignored
Data @ 0x9A ignored
Data @ 0x9A ignored
Initialising FIU at address: 0x1380
FIU (0x1380) initialisation done.
Flash (0x1380) mass erase done.
Flash (0x1380) programming done. 0 words written.
Initialising FIU at address: 0x1340
FIU (0x1340) initialisation done.
Flash (0x1340) mass erase done.
Flash (0x1340) programming done. 0x56b4 words written.
Initialising FIU at address: 0x1420
FIU (0x1420) initialisation done.
Flash (0x1420) mass erase done.
Flash (0x1420) programming done. 0 words written.
Initialising FIU at address: 0x1380
FIU (0x1380) initialisation done.
Mass erase skipped.
Flash (0x1380) programming done. 0x4 words written.
Initialising FIU at address: 0x1360
FIU (0x1360) initialisation done.
Flash (0x1360) mass erase done.
Flash (0x1360) programming done. 0xfff words written.
The target was reset, the application is running



Now come to the failure messages:

First test, Nothing connect but only run the Flash_over _Jtag software

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
I/O port driver started
Command Converter not connected or disabled!The target was reset, the application is running



Second test, only connect the JTAG cable to the parallel port but not plug on the 'Pod.

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
I/O port driver started
JTAG IR path length: 256
JTAG DR path length: 256 (BYPASS)
IDCode status: 0xf
Jtag ID: 0xffffffff
Debug Request status: 0xf
Enable OnCE status: 0xf, polls left: 10
Enable OnCE status: 0xf, polls left: 9
Enable OnCE status: 0xf, polls left: 8
Enable OnCE status: 0xf, polls left: 7
Enable OnCE status: 0xf, polls left: 6
Enable OnCE status: 0xf, polls left: 5
Enable OnCE status: 0xf, polls left: 4
Enable OnCE status: 0xf, polls left: 3
Enable OnCE status: 0xf, polls left: 2
Enable OnCE status: 0xf, polls left: 1
Enable OnCE status: 0xf, polls left: 0
Target chip refused to enter Debug mode!
The target was reset, the application is running


Third test, Connect the JTAG from the parallel port and plug on the 'Pod with no the power applies to the 'Pod

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
I/O port driver started
JTAG IR path length: 4
JTAG DR path length: 1 (BYPASS)
IDCode status: 0x9
Jtag ID: 0x11f2501d
Debug Request status: 0xf
Enable OnCE status: 0xf, polls left: 10
Enable OnCE status: 0xf, polls left: 9
Enable OnCE status: 0xf, polls left: 8
Enable OnCE status: 0xf, polls left: 7
Enable OnCE status: 0xf, polls left: 6
Enable OnCE status: 0xf, polls left: 5
Enable OnCE status: 0xf, polls left: 4
Enable OnCE status: 0xf, polls left: 3
Enable OnCE status: 0xf, polls left: 2
Enable OnCE status: 0xf, polls left: 1
Enable OnCE status: 0xf, polls left: 0
Target chip refused to enter Debug mode!
The target was reset, the application is running



You see the differences on JTAG Code & ID on test 2 & 3 even without the power connect. Your result above is identical to my second failure test. So here is my best guess,
- You may plug the Jtag cable on reversed, or wrong connector on the 'Pod. The Jtag connector of the ServoPod is J8 .

- The Jtag cable, or the CPU Jtag circuitry alone, or the ServoPod is damaged. Can you connect your ServoPod to the serial and see if it still functioning? Because you never be able to flash with the new file, so i expected the IsoMax V0.6x is still there for ServoPod to talk serially. Just try to eliminate the problem.

[RonaldW]

Okay,
The servopod works fine with ISOMAX 0.6. I continually test it with NMITERM and run commands like GRNLED OFF etc. to make sure it responds.

I will try some more troubleshooting. I recently (1 month ago) purchased a tinipod. Is there a save way to test the tinipod and the jtag cable with the flash utility (I don't want to loose ISOMAX on the tinipod). This way it should be possible to eliminate any PC and JTAG cable problems.

Ron

[nmitech]

Solder the 2x5 header pin on the TiniPod so you can plug the JTAG cable, or you can hold the header tight if you don't want to solder. Makesure not to turn on the power to the TiniPod then Run the flash_over_JTAG program. So it won't over write your IsoMax. If everything is OK, atleast you will see the result similar to this,

...
I/O port driver started
JTAG IR path length: 4
JTAG DR path length: 1 (BYPASS)
IDCode status: 0x9
Jtag ID: 0x11f2501d
....

[RonaldW]

Hello people,
Thanks for sticking with me.
Here are some results:

JTAG cable run without pod connected:
E:\servopod\jtag>flash_over_jtag flash807.cfg
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: 256
JTAG DR path length: 256 (BYPASS)
IDCode status: 0xf
Jtag ID: 0xffffffff
Debug Request status: 0xf
Enable OnCE status: 0xf, polls left: 10
Enable OnCE status: 0xf, polls left: 9
Enable OnCE status: 0xf, polls left: 8
Enable OnCE status: 0xf, polls left: 7
Enable OnCE status: 0xf, polls left: 6
Enable OnCE status: 0xf, polls left: 5
Enable OnCE status: 0xf, polls left: 4
Enable OnCE status: 0xf, polls left: 3
Enable OnCE status: 0xf, polls left: 2
Enable OnCE status: 0xf, polls left: 1
Enable OnCE status: 0xf, polls left: 0
Target chip refused to enter Debug mode!
The target was reset, the application is running

Here is the jtag run with a tinipod connected but NOT powered:

E:\servopod\jtag>flash_over_jtag flash803.cfg
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: 0
JTAG DR path length: 0 (BYPASS)
IDCode status: 0
Jtag ID: 0
Debug Request status: 0
Enable OnCE status: 0, polls left: 10
Enable OnCE status: 0, polls left: 9
Enable OnCE status: 0, polls left: 8
Enable OnCE status: 0, polls left: 7
Enable OnCE status: 0, polls left: 6
Enable OnCE status: 0, polls left: 5
Enable OnCE status: 0, polls left: 4
Enable OnCE status: 0, polls left: 3
Enable OnCE status: 0, polls left: 2
Enable OnCE status: 0, polls left: 1
Enable OnCE status: 0, polls left: 0
Target chip refused to enter Debug mode!
The target was reset, the application is running


Both commands are run from the command prompt on a Windows98 machine.
The results same different from your previous post. Does this suggest a faulty JTAG cable ? The tinipod works fine by the way :-)

Regards,
Ron

[nmitech]

The TDO signal seem to be low when you connected to the TiniPod with no power, and high when not connected. So It still not convinced me if the Jtag is bad. I will request NMI Sales manager to email you the IsoMax V0.82 Srecord file for the TiniPod. If it does not flash on your TiniPod we will send you the replacement cable.

chris