I am working with NRF52840 chip with SES 6.4. My application was initially developed for nrf52832 but ported to 52840 and stopped by vector catch in debug mode. I had no issue to build it though. And I did an experiment with blinky example to see if the issue persists. I got same issue. Please help me. Thanks.
Hello,
I was not able to reproduce the fault with the project you uploaded. I also tested the hex file from your build (/blinky/pca10056/blank/ses/Output/Release/Exe/), and the LED toggled as expected. Do you see the LEDs toggling if you flash and reset without starting a debug session?
This is probably not directly related to the issue you are facing now, but I recommend downgrading Segger Embedded Studio to version 5.x, as version 6.20 and later have known compatibility problems with the SDK. From the SDK release notes:
The following toolchains/devices have been used for testing and verification: - ARM: MDK-ARM version 5.25 - GCC: GCC ARM Embedded 9.2020-q2.major - IAR: IAR Workbench 7.80.4 - SES: SES 5.42a
Best regards,
Vidar
I flash it thru SES. Normal mode means flash and run but not debug mode. Wait… I think the chipset is 52833. The chipset was purchased few years ago and flipped and soldered into perforated PCB. I could not tell what it was but highly likely 52833. I will get back to you. If 52833, do I need to use 10040 or 10056 board file?
I flash it thru SES. Normal mode means flash and run but not debug mode. Wait… I think the chipset is 52833. The chipset was purchased few years ago and flipped and soldered into perforated PCB. I could not tell what it was but highly likely 52833. I will get back to you. If 52833, do I need to use 10040 or 10056 board file?
