I have been working with the ADICUP360. Awesome tool! I have progressed to where I need to connect the board to my J-LINK probe and am having trouble. I see from the schematics that the 10-pin Cortex debug connector P16 connects to the M360 SWD pins, but also to the on-board SDA interface. How han I force the SDA interface to relinquish contol and allow the J-LINK to control the SWD pins?
Thanks in advance!
Glad to hear you like the ADICUP360 board
So I'm a bit curious as to why you are using a J-Link to attach to the ADICUP360. There is an on board debugger/programmer for you to use, which connects directly to the USB port of your PC.
There is also a way to directly load the on board programmer with a binary or hex file, and you can simply drag and drop the file you wish to load via the "MBED" drive that shows up as a removable drive.
Which tool chain are you using? We provide a set of tools with instructions which can be used with the ADICUP360. You can find all those details and many more up here on our user guide.
I am trying to move up to the Keil MDK tools and the J-Link probe, which I already own. If I can get the J-Link running, I can use the J-Scope utility which lets me graph the ADC results in real time, without needing to connect some type of user interface to the ADICUP360. SEGGER - The Embedded Experts - J-Scope . And a step towards moving to the tools I will need to use when I incorporate the M360 onto my own PCB.
If you would like to bypass the on board debugger, than you are welcome to do that. Make sure you have the schematic handy, https://wiki.analog.com/_media/resources/eval/user-guides/eval-adicup360/hardware/eval-adicup360_1_.pdf
There is a 10-pin ARM cortex connector on the ADICUP360 located at reference designator (P16) as you have already stated. That is the connector where you want to hook up the J-Link device.
I don't think you will need to worry about the SDA lines going to the MK20DX128 device, because there is a buffer/tristate device that is in between the MK20DX128 and the ADuCM360. So if you are not using the MK20DX128 as the programmer/debugger, those buffer enable pins (1,4,10) should stay high, allowing no communication to happen.
It is important that the jumpers on J3, J4, and J5 are populated when trying to use the J-Link to program from P16. And also make sure that the ribbon cable from the J-Link to the connector is facing the correct way. There are no "keyed" sides of the P16 connector. Here is a drawing I found on the internet showing the connections to the 10-pin connectore, so just make sure you match pin 1 from the ribbon cable of your J-Link with pin 1 of P16.
Up and running! Thanks for the help.
You are correct, the on-board SDA interface relinquishes control of the SWD pins when the Debug USB port is disconnected. When I power the board through the User USB port, the J-Link attached to P16 takes control of the M360 without conflict.
Thanks for closing the loop Steven, good luck on the rest of your project.