• State Verified Answer
  • Replies 23 replies
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 5192 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 226163
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

RTC1_IRQHandler(); Error

jackiemoon98

Hi all,

I am debugging a program after compiling with no errors using the SDK 15.2.0 on a windows laptop and nRF52840 board. The program was designed to save 8 bytes of data to flash every 50ms for 3 days using fstorage. There should be enough storage on this particular board to allow for this, however I have not had a successful 3 day run yet. The latest bug in the code occurred at "void RTC1_IRQHandler();" in the call stack and about 90 minutes in with an error value of what looks to be 0x00026FC4, which doesn't make sense, at least not to me. I understand this has something to do with the timers, which I use to call the fstorage functions every 50ms. However, as a beginner programmer, I am unable to assess any issues at a lower level. Could someone give some suggestions as to what may be causing this issue?

Thanks,

Jack

Parents
  • +1

    Hi Jack

    It seems like you have been changing quite a few things within the files, and all these additional errors seems to be due to the changes made in the SDK files. This makes it almost impossible for us to find the error, and the project as a whole will get harder to work with. I suggest you go back to where you were. The point where you got consistent errors.

    After you've done this, please ensure that you've set DEBUG in the preprocessor defines like this:

    1. right click your project in SEGGER and click Options.
    2. Make sure your configurations are set to Common.
    3. Click the Preprocessor Definitions.
    4. Enter DEBUG into the Preprocessor Definitions, and click OK until you are back to your project.

    When this is done, use the unmodified error handler to check what error code you get when encountering the original error.

    Best regards,

    Simon

Reply
  • +1

    Hi Jack

    It seems like you have been changing quite a few things within the files, and all these additional errors seems to be due to the changes made in the SDK files. This makes it almost impossible for us to find the error, and the project as a whole will get harder to work with. I suggest you go back to where you were. The point where you got consistent errors.

    After you've done this, please ensure that you've set DEBUG in the preprocessor defines like this:

    1. right click your project in SEGGER and click Options.
    2. Make sure your configurations are set to Common.
    3. Click the Preprocessor Definitions.
    4. Enter DEBUG into the Preprocessor Definitions, and click OK until you are back to your project.

    When this is done, use the unmodified error handler to check what error code you get when encountering the original error.

    Best regards,

    Simon

Children
  • 0 in reply to Simonr

    Hi Simon,

    I did everything you said to and instead of returning an error code the program ran until the desired flash region, 0x3f000 - 0x57000, was full! It even continued to run after this and I was able to confirm this with multiple tests.

    Could adding debug to the pre-processor definitions have fixed the bug? Even if not thank you so much for all the help I really appreciate your time! I can change what I have marked as the answer if you think adding debug to the definitions was the solution.

    Thanks,

    Jack

Related

core_v2_widget.Hide()