Simulating ADSP-21479

Hello,

Please note that the Command Line simulator(Chipfactory.exe) will support the below processors only.

Functional Simulator:
ADSP-BF70x
ADSP-BF716
ADSP-21573
ADSP-21584
ADSP-SC584
ADSP-SC589

Cycle-Accurate-Sim:
ADSP-2157x
ADSP-2158x
ADSP-SC57x
ADSP-SC58x

For more information please refer the below CCES help page about usage of command line simulator.
CrossCore® Embedded Studio 2.8.3 > Simulator User's Guide > Usage

Regards,
Santha kumari.K

Thank you very much, Santha,
That explains chipfactory.
I guess I need to use CCES_runner.exe ?
Do you know how I can avoid the error message I am seeing ? I couldn't find anything with a search here or using Google.

Thanks again,

John

Hello,

Please note that the commands '--target chipfactory simulator' and '--platform ADSP-21479 Functional-Sim' that you have used are not supported for ADSP-214xx processors. You have to use the command as below for 214xx processors.

CCES_runner.exe --target "ADSP-214xx Family Simulator" --platform "ADSP-214xx Simulator" --processor ADSP-21479   --core "0,test21479.dxe"

You can find the appropriate commands using --list switch in CCES_Runner help section.This will gives you all available combination of targets and platforms for the corresponding target.

For Eg: CCES_runner.exe --proc ADSP-21479 --list

Also we recommend you to refer the below linked FAQ for more information on using CCES runner utility.
ez.analog.com/.../faq-using-crosscore-embedded-studio-s-cces-runner-utility

Regards,
Santha kumari.K

Hi Santha,

Thank you, again, for your reply.

Unfortunately whenever I run :

CCES_runner.exe --target "ADSP-214xx Family Simulator" --platform "ADSP-214xx Simulator" --processor ADSP-21479 --core "0,app.dxe"
or
CCES_runner.exe --proc ADSP-21479 --list
then CCES_runner just returns to the command prompt without printing anything.
Note "CCES_runner" prints the help screen.
FYI, I am running Windows 10, with all the latest udates applied.

Best regards,
John

Hello John,

Could you please confirm is your example project contains any printf statement in it.If yes, the cces runner will exit with the print which you have provided in the example.

If you are still facing any issues, could you please share us your project along with brief description about it. This will help us to assist you better.

Regards,
Santha kumari.K

Thanks Santha

Here is a printf example that doesn't print

Commands to build and run :

cc21k hw.c -proc ADSP-21479
CCES_runner.exe --target "ADSP-214xx Family Simulator" --platform "ADSP-214xx Simulator" --processor ADSP-21479 --core "0,hw.dxe"

#include <stdio.h>

void main (void)
{
    printf ("hw!\n");
}

Best,

John

Hello John,

We are able to print using your code snippet and we used the command line as you provided.Please refer the attached screenshot of output and "dxe" file that we used.

Can you please let us know which version of CCES you are using?

Regards,
Santha kumari.K

CCES_Runner.zip

Thanks Santha

cces_runner version 1.1.0.12

Your binary doesn't work on my PC.

I wonder if the difference is that contents of the System folder.
Here are the files in mine :
ADSP-21479-compiler.xml
ADSP-21479-linker.xml
ADSP-21479-memory.xml
ADSP-21479-registers.xml
ADSP-214xx-core.xml

Please would you be able to zip yours and send it ?

Best regards,
John

Hello John

Could you please let us know which version of CCES IDE(eg. CCES 2.8.3) that you are using, so that we can assist further.

Regards,
Santha kumari.K

Hi Santha,

Yes, I am using CCES 2.8.3.

as per my earlier message, I can't see the output of your compiled example so I wonder if the difference with the contents of the System folder you are using ?

Best regards,

John

Hello,

As per your request, we have attached the 21479 system xml files. Can you try replace it in the below directory and see if the issue still occurs.Before replacing take a backup copy of the old files.
C:\Analog Devices\CrossCore Embedded Studio 2.8.3\System\ArchDef

If you are still facing the same issues, Can you please check if you have set the CCES_HOME environment variable and make sure that it's set to the right installation of CCES?  e.g., as you are running CCES 2.8.3, the CCES_HOME environment variable should be set to the CCES 2.7.0 install directory.Please refer attached screenshot for reference.

Can you please try uninstall and reinstall CCES 2.8.3 and let us know how you gets on.Also try running this example in any other PC and see if it works.

If this doesn't help, please share us the screenshot of the command prompt after running CCES runner commands. Also please let us know if you are using CCES in virtual machine or native OS.

Regards,
Santha kumari.K

System_Files.zip

Thanks Santha,

I did a full reinstall but there was no difference.

It is a fully native WIndows 10.

CCES_HOME="C:\Analog Devices\CrossCore Embedded Studio 2.8.3"

I had a thought and tried running from C:\Analog Devices\CrossCore Embedded Studio 2.8.3. It works perfectly but not from any other folder.

If we can't figure this out then no problem, I have a workaround now.

Best regards,

John

Thanks Santha,

I did a full reinstall but there was no difference.

It is a fully native WIndows 10.

CCES_HOME="C:\Analog Devices\CrossCore Embedded Studio 2.8.3"

I had a thought and tried running from C:\Analog Devices\CrossCore Embedded Studio 2.8.3. It works perfectly but not from any other folder.

If we can't figure this out then no problem, I have a workaround now.

Best regards,

John

Hi,

CCES Runner can be run from any directory, but if it is running outside from CCES home directory,

the command option --cceshome must be used to specify the location of CCES.

You can use the below command line.
CCES_runner.exe --cceshome "C:\Analog Devices\CrossCore Embedded Studio 2.8.3" --target "ADSP-214xx Family Simulator" --platform "ADSP-214xx Simulator" --processor ADSP-21479 --core "0,hw.dxe"

Regards,
Santha kumari.K

Unfortunately, that didn't work for me so I'll stick with my workaround.

Best,

John