I tried 2 different samples in 2.9 with nRF54L15. None are working. Got some SIGTRAP inside
0x0000a4f6 in sym_KOE6VAFEEMU6WWJIX2YPZ4GY7B7U3D4BFIDGCKQ ()
Any ideas ?
I tried 2 different samples in 2.9 with nRF54L15. None are working. Got some SIGTRAP inside
0x0000a4f6 in sym_KOE6VAFEEMU6WWJIX2YPZ4GY7B7U3D4BFIDGCKQ ()
Any ideas ?
I believe I have worked on Nordic product before. First one was nRF51xx from nRF5_SDK 4 all the way up to now. I also fixed many bugs in the SDK as well. Since ncs 2.7, I wasn't able to get the sample work on the PDK and now DK.
I asked because I am trying to determine whether this is an nRF54L15 issue or an nRF Connect SDK issue, you see.
Nguyen Hoan Hoang said:Did tried flash, no results. Nothing advertised. Pressing reset button after successful flashing no result either.
Let us try something more basic:
Try the zephyr blinky sample. Does the LED blink?
Try to use "flash and erase" to program it. Sometimes "erase" helps.
One thing however. I build the sample example on an much older iMac Intel based. VSCode cannot detect the segger on this one so I use nrfjprog to flash. This works. I'll retry on the M1 when am back to the office. 2 possibilities, either build on the M1 did not work properly or the segger within VS did not work properly. Both machine was installed with the latest segger software 8.12 which has support for nRF54L
Ok, it is confirmed. Flashing from nrfjprog works on both machine. Flashing or debugging within VS with Segger NOT working.
When you say "Flashing or debugging within VS with Segger", what do you mean "Segger" here? Segger can mean multiple things, so I want to clarify.