CN0338 + ADICUP360 + CCES 2.7 hangs up when trying to run.

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

Hi Andrew,

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.

Brandon

Brandon,

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.

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

Brandon,

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.

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

Hi Andrew,

Thanks for sending this along.  I think you may have two(2) different issues going on at the same time. 

• I can replicate the CN0338 hanging up on my Windows 7 machine, and that is one issue that we are debugging for a fix.  
• The issue with not being able to talk to the board half the time doesn't make any sense to me.  And I'm wondering if this might be a Window 10 issue with CrossCore.  I'm trying to find a local Windows 10 machine to try this on right now to validate my thinking.

Do you have any access to a Windows 7 machine that we can use to check on your side whether or not the intermittent programming issue gets solved?

Brandon

Hi Andrew

There is another possibility to get you moving with your design, while figuring out these issues. We have a legacy tool chain that we have which is also Eclipse based called the ADuCM360-IDE. It only works with the ADICUP360 platform and we have legacy source code that works with the CN0338 board. The ADuCM360-IDE was never tested on Windows 10 and there are no plans to ever do that, so you may find this doesn't work with Windows 10.  I rather not go down this path because we are deprecating support for this tool and the source code, but in a pinch this might help.

You would download and install the tool(Tool Chain for EVAL-ADICUP360 [Analog Devices Wiki] ), and import the legacy example source from Github (EVAL-ADICUP360/projects/ADuCM360_demo_cn0338 at release/aducm360-ide-1.0.1 · analogdevicesinc/EVAL-ADICUP360 · GitHub ) and use this for your development for the moment. Again we are deprecating support for this so just remember that this really is a potential temporary solution. The CN0338 source code is the same as the version in CrossCore 2.7, but the project is structured differently, doesn't have all the same includes, and doesn't make use packs or any ARM updates.

Brandon

Brandon,

I got my hands on a windows 7 computer so I will try that route first and report back to you.

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

Hi Andrew, 

When you move the USB cable to the user conector you are trying to use the board without the debugger, am i right ?

In this case you have to change the semihosting setting which enabled the board to run without debugger support. This is the link where the process is described CrossCore Embedded Studio Quickstart User Guide [Analog Devices Wiki] . 

For the cn0338 we looking for a fix, but the other projects should work. 

Regards,

Mircea

Mircea,

Thank you for the response.  I tried your suggestions and it still doesn't seem to work properly.  If I debug with "rdimon.specs", I can get the program to upload, however, nothing happens in there terminal program.  If I debug with "none", I can't get successful upload, I get a warning that an error occurred during upload.  And if I debug with "nosys.specs", sometimes I get successful upload but most of the times I don't and I get an error, cannot find CMSIS-Dap Device".

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