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 ?
Hi,
Can you explain your steps in more detail? What did you do to build? What did you do to program the device? Did you try to run the device without debugging?
Regards,
Sigurd Hellesvik
create new applications using copy from sample. Using peripheral uart for example. Build then start debug. and it get stuck there. Dev on iMac with Apple silicon M1
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.
The JLink on the Devkit. VS code detect the jlink.
I see, that makes sense.
Can you clink the "Generate Support Information" and upload the file so I can check if there are some configurations missing in VS Code?
I see, that makes sense.
Can you clink the "Generate Support Information" and upload the file so I can check if there are some configurations missing in VS Code?