I am having a very similar issue. Initially I could not get the ADICUP360 with the EVAL-CN0338 board to communicate with CCES. I was eventually able to upload a program, however, this process is inconsistent. Sometime it works and other times it does not. I do not have this issue with any other of the demo sketches, just the CN0338 one. I have also tried all of the recommendations listed above and can't get anything to work. When I was able to successfully load a program onto the board, I wasn't able to get good communication in the terminal software (putty). It will initiate as it should but when I type "run", or any other command for that matter, it times out. It give me half of a response and then freezes up. Any suggestions?
Hi Andrew,
Sorry for not seeing your question earlier. I have moved it out from under the previous reply and added it as a separate question.
I have been able to replicate your issue on my side and we are currently trying to debug the software to find out where the issue is. Early indications point to a potential UART buffer size issue or memory issue that we are looking into at the moment. We will get back to you as soon as we can with more details.
Brandon
Brandon,
Thank you for the quick feedback. I am actually having all kinds of problems with the ADICUP360 board. Sometimes I can upload some of the example programs and get them working fine and other times it just doesn't work. I am starting to find that if I make any changes to the example code, it won't work when I upload them, but if I first upload a different example code, and then upload the example code that I modified, it will work. Its sort of hit or miss right now and I can't quite figure out why.
Thanks,
Andrew Mertz
Senior Project Engineer
Ohio Lumex Co., Inc.
Email: andrew.mertz@ohiolumex.com
Office: (440)-264-2500 Ext. 310
Fax: (440)-264-2501
Cell: (330)-888-2906
www.ohiolumex.com
This certainly sounds bizarre. Would you have a list of steps that you went through that you could share with me? Also, would you be able to send your modified code so that we could test on our end to see if we could replicate it?
Just in general a user must download/flash the board using the DEBUG USB port (P14) with jumpers(J3 and J4) populated. In many instances in order to see the code output on the serial terminal, we ask the user to set the jumpers and switches and move the USB cable over to the USER USB.
When you say it doesn't download/flash what do you see in the console window of CCES? Do you have a picture of the board and the settings you are using? Which of the other projects have you tried to load where things seem to work fine?
Sorry for the issues, there was a recent ARM CMSIS pack update and I wonder if it has anything to do with that? Any information you could share would be helpful.
I just tried downgrading the ARM CMSIS Pack to the previous version and it seems more stable at first glance. I will continue to work on this and provide you with feedback. If I see the same issues arise I will upgrade to the most recent version again and grab some screenshots to send your way.
Nevermind, same issues. Basically, I am using 3 demo sketches right now. These demo sketches are the ADC demo which is in the examples library of the ADICUP360, the ADUCM360_demo_cli, and the ADUCM360_demo_cn0338. When I make modifications to the code I just make simple math modifications or modifications to what is printed, for example in the ADC demo it prints the "voltage: ", and I may just change it to say "voltage 123: " Something simple for me to check and verify if my code was actually uploaded properly. I have verified the jumpers are in the proper location and I have also tried many different combinations to see if that helped and have not had success there.
With all of these examples, I am seeing a few things and I have listed them below. Just a note, this is running on a 64 bit version of Windows 10 Home.
1. Basically my process will be as follows (This is an example of something I see often). I first import the ADC example, then I build it and get no errors. I then create a debug configuration where I put in my target processor (ADUCM360) and I choose the "ARM CMSIS-DAP compliant adapter" as the interface. I check "run" and "debug" in the common tab and then I press debug. Sometimes I will get an error "unable to find CMSIS-DAP device". Normally I will press debug again and again and eventually it will find it. Other times I will get the attached screenshot (file[1]). If I then move my usb to the "user" port and then try to run this in putty, nothing works, nothing happens. I then go back to CCES and try to debug again and again and eventually get (file[2]). If I can get to this point, I can get both demos to operate fine in putty, however, the CN_0338 demo freezes up as you are aware. If I come back to CCES and try to make a slight modification, I generally go through this whole process again and eventually, sometimes, I can get it to work. I hope some of this is helpful information.
2.