SDK12.30 & software S130

RE: SDK12.30 & software S130

Håkon Alseth — Mon, 21 Jan 2019 14:19:36 GMT

Is there anything connected to your RXD line? If it is left floating, you may end up in this scenario:

https://devzone.nordicsemi.com/f/nordic-q-a/40697/how-to-resolve-the-error-nrf_error_no_mem-at-the-case-app_uart_communication_error-in-uart_event_handle

There's several suggestions on how to work around this issue in the above thread. Could you check this, and if it still does not work, please provide assertion information (line/file/err_code)?

Kind regards,

Håkon

RE: SDK12.30 & software S130

Lee — Mon, 21 Jan 2019 14:09:59 GMT

Hi Håkon Alseth:

I have checked the code and the sch ,and sure as following:

I am using S130 softdevice ,and SDk has test SDK11,SDK12.30.

in the sch, using tx as PIN 2,RX as pin 3.And no CTS & RTS.

I have modified the SDK's example ble_uart code ,

when i modify the rx pin to 3, the stack will be crashed . i am sure .

I using the 32.768 with NRF_CLOCK_LF_SRC_SYNTH define in SDK11.

the pin 3 ,not pin 2 will be caused the stack crashed.

RE: SDK12.30 & software S130

Håkon Alseth — Mon, 21 Jan 2019 07:55:55 GMT

Hi,

You should be able to change TXD to GPIO P0.02, as long as no other peripheral is using this GPIO.

Where exactly does your firmware assert/hang?

Kind regards,

Håkon