Getting HardFault Handler after porting latest nRF_SDK_15.3.0 to nRF52840.

[Nirupama]

Hi Nordic,

I have ported nRF_SDK_15.3.0 to nRF52840. These changes involves USBD. So While initializing pp_usb_init(), I see it is going to some hardfault handler. Please find below image for reference. Need help in resolving this.

Thanks,

Nirupama. T

[awneil]

Nirupama said:

I have ported nRF_SDK_15.3.0 to nRF52840

What do you mean by that?

The SDK already supports nRF52840 - no "porting" is necessary!

Nirupama said:

I see it is going to some hardfault handler

That'll be because of an APP_ERROR_CHECK() which has detected an error return code from some SDK function call.

devzone.nordicsemi.com/.../40107

Nirupama said:

Need help in resolving this

In a Debug configuration, you should get useful messages on the debug log output.

Or use the debugger to step through your code to find where it's failing.

https://infocenter.nordicsemi.com/topic/ug_gsg_ses/UG/gsg/debug.html

infocenter.nordicsemi.com/.../communicate.html

[Nirupama]

Yes, It Supports nRF52840. I had this old version of SDK which I changed to 15.3.0, After the changes in USB driver, I am facing this hardfault. I tried debugging step by step and Observed that USB start is failing and accessing some restricted memory range in app_usbd_power_events_enable().

[Nirupama]

Yes, I have tried the example in PDK board and came to know that the example do not work on V0.9.0 board. So I am trying the example on revision 1, Still I don't see that nRF52 USB when I connect the board to my PC.

[Vidar Berg]

Yes, the PDK board may fail to enumerate. On the rev. 1 kit, are you connecting both of USB ports and does the LEDs indicate port "closed" or "open" when you connect to the "nRF USB"

[Nirupama]

In the rev. 1 kit, I flash using j-link connected to USB, and then connect to other port to check the logs in Teraterm.

This is my setup connected to USB for flashing the code.

This is to check my logs

[Vidar Berg]

When you said the revision 1 kit, I thought you were referring to the 52840 DK (non-preview version). Do you have a 52840 DK to test with? And on the custom board, are you able to debug the board while having the "USB module" connected to see if there are any code assertions or unexpected resets? 

[Nirupama]

I have nRF52840 PDK board of V0.9.0 where  this USB do not work, I am debugging on my custom board. According to Errata document, I see there are some problem w.r.t USB but they also provided some workaround to make it work. But SDK 15 has already that workaround, So it should work. I tried testing using RTT viewer sending logs through USB and it worked, When I try the same using Teraterm, I am not getting any logs.

[Vidar Berg]

RTT messages are transferred through the SWD lines to the debugger, not USB. But to confirm again, the USB starts working if you re-program the board with your old FW, and does not work when you program your new FW or any of the SDK examples?  

[Nirupama]

Yes, With new FW, it is not working.