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().

[Vidar Berg]

Are you using the Softdevice, and in that case, are you enabling the events through the sd_power_* APIs? Accessing POWER registers directly will lead to a hardfault if you have the Softdevice enabled.

[Nirupama]

Soft device is not enabled, Now I am able to initialize the USB without any hard faults but when I test in Teraterm, It is not recognized as nRF52 USB device. So is it because of USBD changes in nRF_SDK_15.3.0, Should we update the Nordic USB driver?

[awneil]

Nirupama said:

when I test in Teraterm

recognising the USB device is done by Windows; not Teraterm.
Teraterm (or any other app) just sees a COMx: device - it neither knows nor cares whether that's a real RS232 port, a modem, USB, or anything else.

You need to be looking in the Windows Device Manager ...

[Nirupama]

Yes, I checked it in the device manager, It is recognized as USB device. But in order to test the logs, I should check in Teraterm, where it should be identified as nRF USB device. I am not getting that.

[awneil]

Nirupama said:

It is recognized as USB device

but is it recognised as a COM: port?

Nirupama said:

in Teraterm, where it should be identified as nRF USB device

No, it shouldn't.

Again, Teraterm  (or any other app) just sees a COMx: device 

[Nirupama]

I have 2 apps, which is older SDK and one is new SDK. When I flashed with older one, in Device manager, I am able to identify it under USB controllers as USB composite device and under ports as USB COM PORT 14. But with latest driver, Under USB controllers, device is identified as J-link driver and USB composite device and Under Ports as "CDC Port"

[awneil]

but what Teraterm, et al, needs is a COMx: port!

There should be a COM port in the CDC device properties ... ?

You know how to post screenshots ...