We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
J-Link V6.12d API Warning Debugger problem discovered: The debugger has set two breakpoints at the same address xxxxxx. ------
I use Tessy to do unit test work with Keil uvision. The breakpoint is set by the test software Tessy at its communication function. In fact, it can run well at Keil Simulator without Jlink. And now this warning appears with Jlink connecting. Anyway, If I keep clicking the OK of the warning to go on the test, it can go to the last.
I wonder is there any suggestion to solve this , or how can I just simply disable the warning?
... The breakpoint is set by the test software Tessy
Sounds like you need to be discussing this with the Tessy people, then?
HA They say ask Keil... And there was a question here however without an answer: devzone.nordicsemi.com/.../keil---debugger-set-two-breakpoints-at-same-address
That's getting to be a bit of a reach.
Most probable is that the test tool is trying to set break-points to different lines in the code, but either those lines don't generate code, or the optimizer re-arranges or folds things in such a way that the two requests fall on exactly the same code address. If the tools is trying to do this as a way of single stepping or profiling, then it really should be sufficiently aware that the line-to-address translation isn't always going to result in a unique address, or in-order.
You should discuss with the Tessy developers what their expectations are, and if they have sufficient visibility to see that they are trying to set two breakpoints at the same address.
Keil has direct support contact points, use those, not the forum.
You do realise that this is a user forum - it is not the way to contact Keil ?
See: http://www.keil.com/forum/ - look at the first bullet point under 'Note' ...
Andrew, you and I come from a place when we learned to read and ask coherent questions, and could do math with log and sine tables when we were eleven. This isn't that world..
Dear LI CL,
You may turn on TESSY's low level logging (Help->Logging...->Low Level). Look for the following messages:
[uvscInitialize] Waiting 0 seconds before setting the sync breakpoint 00:00:02.91 [T->] CUv3Client::DBG_CREATE_BP() 00:00:02.91 [-->] [DBG_CREATE_BP ] [(BKPARM) Type:Exec Access Size:0 Count:1 Expr:tslows_sync] 00:00:02.91 [-->] [DBG_CREATE_BP ] [00000434 00002014 00000414] 00000001 00000001 00000000 0000000C 00000000 6F6C7374 735F7377 00636E79 0028FB44 0028FA54 00000000 723316AF 00730670 FFFFFFFF 0000001C 00000000 00000001 00000000 0028FA9C 0028FB8C 00000000 0028FA80 00000000 77CFEB35 0028FA80 723112FD 00005DD2 77DCF901 723317CD 00000100 00000001 0028FAA4 00000000 0028FB58 0028FB48 0028FC24 00000010 FFB3B4C0 FFFFFFFF 00000134 00730670 00000000 00000000 0028FBA8 72336D20 0028FBA8 72336D77 723316AF 72336B58 C9D64CA8 020F4850 00000000 00000000 00000000 0000001C 00000000 00000000 0028FB54 0028FC0C 0028FB1C 00000000 723316AF 00730670 FFFFFFFF 0000001C 00000000 00000001 00000000 0028FB64 0028FC54 00000000 0028FB48 00000000 77CFEC0D 00000000 00000001 00370000 00000001 FF676980 77DCF951 723342A3 00000134 00000100 00000000 00000000 0028FBA4 00012017 0028FB8C 00000010 00000000 7233432A C9D64CE0 00000000 020F4850 00000000 0028FC18 00000001 00000000 00000020 72352F67 BBCDDBA8 00000000 00000001 00000000 00000100 00730670 00000000 00000000 0028FBA4 00000000 0028FB7C 00000000 0028FFC4 72352F67 BBCDF430 FFFFFFFE 7233432A 75EB689F 00000134 0028FC18 00000001 0028FC30 0028FC3C 75EB2FAC 020F4850 020F4850 75EB68A8 00000000 00000000 0028FF30 00000001 0028FD5B 020F4760 00000000 0028FD98 6E40D60D 00000001 0028FD5B 00000001 00000000 0028FD5C 00000010 00000000 006E0000 00743210 00000001 00000134 01370174 0028FBA8 00370150 0028FD3C 006E00C4 006E5C80 FFFFFFFE 006E0000 006E0150 00000034 00000040 006E5C80 00743208 0028FD60 0028FD78 000007FF 0028FD08 77E24DCD 00000003 FFFFFFFE 000007FF 77DE2C45 00000000 02000002 0000077F 00000000 0072C4A8 01F37DD0 0028FD18 00000000 00370000 00000000 006E5C80 C9D5AB38 0028FD0C 00743210 006E00C4 00000020 00001BBB 00000000 01000000 77DCF901 760615CE 000001A0 00000000 76061601 C9DBA70F 00000000 000001A0 0028FF30 00000024 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 77DDE770 006E0000 00000000 0028FD14 0A28FD68 00000000 000F4240 00000001 00000046 76061601 75C61194 00000000 77DCFA22 7605C585 000001A0 000001A0 0028FD98 75C61408 000001A0 00000000 0028FDC8 6E40D832 000001A0 FFFFFFFF 01F37E18 1000D1C3 00000140 0072BB28 007427CC 000001A0 77DCFDC1 76063D3C 00000000 76063D68 C9DBA44B 00000000 00000000 0028FF30 00000024 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 40000024 0028FDD0 0028FE44 0028FFC4 76087270 BFFBD6AB 00:00:02.96 [-->] [GEN_CPLX_COMPLETE ] 00:00:02.96 [-->] [GEN_CPLX_COMPLETE ] [00000020 0000000C 00000000] 00:00:02.99 [<-T] CUv3Client::DBG_CREATE_BP() = UVSC_STATUS_SUCCESS
This is where TESSY sets a breakpoint. For normal unit tests without interaction these messages should occur only once. For interactive debugging a further breakpoint is set at your test object.
Hi Ben, Thanks for your reply. I have noticed the log, just the same as your reply. But I didn't find a further breakpoint as you say. And do you have ways to avoid the warning?
Hi ChangLei,
I heard that our support could help you. Still wonder who told you that you should ask Keil. Normally we contact Keil if there is a problem that we cannot solve and, where applicable, arrange a WebEx session with all parties.