My OSBDM (JB16) does not work with a 9SJS16 target

[naej_gz]

hy

Code warrior IDE version 5.9,  windows XP SP3

There is no communication with the target board. A scope on BDM pin displays nothing (and no flashing LED on OSBDM)

if I change the target board for a GT8 or an AW32, The OSBDM  works fine.

if I use the JS family USB boot loader, I can erase and program  the JS16 target and drive some LEDs on the target board, but I need the debug

any suggestions ?   thanks for your help  

bye jean

[pgo]

Dear Jean,

The JS16 differs from the AW32 and GT8 in that to enter Background mode the BKGD pin needs to be low during the power on reset. The reset pin cannot be used.  The OSBDM doesn't handle this very well (depends on version).

This may account for the different results.

You can try the following to check this:

Hold BKGD low while applying power to the chip (without the OSBDM connected)

Connect the BDM and see if it now works.

You can leave the BDM connected if you are brave but it might damage the driver chip in the worse case.

If this works I would recommend upgrading to USBDM which has a software solution for this problem.

bye

[naej_gz]

dear   pgo

My first problem was actually the reset.

A low state on BKGD while powering did nothing, but since you told it was a lack of reset pin, I added SOPT1_RSTPE =1 (to get a reset pin) in my test program using the USB bootloader.

I now have a new problem, the OSBDM have the communication, but it cannot download he code to the target.

the error message is :   error while loading diadgnostics algorithm to target system

                                            the chip may be secured, or the derivative selected may be wrong

I did nothing to secure the chip, and i'm sure I work with a JS16

can you help ?

thanks

[rocco]

Hi Jean,

I have found that when I have had communication problems with the BDM, that the MCU (not a JS16) end up secured. It would happen if the chip was erased but not reprogrammed.

Simply select the "Unsecure and erase" (I think that's what it's called) in the debugger's menu.

Mark

[naej_gz]

SOLVED !

the chip was secured !    many thanks for the two of you

I guess the chip was secured while erasing with the USB bootloader setting the SEC01 and SEC00 bits 

bye jean