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

    I have consulted with one of the gurus here, and first, just stow away the ACL idea for now. Next, could you add DEBUG in preprocessor defines and enable logging. This way you should be able to find out which APP_ERROR_CHECK(err_code) is returning and what exact err_code it is. I'm not so sure it describes the flash page and error, it could be a multitude of things.

    You should probably increase the saving frequency when testing by quite a bit, so you won't have to wait for hours each time.

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi Simon,

    I have been using logging this whole time and I am pretty sure I have been in debug mode.  However, I noticed that even with the debug flag on, debug was still turned off in the app_error_weak.c file. After looking into this, it appears to be a known issue with the sdk 15.2.0 in segger, but it is only visual. Unfortunately in my case, the program would still encounter NRF_BREAKPOINT_COND. After manually moving the lines from the #ifndef DEBUG to the break point, I am still running into inconsistent failures. Unlike before, the flash initialization is no longer working as it will always hard fault, as well as the adc function will get stuck in a loop. These bugs are even stranger as I never changed anything in the ADC timer, or anything other than the saving period in the fstorage timeout handler. Is it possible that there could be an issue with the hardware? I apologize for the off-topic errors, but I was unable to debug these issues and do not have any other resources to help....I hope these errors are all related. 

    However, if I did in fact have logging and debug set up properly before, I would consistently get the 2006 error.  

    Thanks again for your time,

    Jack

Reply
  • 0 in reply to Simonr

    Hi Simon,

    I have been using logging this whole time and I am pretty sure I have been in debug mode.  However, I noticed that even with the debug flag on, debug was still turned off in the app_error_weak.c file. After looking into this, it appears to be a known issue with the sdk 15.2.0 in segger, but it is only visual. Unfortunately in my case, the program would still encounter NRF_BREAKPOINT_COND. After manually moving the lines from the #ifndef DEBUG to the break point, I am still running into inconsistent failures. Unlike before, the flash initialization is no longer working as it will always hard fault, as well as the adc function will get stuck in a loop. These bugs are even stranger as I never changed anything in the ADC timer, or anything other than the saving period in the fstorage timeout handler. Is it possible that there could be an issue with the hardware? I apologize for the off-topic errors, but I was unable to debug these issues and do not have any other resources to help....I hope these errors are all related. 

    However, if I did in fact have logging and debug set up properly before, I would consistently get the 2006 error.  

    Thanks again for your time,

    Jack

Children
No Data
Related
Terms of service