9S12XDP512 BDM debug problem

[sfb]

Hello,

I am working with 9S12XDP512 and when connected to BDM there are some warnings and errors on debug screen. I checked the pins and see that :

VDD1 : 2.5V

VDD2 : 2.5V

VDDX2 : 5V

XCLKS : 5V (pulled high)

BKGD : 5V (pulled high)

VDDR1 : 5V

RESET : 5V (pulled high)

TEST : GND

VDDR2 : 5V

VDDA, VRH : 5V

VREGEN : 5V (pulled high)

VDDX1 : 5V

I see these warnings one ofter another:

first : "Loading a new application will stop the exacution of the current one"

and second : "Error Elf Loader

                       Error while writing to FFFE ... 101FE"

and last : "Failed to load

                 "C:\ ..... \P&E_Multilink_CyclonePro.abs"

And after all of these processor doesn't work. Why?

[stevo10]

Hello,

Could it be the case the device is secured? Have you tried an unsecure script on the device?

Regards,

Stevo

[sfb]

Yes, I tried it but nothing changed.

[JimDon]

First "Loading a new application will stop the execution of the current one" is just a warning, and can be turned off on one of the config panels - Detect target is running or something like that.

Tried "it" - tried what - did you down load P&E Unsecure and run it ?

[sfb]

No I didn't download anything for unsecure process, I did it from debugger menu.

But I see another thing:

I am using expanded mode MODC = 1, MODB = 0, MODA = 1 (1 is pull up and 0 is pulled low). And PK7 is high. When I remove the pull up resistor from MODA pin processor is running. Can someone explain me what is wrong with selecting Normal Expanded Mode like above hardware configuration (Because I think that there is a problem when starting Normal Expanded Mode and there is no problem for Normal Single Chip Mode)?

Best regards

[kef]

Debuggers normally expect target being configured for normal single chip mode. MODC(BGND) pulled high, MODA and MODB pulled low. MODC:MODB:MODA=100.

To get into active background mode (special single chip mode), debugger pulls MODC low and pulses reset low. Target gets reset into special single chip mode, 000.

Now, if your target is set for normal expanded, 101, then hitting connect in debugger will also make MODC pulled low and target will be reset. Thats mode 001, Emulation Single Chip. I guess it's not what you want.

I think you need to jumper your target for normal single chip and enable expanded memory at runtime. You may also try using hot-plugging mode, check hiwave->P&E multilink settings.