This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

error code 0x057D

hi 

I am using nRF52832.i have added 3 service and and 3 characterastics to one service 

1.Peripheral service (accelormeter + gyroscope sensor) and 3 characterstics

2.battery service

3 device information service

i am using SDK14.2.0

 i connect to device and disconnect using nRF connect app,when i try to reconnect ,i cant be reconnected until i dont reprogram the device.I run code in debug mode 

i found this 0> <error> app: Error 0x057D (1405) at line 1024 in file: KGJ`hóˆ@h

though i havent added file name with this "KGJ`hóˆ@h".I am not able to understand why device cant be reconnected and error with this file name and code .

quick  response will be highly  appreciated .

Thank you

  • Hello,

    That is strange. Can you please try to enable debug mode (define "DEBUG" in your preprocessor defines) and set a breakpoint at line in app_error.c and see if it stops? Then check the file name on the file that caused the error? You probably also need to set the optimization level to 0 (-O0) in your project settings. 

     

    Best regards,

    Edvin

  • i have set optimization level 0(-O0) and c/c++ define preprocessor output

    BOARD_PCA10040 CONFIG_GPIO_AS_PINRESET FLOAT_ABI_HARD NRF52 NRF52832_XXAA NRF52_PAN_74 NRF_SD_BLE_API_VERSION=5 S132 SOFTDEVICE_PRESENT SWI_DISABLE0 DEBUG MPU9255 MPU_USES_TWI

    i set breakpoint at line 73 of function  app_error_handler() of app_error.c .It doesnot stop to breakpoint .

  • Sorry. I forgot to insert the line number, but you are correct. I meant to say line 73.

    Does it stop there if you try to enter: 

    APP_ERROR_CHECK(1); somewhere in the start of your main() function?

     

    Just to check that the error handler is set up correctly. I do not understand completely what is printed in the log. Of course, there is something weird with the name, but the error code, 0x057D also seems unknown.

     

    Best regards,

    Edvin

  • Has anyone solved this? I am seeing the exact same issue. Usually happens upon a reconnection. If I perform several disconnections followed by reconnections, it will eventually get into this state.

  • Do you get the exact same message, or something similar?

    Can you also try to add an APP_ERROR_CHECK(1); somewhere in your main() function, and figure out where in the project that tells you what APP_ERROR_CHECK(err_code) that is caught in the error handler. 

    The reason I can't tell you exactly where is because the error handler works a bit different in different IDEs.

    The jibberish message can have a couple of reasons:

    1. There is something wrong with the LOG when the error occurs, so that the message looks weird.

    2. The error log doesn't understand what function that returned the err_code passed into APP_ERROR_CHECK, and it is having difficulties to translate it to readable text.

    Best regards,

    Edvin

Related