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

I have a nRF52832 that is periodically giving me NRF_FAULT: id=L\04 pc=0x9eca info=536935686 what does this mean?

I am using several Laird BL652 units on a project.  They contain a nRF52832.  For the most part they are working great, except I have one that only works some of the time and seems to be getting worse.  It is giving me the following error:

NRF_FAULT: id=L\04 pc=0x9eca info=536935686

I just was hoping someone could tell me what this means and whether it is something I might have caused?  (I talked to Laird and they said to come here)

Parents
  • Is the addres 0x9eca in your application code or is that in the softdevice range? Which softdevices do you use?

    Are there any other modules running the same code with this error? Otherweise, there might be something out-of-spec on just this module (e.g. quarz crystal, voltage regulator).

  • I'm not sure.  It is running a small script written in smartBasic (might be Lairds thing).  I am now suspecting a hardware issue, but I want to make sure its not something I caused.  I have not tried any other scripts on it and will likely just swap the module out for a new one.  I was hoping those error codes pointed to a better defined issue.

  • I think you should ask Laird what 'id=L\04 pc=0x9eca info=536935686' means because that ID is not generated by the Nordic SDK, and since you're using smartBasic, who's also not from Nordic's SDK, we do not really know what code is executing at that address. The same can be said for the info field. 

    Do you use the SoftDevice?

    Can you show us a dissasembly view around that PC address?

    "  I am now suspecting a hardware issue, but I want to make sure its not something I caused.  I have not tried any other scripts on it and will likely just swap the module out for a new one."
    I urge you to spends some time finding the root cause of this issue before you give up, usually, there's a fix or perfectly acceptable workaround for any given issue, we just need to identify the issue.

  • I don't know if I am using SoftDevice?  smartBasic is fairly high level scripting and it obscures all of the underlying Nordic SDK stuff.  I am using this modules to listen for IBeacons, but it does not advertise or present a GATT profile itself.  Here is what Laird said the first time:

    "We believe you'll need to submit the fault code (NRF_FAULT: id=L\04 pc=0x9eca info=536935686) to Nordic via their support portal to get the specifics of the issue.  It appears to be a fault of the stack that occurs when it is trying to access memory but beyond that we don't have a listing of the various codes that can be generated and the issue(s) that can cause them to be generated.  It is not a fault generated by smartBASIC."

    Thanks

  • I need to know exactly what SoftDevice version you're using, ask Laird.

Reply Children
No Data
Related