i have 2 setups, one on a pca10040 running sdk 14.2.0 s132 and the other one on a pca10028 clone running sdk12.3.0 s130 with a 51822_xxaa mpu
the ble_uart examples from both sdks got the following equal modifications
replaced uart code with my own (isr support) along with my own queue-ing classes
getting the tx data from my tx fifo and sticking it into the ble_nus_string_send funct is at a 5 ms period handled in main with a max payload of 20 bytes
my firmware queues (tx) up strings to a nexus 7 at a 30 ms period on the 51822 and at a 100 ms period on the 52832 ... yes, the 52832 can not handle a 30 ms data stream period
the periodic data strings start with a length of 1 incremented by one up to a max of 90 chars followed by a decrement by one, and again ... this provides a nice pyramid shape data scroll and any misses are visually easy to spot
the same kind of pyramid data is also sent by the nexus 7 to the ble device ... the max speed seems determined by the capabilities of the nexus 7 and maxes out at 100 ms
the 51822 ble_nus_string_send appears to exhibit err_code returns of NRF_ERROR_BUSY and BLE_ERROR_NO_TX_PACKETS, in which case i repeat the previous data on the next 5 ms ble_nus_string_send period and everything seems fine ... i can live with some data errors on long test lines
the slow problem child seems to be the 52832 s132 based device where the ble_nus_string_send funct returns either NRF_ERROR_BUSY or unknown error 0x13
why do i not get a BLE_ERROR_NO_TX_PACKETS and instead this to me unknown err 0x13 which appears to be some like missing resources or similar
both projects are literally almost the same, except where the s132 vs s130 dictate differences
what's wrong with the, should be faster, cortex-m4 52832 setups
one note on the side :
why is there, this to me significant, code difference in the ble_nus_string_send funct
52832 hvx_params.handle = p_nus->tx_handles.value_handle ;
51822 hvx_params.handle = p_nus->rx_handles.value_handle;
what is it now ... tx or rx ... ble_nus_string_send woudd imply tx to me
any help on the slow s132 based 52832 setup would be highly appreciated
cheers Klaus