• State Verified Answer
  • Replies 23 replies
  • Answers 1 answer
  • Subscribers 63 subscribers
  • Views 5245 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
  • 0

    Hi Jack

    Is the error always the same (Storage full on flash page 2)? Are you able to write anything at all on flash page 2, or is this when occuring when flash page 2 is full, and expected to go to page 3? Or is it just within page 2? There might be an issue when the application is going to the next flash page. Are you able to provide a log when this crash happens?

    Best regards,

    Simon

Reply
  • 0

    Hi Jack

    Is the error always the same (Storage full on flash page 2)? Are you able to write anything at all on flash page 2, or is this when occuring when flash page 2 is full, and expected to go to page 3? Or is it just within page 2? There might be an issue when the application is going to the next flash page. Are you able to provide a log when this crash happens?

    Best regards,

    Simon

Children
  • 0 in reply to Simonr

    Hi Simon,

    Yes, the three times I ran the test I observed the same error and believe that the 2 means its on that page but am not 100% sure. I'm not sure at what address the 3rd page starts at, but the error occurred at the location 0x42fc4 and took 19130 seconds  in the second 2 tests (the first one didn't probably due to the different saving frequency). Additionally I ran the test again, this time starting the memory address at 0x42fc4 and the test was able to run for a while but also eventually crashed. Unfortunately I wasn't there when this test encountered the error and didn't record the last location the flash was written to or how long it ran for. I am currently running another test to reproduce the error in a hope to give you more detail. If you think it would be helpful to recreate the error with the flash location starting at 0x42fc4 I will run that test as well and be sure to record the crash details this time!  

    Thanks,

    Jack

Related