This is an old revision of the document!
Some of the example setup images are of EVAL-CN0428-EBZ, but still apply to both projects.
Although the Sensor Board ships programmed with tested firmware out of the box, it is often important to be able to modify the firmware and reprogram the board with new functionality. The following procedure gives some options for how to do this.
This guide focuses on programming and debugging the Sensor Board. General information about the Sensor Board can be found at EVAL-CN0428-EBZ and EVAL-CN0429-EBZ, depending on which Sensor Board is used.
If a stand-alone debugger is available, it can be plugged into P10 of the EVAL-M355-ARDZ-INT directly and none of the below rework is required. This is a good option for both programming and debugging if there is a stand-alone debugger available. The IAR project for the Sensor Board is set up by default for a J-Link/J-Trace debugger. An adapter cable such as the following is typically required to convert the 20-pin connector at the output of the debugger to the 10-pin connector on the EVAL-M355-ARDZ-INT. This cable is not included and can be found from distributors.
If using this option, most of the remainder of this page is not needed. When plugging in the debugger to the EVAL-M355-ARDZ-INT, make sure the pins of the cable and the on-board connector are correctly aligned and that pin 1 of the cable matches pin 1 on the EVAL-M355-ARDZ-INT board. Some more info is available on the EVAL-M355-ARDZ-INT wiki page. The items in the Software section still apply, including installing IAR and running the ADuCM355 Installer. After that, the project can be opened from the .eww workspace file in the source code and the project can be edited and the boards can be programmed and debugged from within IAR.
Alternately, if a stand-alone debugger is not available, the on-board debugger on the EVAL-ADICUP3029 can be used to program both the EVAL-ADICUP3029 AND the Sensor Board separately. This does not require any extra equipment beyond what is included with the boards in the CN0428/CN0429 package, but it requires 3 traces to be cut on the EVAL-ADICUP3029. Once this is done, the SWD connections from the output of the debugger are disconnected from the ADuCM3029, but these SWD connections are available at connector P12.
After this rework is done, it is simple to program or debug ADuCM3029 by connecting P12 to P14, or to program or debug the ADuCM355 on a Sensor Board by connecting P12 on the EVAL-ADICUP3029 to the P10 on the EVAL-M355-ARDZ-INT.
USB power and communications are not affected by these reworks, only the SWD signals are affected.
In order to make the debugger available to either the ADuCM3029 or the ADuCM355, the SWD signals must be cut so they are not connected directly to the ADuCM3029 SWD pins. This requires 3 traces to be cut with an X-Acto or similar hobby knife or utility knife. 2 of the SWD traces to be cut are on the primary side and 1 trace is on the secondary side.
The traces are cut after the P12 connector on the debugger side of the EVAL-ADICUP3029 so that the SWD signals are available at P12 and the ribbon cable that is included with EVAL-M355-ARDZ-INT can be used to connect those signals to the device to be programmed or debugged.
As shown in this magnification, the upper trace is SWD_CLK_3029 and the lower trace is 3029_RESET. These traces should both be cut completely. Both signals still go to P12, this just removes them from P14.
The trace that needs to be cut on the secondary side of the board is SWD_DIO_3029. This is the outside trace of the 3 that cross the island from the debugger board to the main EVAL-ADICUP3029 board on the secondary side, but it is simpler to cut the trace in the location indicated to avoid accidentally cutting one of the other traces.
This magnified version of the 3 traces that cross the island shows that the other two traces that cross the island are MBED_TX (shown bottom in picture) and MBED_RX (shown middle in picture). These two lower traces must not be cut or USB communication to the board would no longer work.
Image showing ribbon cable connection and installed EVAL-CN0428-EBZ, ready for programming. The other side of the ribbon cable is still connected to P12 on the EVAL-ADICUP3029 as was shown above.
Once the modifications are in place and the cable is connected between P12 on the EVAL-ADICUP3029 and P10 on EVAL-M355-ARDZ-INT, there are two main options how to program the ADuCM355 on the Sensor Board.
Both programming options require the following conditions to be met:
If either of the above conditions are not met, go to the Software section to set up the software first.