My build number is: BN746-51

my target is a uPSD3454EV

Dear Massimo,

I just installed BN746-51 and it still works, on a uPSD3434. I noticed that 'Program' and 'Erase' are visible when you are not in debug mode, but 'Advanced Breakpoints' appears as soon as the debug session is actually launched. Did you make sure the debug session was still running when you checked the menu ?

Apart from the Advanced breakpoints, does the debugger works correctly ? Including standard breakpoints ?

Best regards,
Lionel

I confirm you that the debugger works fine.
I can execute my code step by step, but the "advanced breakpoints" menu doesn't appear.

Massimo Marolda

FYI,
I tried with a 3434 target, and the "advanced breakpoints" menu is visible.
Can you send me a patch for the 3454 ?

Thank you

Massimo Marolda

Any news ?

Massimo,

I did not have uPSD3454 to make some tests, but I doubt it comes from the device. Which boards do you use for uPSD3434 debugging and uPSD3454 debugging ? Are the optional signals TSTAT and /TERR connected ? I think they are needed for the advanced breakpoints to work.

The responsible for uPSD programming and debugging is absent until Monday 26th. When he is here, he will look at your problem more precisely.

With best regards,
Lionel

I don't have these 2 signal connected.
I'm sure that they are only usefull for a faster programming mode, not for debug.

My idea, is that RIDE is missing the 3454 from the list of "Advanced Breakpoint capable CPUs"

M.Marolda

Massimo,

you may be right, but Vincent will tell you more about all this when he is back. Thank you for your patience.

Lionel

Thank you.
Have a good week-end!
M.Marolda

Hi,

First, I confirm that the optional signals TSTAT and TERR are not related to this problem. In fact, RLink does not ever use them.

There is no such thing as a "list of "Advanced Breakpoint capable CPUs" ". In fact, all uPSDs that are able to debug (uPSD33xx and uPSD34xx) are also able to handle advanced breakpoints. See this screenshot, which was taken with uPSD3454 as target. (maybe you can make a screenshot too?)

I don't understand how it's possible that you are in debug and don't see this. Are you using a multi-application project?

Please try to open one of the RIDE examples (C:\RIDE\EXAMPLES\8051\DERIVATIVES\ST_UPSD\UPSD3400\DK3400\LED_BLINK will be fine) and try it on your board. (no need to execute, just start debug and see if there is the option) Then, change the target to uPSD3454 and do the test again. When I know the result of these tests, maybe I'll be able to understand what happens.

Also, in case the project file is corrupt or something, if you could send us your project or another project that shows the problem, then maybe we'll be able to reproduce and understand the problem. Send the complete project, with sources, headers, etc. to "support@raisonance.com".

Best Regards,

Vincent