Overlapping hex files

Hi I did fixed this problem. But for now I have another problem for the engineer. 
I want to use the usbd_ble_uart example. I get an error in the ble_nus.c.

blcm_link_ctx_get(…. p_link_ctx_storage,….)

No member named p_link_ctx_storage.

Hello,

That's strange, the project should compile without errors. Any chance the ble_nus.h/ble_nus.c sources may been modified? I would suggest that you try again with a new SDK copy just to be sure.

Best regards,

Vidar

Meanwhile I did the downgrade, but after building I got this error. Am I missing something?

user115974 said:

Hi, I did disabled retarget and removed RTT_Syscalls from my project, but that's not enough? Should I downgrade it?

You also need to set the IO output to 'RTT' in your project as explained in Einar's post. 

user115974 said:

Meanwhile I did the downgrade, but after building I got this error. Am I missing something?

Your project is including the wrong version of the thumb_crt0.s file for some reason. What is the path to file (you can hover the mouse over the thumb_crt0.s tab to see it)?

user4240 said:

You also need to set the IO output to 'RTT' in your project as explained in Einar's post. 

Yes, this was the step I forget. But when I’m doing this I don’t see anything printed on the uart com-port. Is that true.

user4240 said:

Your project is including the wrong version of the thumb_crt0.s file for some reason. What is the path to file (you can hover the mouse over the thumb_crt0.s tab to see it)?

It takes it from the ses 6.22. I didn’t erase the full application in case it wouldn’t work with the downgraded version.

The NRF_LOG_INFO isn’t printed on the uart com port but if I send something after connecting it is visible on the uart. The NRF_LOG_INFO is only visible in the debug terminal.

ps: this is an example of the ble_app_uart. It is the same problem I can’t fix

user115974 said:

It takes it from the ses 6.22. I didn’t erase the full application in case it wouldn’t work with the downgraded version.

It needs to come from the same version you use to build the project. Pleasedo a clean build and see if includes the correct version.

user115974 said:

Yes, this was the step I forget. But when I’m doing this I don’t see anything printed on the uart com-port. Is that true.

Yes, this is the limitation I mentioned in the other post. If you need printf to be redirected to UART, then you have to downgrade SES.

user115974 said:

The NRF_LOG_INFO isn’t printed on the uart com port but if I send something after connecting it is visible on the uart.

NRF_LOG_INFO() will only print the debug messages to RTT as the UARTE0 is not available for logging in this example (UART/Serial Port Emulation over BLE)

user115974 said:

It takes it from the ses 6.22. I didn’t erase the full application in case it wouldn’t work with the downgraded version.

It needs to come from the same version you use to build the project. Pleasedo a clean build and see if includes the correct version.

user115974 said:

Yes, this was the step I forget. But when I’m doing this I don’t see anything printed on the uart com-port. Is that true.

Yes, this is the limitation I mentioned in the other post. If you need printf to be redirected to UART, then you have to downgrade SES.

user115974 said:

The NRF_LOG_INFO isn’t printed on the uart com port but if I send something after connecting it is visible on the uart.

NRF_LOG_INFO() will only print the debug messages to RTT as the UARTE0 is not available for logging in this example (UART/Serial Port Emulation over BLE)