ble_app_uart with RTT won't load

RE: ble_app_uart with RTT won't load

etamar — Thu, 15 Sep 2016 12:51:53 GMT

yes, and the listing tab looks exactly like in the photo you uploaded (except from "C Compiler list" that is not even clickable)

RE: ble_app_uart with RTT won't load

Susheel Nuguru — Tue, 13 Sep 2016 06:34:02 GMT

sorry for late response, did you attach full .map file? seems like you ripped off the important data with memory addressing map to functions and data

RE: ble_app_uart with RTT won't load

etamar — Thu, 08 Sep 2016 07:14:20 GMT

something is not clear to me with the map file, it doesn't look like it is described. I attached it to the end of the question. I am using softdevice s132 version 2.0

RE: ble_app_uart with RTT won't load

Susheel Nuguru — Thu, 08 Sep 2016 04:48:06 GMT

Can you attach you. Map file and tell me which softdevice version is flashed to device?

RE: ble_app_uart with RTT won't load

etamar — Wed, 07 Sep 2016 20:34:30 GMT

The markings are: N52832

QFAAB0

1611AN

RE: ble_app_uart with RTT won't load

Susheel Nuguru — Wed, 07 Sep 2016 12:05:32 GMT

maybe you are having a chip with smaller flash and/or ram. Which chip are you using, can you tell me the laser markings on the nRF chip.

RE: ble_app_uart with RTT won't load

etamar — Tue, 06 Sep 2016 18:24:06 GMT

Sorry for the long time to respond, i did change the irom and iram values as written there, but the error doesn't disappear. The example in this tutorial has RTT files and was built to the dk with no errors: devzone.nordicsemi.com/.../

RE: ble_app_uart with RTT won't load

Susheel Nuguru — Tue, 30 Aug 2016 11:13:47 GMT

Then the .map file will be generated everytime the compilation is successful.

RE: ble_app_uart with RTT won't load

etamar — Mon, 29 Aug 2016 18:48:10 GMT

thank you for the quick replay, after i closed the .map file i cant find a way to generate another(needed in the post you refered), how is it done?

RE: ble_app_uart with RTT won't load

Susheel Nuguru — Mon, 29 Aug 2016 12:37:59 GMT

The first message just tells you that the .map file is open in your editor and after you compile it, it has generated a new .map file and asking you to reload that in your editor. Close the .map file in your editor and it wont give you this message anymore.

The second message might happen if your IROM settings does not match the softdevice. Please check the correct softdevice release notes to find what to put in IROM settings. this post even though not latest will give you some info.