unknown function at 0x000008C8

RE: unknown function at 0x000008C8

Einar Thorsrud — Tue, 01 Feb 2022 07:37:45 GMT

Hi,

[quote user="Dipak"]How to set the project in DEBUG mode ?[/quote]

The example project here does not have a DEBUG build configuration (probably because of size constraints). So in this case you will have to disable optimization yourself, in addition to define DEBUG (hopefully that will fit in this small device).

[quote user="Dipak"] I have disabled the optimization level to none but the result is the same as it was! [/quote]

Then it should be good and you should be able to use a debugger to see what happened by debugging in the error handler. See An introduction to error handling in nRF5 projects. In this case, with DEBUG defined and optimizations you should be able to get this. You may need to do this though:

Either place a breakpoint in the error handler, or simply let it run to NRF_BREAKPOINT_COND. Then add p_info to watch. Then make an expression of (char*)<address you find for p_file_name when inspecting p_info>. That should look something like this:

As you see, here there is an error on line 0x2a2 (674) in nrfx_spim.c. You should be able to use the same approach.

(If you have trouble with this somehow, then an alternative could be to inspect every return value you feed into an APP_ERROR_CHECK() with your debugger.)

RE: unknown function at 0x000008C8

Dipak — Mon, 31 Jan 2022 18:18:25 GMT

Also, I have disabled the optimization level to none but the result is the same as it was!

RE: unknown function at 0x000008C8

Dipak — Mon, 31 Jan 2022 18:16:56 GMT

Hi Einar,

Thanks for the reply!

As I look in my project option there are two options are available one of them is release and the other is common

How to set the project in DEBUG mode ? [ Please have a look at the below image ]

Best and regards,

Dipak

RE: unknown function at 0x000008C8

Einar Thorsrud — Mon, 31 Jan 2022 06:55:24 GMT

Hi,

Your topic "unknown function at 0x000008C8", and this is within the MBR which is part of the SoftDevice distribution and only provided in binary. So that will always be unknown as you don't have the source code for it.

[quote user=""]seggar embedded studio STOPS working[/quote]

In what was does it stop working? Please elaborate.

[quote user=""]- I have placed DEBUG preprocessor inside the preprocessor and placed breakpoint at app_error_fault_handler inside app_error.c but it is not giving me any information like where the program is stuck.[/quote]

Did you also disable optimizations? That is needed in order to make sense of things when you debug, as without it optimization will cause the actual binary code to be quite different from the C code you are looking at. If you have based your application on a SDK example, simply select the "Debug" build configuration as that will also disable optimization (in addition to define "DEBUG"). If not, select this your self under Code Generation -> Optimization Level. For debugging, this should be "None". As a last point, remember that you cannot continue from a breakpoint or pausing/stopping when using a SoftDevice, as the SoftDevice will assert in this case. So if you want to step in the code, you should instead do that with a breakpoint, then move the breakpoint and reset to go further the next time. With that, you should be able to get more out of your debugging.