Unknown function at 0xED9F60002

RE: Unknown function at 0xED9F60002

Maria Gilje — Fri, 19 Jul 2024 12:45:46 GMT

Hi Mushtakh,

[quote user="Mushtakh Shaikh"]3. gnu arm embedded toolchain [/quote]

Which version have you installed?

[quote user="Mushtakh Shaikh"]4. nrfjprog [/quote]

Are you able to program and run the ble_app_blinky from the command line with nrfjprog? See the command overview for nrfjprog commands here if you are unfamiliar. The flash command should look somewhat like this: nrfjprog --program program.hex -e --verify --reset

Best regards,

Maria

RE: Unknown function at 0xED9F60002

Mushtakh Shaikh — Tue, 16 Jul 2024 07:16:12 GMT

Hello Hieu,

I have installed the following applications:

1. Segger Embedded studio

2. Latest nRF SDK,

3. gnu arm embedded toolchain

4. nrfjprog

5. Jlink software

Please let me know if anything needs to be installed.

RE: Unknown function at 0xED9F60002

Hieu — Tue, 16 Jul 2024 07:07:49 GMT

Hi Mushtakh,

OK, we haven't been on the same page all this time. Edvin and I thought that you had a hard fault in execution. What you are saying is that you can't even flash the device.

Have you ensured you install all the necessary software and driver following the Getting Started pages here: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/nrf51_getting_started.html?

RE: Unknown function at 0xED9F60002

Mushtakh Shaikh — Tue, 16 Jul 2024 07:04:49 GMT

Hello Hieu,

No, I am not pausing the execution. I am able to compile the code successfully. When I click on flash download, the errors observed as "Unknown function at 0xA60 and Stopped by vector catch."

After this when I click play/debug : SES shows errors as "Unknow function at 0xF8124420" and "t-bit of XPSR is 0 but should be 1. Changed to 1"

I am unable to debug any application.

RE: Unknown function at 0xED9F60002

Hieu — Tue, 16 Jul 2024 06:59:04 GMT

Hello Mushtakh,

Are you pausing the execution and then resuming? That is including using breakpoint?

If so, then it is not possible using when BLE activity is enabled. Please refer to: application debug with softdevice

If you are not, then there is nothing that could explain what you are seeing, especially when you have tried on a second PC.

RE: Unknown function at 0xED9F60002

Mushtakh Shaikh — Tue, 16 Jul 2024 05:44:34 GMT

Hi Hieu,

Thanks for the update. I have installed the version 5.42a and re-installed the SDK 17.1.0. But still I am facing the same issues. Kindly let me know what exactly is missing in the configurations if any. I have tried other examples in the SDK, all are showing the same error. I have also tried using another laptop. But the same error is encountered. I am not able to identify the issue.

RE: Unknown function at 0xED9F60002

Hieu — Mon, 15 Jul 2024 20:33:47 GMT

Hello Mushtakh,

My apologize for the late follow-up.

I have checked your .zip files, both Nordic_DeviceDownload.zip, and DeviceDownload_Old1.zip. I can comfirm that they are indeed the same as an unmodified nRF5 SDK v17.1.0.

The issue remains that you are facing failures out of the box that have not been observed before.

The only suspect left is the build environment. I see that you are using SEGGER Embedded Studio (SES) v5.60a, which seem to work for many people. However, to be sure, could you please install a fresh copy of SES v5.42a? This is the version that nRF5 SDK v17.1.0 was released and tested with.

Hieu

RE: Unknown function at 0xED9F60002

Mushtakh Shaikh — Mon, 08 Jul 2024 06:49:48 GMT

devzone.nordicsemi.com/.../Nordic_5F00_DeviceDownload.zip

Hi Edwin,

I have downloaded the ndevzone.nordicsemi.com/.../DeviceDownload_5F00_Old1.zipew SDK from the above link that you have provided. Just compiled the code "ble_app_blinky" from the SDK examples and tried to flash in my nRF52832 DK. But still I am facing the same issues.

I am attaching the zip file here. Kindly check and please let me know if any configurations are required to be modified. Nordic_DeviceDownload is the new SDK you have just shared to me. Also I have attached the SDK that I was using as"DeviceDwonloadOld1.zip"

RE: Unknown function at 0xED9F60002

Edvin — Fri, 05 Jul 2024 21:25:53 GMT

Hello,

That is strange. Can you please try to delete the entire SDK, and unzip it again, and see if it behaves the same. If it does, did you download the SDK from here, or somewhere else:

https://www.nordicsemi.com/Products/Development-software/nRF5-SDK/Download?lang=en#infotabs

Try to avoid the "freeRTOS" samples to begin with. But the ble_app_blinky and the ble_app_uart should work out of the box. At least when using Segger Embedded Studio, since this will upload the SoftDevice automatically (the Bluetooth stack).

If unzipping the SDK once more (to make sure that no files are changed) doesn't work, is it possible for you to upload the entire zipped SDK, so that we can have a look?

And you are sure that you are using the nRF52832 DK? (it should say pca10040 somewhere on it). And that you didn't do any changes to the project settings before building and flashing?

Best regards,

Edvin

RE: Unknown function at 0xED9F60002

Mushtakh Shaikh — Thu, 04 Jul 2024 04:35:38 GMT

This is the result I am getting when I run any example code from the SDK. I feel there's nothing wrong with the code or application as it is failing with all the examples from the SDK as well.

I guess there is some issue with configurations that I am missing. Please let me know of you need any further details.

Thank you

RE: Unknown function at 0xED9F60002

Mushtakh Shaikh — Thu, 04 Jul 2024 04:27:53 GMT

Hi Edwin,

Thank you for your response.

1. In case of 0xA60, this error shows as soon as I click on debug, program didn't even reach to main(); function. I am using. I have tried ble_app_blinky example from the SDK. This is also resulting in the same.

RE: Unknown function at 0xED9F60002

Edvin — Wed, 03 Jul 2024 22:06:57 GMT

Hello Mushtakh,

If you see that the debugger stops in 0x0A60, it means that it is the hardfault handler that has triggered. This is in general a bit difficult to handle. There is a hardfault handler that you can add to your application. Please refer to the ble_app_hrs_freertos example on how to enable this. You need to enable it from sdk_config.h (by adding the hardfault-related definitions from the ble_app_freertos example), and then you need to add (the path to) some header files, and a couple of .c files.

However, you can start by trying to figure out when the hardfault handler is reached. Try setting breakpoints to check if they are reached or not. You can also use the log to help pinpointing when it happens.

Another hint is to look at the r15(pc) and r14(lr) registers when the hardfault occured.I can't tell from your screenshot what they are, but if you'd scroll a bit down in the box to the bottom right, it will show you.

This register in itself doesn't say much, and the r15 probably says 0xED9F6002. This is obviously a mistake, since this is outside the flash, but something has made the nRF think that it should execute whatever is in this address, which caused the hardfault. The r14(lr) is the link register. This will tell you the address of the function that called the address in r15.

You can use a tool called addr2line to figure out what function this was. Take whatever the r14 says, and use the command:

arm-none-eabi-addr2line -e <path to .elf file in your build folder> <0xaddress in r14 register>

You need to install the gnu arm embedded toolchain on your computer, and make sure that it is in the environment path of your computer in order to use the addr2line tool.

Please also note that you need to use the address from your latest log output. If you rebuild your application, the functions may end up in different addresses, and the r14/r15 may change.

Is there a way for me to reproduce what you are seeing using just an nRF52832 DK? Or do you need an external sensor in order to replicate the issue?

Best regards,

Edvin