CN0565+ADICUP3029，Serial Connection Error! No device found

Hi dachiyijing ,

I’ve noticed that the error you're encountering, "No device found," typically occurs when the COM port in the code is incorrect or when the hex file hasn't been properly loaded. To check if the hex file has been successfully uploaded to the DAPLINK drive, make sure there is no FAIL.txt file present. You should also verify that you’re connected to the correct COM port. If necessary, try re-uploading the hex file. An updated zip file containing the cn0565.hex file is available on the Wiki page. Once the firmware is successfully uploaded, you can reset the ADICUP3029 either by pressing the reset button or by unplugging and re-plugging the device.

Have you also tried running some example scripts? Are you encountering the same error with them?

Alternative Fix:

- Try replacing the data cable you're using to connect the ADICUP3029 to your machine.

- Pressing the reset button "S1" on ADICUP3029 before and after uploading the .hex file.

- Check if your machine recognizes the ADICUP3029 as "mbed Serial Port". If not, install the mbed serial port driver using this link https://os.mbed.com/handbook/Windows-serial-configuration

- You may also try this fix that is helpful for some customers.
If you go into "Computer Management->Services" and stop the "Storage Service" and "Windows Search" (also need to disable so that it won't restart later) then the MBED device starts behaving correctly and I was able to flash to it without any trouble.

Regards,
Michelle

If you have a configured requirements.txt, requirements_dev.txt, requirements_doc.txt, and requirements_prod_test.txt files, can you send me a copy？ my python environment always has problems

You may skip the installation of the requirements_dev.txt, requirements_doc.txt, and requirements_prod_test.txt files since these files were used mainly if you're going to develop a specific use case. Instead, you can install the requirements.txt file that can be found in pyadiio/examples/cn0565.


Regards,
Michelle

I reconfigured the file in the python virtual environment, but it still shows No device found. I would like to ask what port values need to be changed in the pyadiio/examples/cn0565 file?

In every example script in the pyadi-iio/examples/cn0565 folder, only the serial port value needs to be modified.

Thanks for the reply, but the problem persists. I changed the baud rate value in the code 230400 to 9600, and the port baud rate is displayed as 9600 in my computer, does the device support it? Do I need to change to a different baud rate?

Hi dachiyijing ,

May I see your hardware setup? Both the ADICUP3029 and CN0565 boards, I would just like to check if the jumpers are on its correct position.

Regards,
Michelle

Regards，

dachiyijing

Hi dachiyijing , mso , looking at the above, a good reality check is to connect to the board from a generic terminal, like HyperTerm. I had a CN0565 sitting around so I uploaded the hex file from the wiki page, and here's the message on resetting the board:

However - the baud rate indicated is wrong, TeraTerm is set to 115200, so this is probably just an error in the string in the source. Next, I tried connecting via IIO Oscilloscope, which should be able to connect to any valid IIO context, but get an error:

BUT - if I load up cn0565_aducm3029_fw_eit_ad5940_iio.hex from the cn0565.zip file from https://github.com/analogdevicesinc/no-OS/releases/tag/last_commit, Success! Note the baud rate is 230400:

And for the sake of completeness, Scopy2 is able to connect:

You will still want to use the CN0565-specific Python scripts, but this should be enough to debug the connection.

Oh, one last thing, I THINK that maybe the status message is printed out at 115200 baud, but the IIO communications itself is at 230400 - mso take a peek into the code and see if you can make sense of this...

-Mark

Thank you for your reply! I found that simply changing the baud rate to 115200 can connect, and the problem has been resolved. Thank you!

Thank you for your reply! I found that simply changing the baud rate to 115200 can connect, and the problem has been resolved. Thank you!

Great! Glad you're up and running.

-Mark