Regarding the Uart not working as per intended in release mode... or without the debugger connected to the chip

[Sijeo Philip]

Hi , 

In my application .. I have define two custom characteristics one with write permission and other with read + notify permission... 

Whenever a value is written to the characteristics with write permission it is transmitted over uart to my MCU as it is..

The string recieved by the  MCU is processed and the appropriate response string is sent  back to the nrf52810 chip over uart, which inturn updates the characteristics with read + notify permission.

Above mentioned functionality  is working fine when the chip is connected to my Debugger/Programmer (nrf52840 DK ) and the application is run in Debug Mode..

but when Debugger is disconnected and board is power cycled...  I could write data to write characteristics and it is written as expected over uart to my MCU, My MCU is forming the response and sending the same over UART to NRF52810 chip  (This is been verified physically over uart lines and also reading my MCU UART registers in Debug Mode)

the Data received over the UART by the NRF52810 chip as response to  is not updated over the read  + notify characteristics... 

Can you please help to understand, where should i look or how should I overcome this issue.

Please find enclosed code for your review and comment... suspect it has something to do with the timing, but not sure how to work around on the same, as it seems to work perfectly fine when the application is run over my PC with the debugger connected to the NRF52810 chipset

Thanks and Regards

Sijeo Philippca10040e.rar

[Sijeo Philip]

Hi, We purchased a new board nrf52840 DK PCA10056 v 2.0.1 to use it as sniffer.. As i connected after unboxing using nrf Connect Desktop to flash the sniffer firmware.. it was showing as incompatible board... further to which i tried updating the board J-LINK OB MCU firmware from Nordic website (i.e. J-Link OB-SAM3U128-V2-NordicSemi 170724 ) and after that it  stopped connecting as well (i.e. no longer J-LINK interface was appearing)

 In an attempt to resolve the same i tried flashing the new bootloader software

i.e. (0244_sam3u2c_bootloader_update_0x5000. bin) from embed

by using IF BOOT RESET button ,after which it is no longer in opens in boot loader mode on pressing the IF-BOOT button and power cycling the board... it opens as MAINTENANCE drive instead of BOOT LOADER drive... 

Can you please help recover....i have a different board of nrf52840 PCA10056 v1.0.0 which works very well with the nrf Connect without any problem.. 

Please help to understand how i can recover this board and use the same as sniffer.

[Jørgen Holmefjord]

Hi,

I have never updated the bootloader of the interface MCU. Does the board mount as a JLINK or MBED device if you do _not_ hold the IF/BOOT button when turning on? If not, try dropping the J-LINK OB MCU firmware to the MAINTENANCE drive.

Best regards,
Jørgen

[Sijeo Philip]

Hi, 

With regards to the mobile apk getting disconnected I have collected some logs from the soc ... Please find enclosed for your review and advise.. 

the mac id starting with F7:... is the nrf52810 device... there were some instances where it showed failed to decrypt due to bad MIC... could you please help understand the same... There were also some empty PDUs send yukee_lock_ble_log1.pcapngyukee_lock_ble_log.pcapng

This time somehow the mobile didn't disconnect automatically as before... request you to help me make sense out of these logs

[Sijeo Philip]

Hi, 

Tried dropping the JLINK_OB_MCU firmware to the MAINTENANCE drive.. with no luck... can you please help recover the same. Is there something different I need to do as the board is nrf52840 DK PCA10056 v 2.0.1

[Jørgen Holmefjord]

You may have bricked the device when trying to load the bootloader update. I do not know what this binary contains or how it will affect the board. You should check with the source where you got it. We do not provide interface MCU bootloader updates or recommend this for our customers. You may need an external debugger to recover the board.