This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Stopped by vector catch : nrf52840 (s340 6.1.1)

Hi,

I have looked at a number of posts with respect to this error, but I still could not work out my issue.

Board: nrf52840dk (PCA10056 2.0.1, 2020.37)
SES: 5.50a and 5.34a
SDK: 17.02

Project: Receive Bike Power via ANT+ (with the s340 softdevice), then  transmit some of it back over UART.  This is part of a larger project on the 9160dk and then Thingy91.

All was running great, I had all the ANT+ code working and then got the UART code working, as individual projects.  Then I tried to merge the code - which is when I started to get the Stopped by vector catch issue and could not proceed.  Since then I have rolled back all the changes (or I think I did), but I still get this same issue - and no sure how to proceed.

I have tried the following with no success;
* Installed the new version of SES - 5.50a
* Installed the SDK in a new directory to start fresh - nRF5_SDK_17.0.2_d674dde
* Re-Installed the ANT header files (tired 7.1.1 and 6.1.1)
* cleaned and rebuilt projects from scratch
* Erase All - from nrf connect (to makes sure all is clean)

The examples/peripheral/uart example still works, but it appears anything to do with the softdevice doesnt, as I have tried /examples//ant/ant_message_types/master/pca10056/s340 and examples/ble_peripheral/ble_app_hrs/pca10056/s340.

After loading the new projects, I confirmed they were loaded on the devices, as the memory locations (after reading with nrf connect) were different, when I switched between projects.

I am at a loss as to what to try next - could there be anything cached in SES which is causing some corruption?

regards
-brett

Parents
  • If it was working first with clean example and it if it was working with your UART code and if the problem started to appear only after merging the code, then erase all should take care to flush device memory. Do you have any other chip/kit other than the one that is showing this behavior? I do not think SES can cache as far as i know. Seems like your device might be broken? please test this with another device if you have a spare one?

Reply
  • If it was working first with clean example and it if it was working with your UART code and if the problem started to appear only after merging the code, then erase all should take care to flush device memory. Do you have any other chip/kit other than the one that is showing this behavior? I do not think SES can cache as far as i know. Seems like your device might be broken? please test this with another device if you have a spare one?

Children
Related