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

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

Nirupama — Wed, 02 Oct 2019 06:52:11 GMT

Yes, With new FW, it is not working.

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

Vidar Berg — Wed, 02 Oct 2019 06:48:43 GMT

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?

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

Nirupama — Wed, 02 Oct 2019 05:39:36 GMT

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.

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

Vidar Berg — Tue, 01 Oct 2019 13:15:35 GMT

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?

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

Nirupama — Tue, 01 Oct 2019 08:38:21 GMT

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

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

Vidar Berg — Tue, 01 Oct 2019 07:58:39 GMT

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"

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

Nirupama — Tue, 01 Oct 2019 06:46:09 GMT

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.

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

Vidar Berg — Tue, 01 Oct 2019 06:39:31 GMT

Have you tried the default USB CDC ACM Example in SDK 15.3.0 to see if that works? Drivers should be installed automatically if you have Windows 10.

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

Nirupama — Fri, 27 Sep 2019 14:52:57 GMT

Yes....What screen shots you want?

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

awneil — Fri, 27 Sep 2019 14:51:01 GMT

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

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

Nirupama — Fri, 27 Sep 2019 14:43:00 GMT

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"

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

awneil — Fri, 27 Sep 2019 14:18:26 GMT

[quote userid="74060" url="~/f/nordic-q-a/52662/getting-hardfault-handler-after-porting-latest-nrf_sdk_15-3-0-to-nrf52840/212320"]It is recognized as USB device[/quote]

but is it recognised as a COM: port?

[quote userid="74060" url="~/f/nordic-q-a/52662/getting-hardfault-handler-after-porting-latest-nrf_sdk_15-3-0-to-nrf52840/212320"]in Teraterm, where it should be identified as nRF USB device[/quote]

No, it shouldn't.

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

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

Nirupama — Fri, 27 Sep 2019 14:11:44 GMT

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.

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

awneil — Fri, 27 Sep 2019 13:54:25 GMT

[quote userid="74060" url="~/f/nordic-q-a/52662/getting-hardfault-handler-after-porting-latest-nrf_sdk_15-3-0-to-nrf52840/212308"]when I test in Teraterm[/quote]

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

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

Nirupama — Fri, 27 Sep 2019 13:42:30 GMT

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?

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

Vidar Berg — Fri, 27 Sep 2019 12:43:01 GMT

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.

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

Nirupama — Fri, 27 Sep 2019 10:54:29 GMT

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

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

awneil — Fri, 27 Sep 2019 09:07:11 GMT

[quote userid="74060" url="~/f/nordic-q-a/52662/getting-hardfault-handler-after-porting-latest-nrf_sdk_15-3-0-to-nrf52840"]I have ported nRF_SDK_15.3.0 to nRF52840[/quote]

What do you mean by that?

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

[quote userid="74060" url="~/f/nordic-q-a/52662/getting-hardfault-handler-after-porting-latest-nrf_sdk_15-3-0-to-nrf52840"]I see it is going to some hardfault handler[/quote]

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

[quote userid="74060" url="~/f/nordic-q-a/52662/getting-hardfault-handler-after-porting-latest-nrf_sdk_15-3-0-to-nrf52840"]Need help in resolving this[/quote]

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