Uart communication between nrf52832 dev kit and another MCU.

Good Morning people.
I'm developing a module with the soic nrf52832 and I'm having doubts about the electrical schematic of the UART communication with another MCU.
I analyzed the electrical schematic of the PCA10040-nRF52832 development kit and realized that only pins P0.05(RTS), P0.06(TXD), P0.07(CTS) and P0.08(RXD) are used for serial communication.
In my case I'll have to use all these pins or just need to consider the TX and RX pins.
And for what server the RTS and CTS?

My other question is if it is possible to use the development kit as a recorder of the module that I am developing, I saw that there is a Debug in pins?

Parents
  • Hello,

    nrf5xfanboy is correct about the CTS/RTS pins - they are most useful these days if you will be communicating at very high speeds with a system that is not always ready to receive the incoming data, for instance.

    I am not sure if I understood your 'recorder' question correctly but you can indeed use the development kit as a debugger for your other SoC through the SWD interface. I have attached an image that shows how this can be done:


    For convenience I would recommend that you program your DK with the regular 'blinky' example before you use it as the debugger for your other SoC, so that you can easily verify that the program was written to the correct Chip (since the DK should keep blinking as usual).

    Best regards,
    Karl

Reply
  • Hello,

    nrf5xfanboy is correct about the CTS/RTS pins - they are most useful these days if you will be communicating at very high speeds with a system that is not always ready to receive the incoming data, for instance.

    I am not sure if I understood your 'recorder' question correctly but you can indeed use the development kit as a debugger for your other SoC through the SWD interface. I have attached an image that shows how this can be done:


    For convenience I would recommend that you program your DK with the regular 'blinky' example before you use it as the debugger for your other SoC, so that you can easily verify that the program was written to the correct Chip (since the DK should keep blinking as usual).

    Best regards,
    Karl

Children
No Data
Related