Our boards are no longer being initialized or able to communicate to them through the serial port of the EVAL-ADICUP3029.
We have tried programming the CN0429 with custom code and have made the modifications to the 3029 in order to program the CN0429.
It appears now that the boards are no longer being initialized or able to communicate with them through the serial port. We have tried reprogramming the hex file ADuCM3029_demo_cn0428_cn0429.hex into the 3029 but that doesn't help. The error that we see displayed is:
Please wait for sensor startup and initialization:...........Sensor in site 1: 0x4000008 initialization error. Address 0x0A!Sensor in site 2: 0x4000008 initialization error. Address 0x0B!Sensor in site 3: 0x4000008 initialization error. Address 0x0C!Sensor in site 4: 0x4000008 initialization error. Address 0x0D!No Sensor Board Found! Please check connections and reset ADICUP3029.
One thing of notice is that when the 10pin cable is connected to the ADuCM355 Arduino Interposer board, if the switch was set to a spot (1-4) with no CN0429 connected the D drive would appear as maintenance but if the switch was set to a spot with a CN0429 the D drive would appear as DAPLINK.
Nothing we have tried is able to get this working again. Do you have any advice?
Is this the same ADICUP3029 that you cut the traces on? Those traces correspond to the SWD lines, and if you are trying to reprogram the ADICUP3029, then you will need to use the ribbon cable between P12 and P14 in order to connect to the board via the IDE.
Yes we have moved the cable to P14 in order to program the 3029. Everything appeared to program correctly.
It doesn't matter where the cable is connected, P14 on the 3029 or P10 on the interposer board the CN0429 boards will no longer initialize.
If you did change the firmware on the CN0429, I would recommend downloading and re-flashing the CN0429 with the stock firmware and upload the ADICUP3029 with the stock firmware ADI provides to see if you can get the boards to respond properly.
Many times if you create custom code there was something there you may have removed that was important for the ADICUP3029 to read in order for things to initialize properly.
If this works then you know that it's your code that is causing the issues.