Hi all,
Is there a way to change the UART pins configuration to bypass the segger jlink debugger on the nRF51/52 devices? I would like NOT to use this debugger chip for budget device strategy.
Thanks in advance and best regards.
Hi all,
Is there a way to change the UART pins configuration to bypass the segger jlink debugger on the nRF51/52 devices? I would like NOT to use this debugger chip for budget device strategy.
Thanks in advance and best regards.
Don't understand your question here: segger jlink connects to the SWD and SWDCLK pins and not the uart tx/rx pins, so what exactly is this bypass business about?
Hi Matt first of all, thanks for the help. Let me try to explain a bit more our doubt. We will need to include the nordic nRF52XXXX chip into our developed device and would like to not include the segger jlink chip on it since we need to get a budget device and, as far as we know, the jlink chip is the most expensive part of the nordic nRF52 solution ( please correct us if we are wrong). We were not sure if the jlink is only used to load the S13X softdevice to the nordic chip or is it used as an interface between the ble device and the UART to comunicate to the linux host. As you told in the previous email the jlink is not used to UART data send/receive and it could be withdraw on our device solution correct?
So, there is another question: if we remove the jlink, how will we load the softdevice into the nordic chip?
I hope the explanation above could help you to undestand a bit more our doubts.
Thanks and best regards
The nRF52 SoC does not include the JLink OB. You must be thinking about the PCA10040 DK which is nRF52 + mBed with JLink OB. To load the softdevice into the nRF52 you need to expose the SWD and SWDCLK pins in your custom board so that you can connect your own Segger JLink flasher to it; or investigate using a bootloader so that you can perform OTA device firmware upgrade later on.
Thanks Matt, I will investigate how to perform a OTA device firmware upgrade. Best regards
Start with the DFU description in, say, nRF5 SDK v11.0.0/Examples/DFU Bootloader examples/BLE & HCI/UART Bootloader/DFU in the nordic semiconductor infocenter. I believe back in sdk11 there was the serial bootloader version available so that if there is a uart connection between the nRF52 and your Linux host (eg. RasPi 2 or 3) you can use the LInux host as the bootloader driver.