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

Parents
  • I placed the APP_ERROR_CHECK(1); into my main.c and it worked as intended. The line number and file correctly matched where it was placed. Are there any other suggestions?

  • Sorry. I realize I wasn't as clear as I intended.

    Define DEBUG in your preprocessor defines, turn off optimization, and set a breakpoint on line 73 in app_error.c.

    If it stops there, you should be able to add error_info to watch, and what APP_ERROR_CHECK() that received the err_code != 0.

    The reason to add APP_ERROR_CHECK(1) was just to see that you found the right place (73 in app_error.c).

    (screenshot from APP_ERROR_CHECK(1) in main() function)

    Set a breakpoint here, remove APP_ERROR_CHECK(1), and see if you can get any more sensible data from the weird error log.

    Best regards,

    Edvin

Reply
  • Sorry. I realize I wasn't as clear as I intended.

    Define DEBUG in your preprocessor defines, turn off optimization, and set a breakpoint on line 73 in app_error.c.

    If it stops there, you should be able to add error_info to watch, and what APP_ERROR_CHECK() that received the err_code != 0.

    The reason to add APP_ERROR_CHECK(1) was just to see that you found the right place (73 in app_error.c).

    (screenshot from APP_ERROR_CHECK(1) in main() function)

    Set a breakpoint here, remove APP_ERROR_CHECK(1), and see if you can get any more sensible data from the weird error log.

    Best regards,

    Edvin

Children
No Data
Related