ADAU1797 Compiling issues
Hello,
I have recently received the ADAU1797Z evaluation board, as well as the instructions on how to run projects and the SDK. After configuring SigmaStudio+ and XTensa to run together, and loading the Simple Audio Flow example project (located in C:\Analog Devices, I used the "Link Compile" option but got an error message without any details : XTensa Compiler - Failed to compile project. When using the "Link Compile Download" instead, although I don't know if the compiling error originates from the same issue as before, the compilation fails again, but this time, an error log is generated giving the following information :
Thus, I followed the instructions in the guide provided by the Analog team to generate the self_boot.hex file. However, upon generation in the console, the following exception is raised :
I had previously enabled the generation of the hex file. However, the name of the project's directory contained spaces and I had to setup the entire project again. After that, the self_boot.hex file simply wouldn't generate automatically anymore. I have double checked the configuration guide to make sure I didn't miss anything and reinstalled XPlorer once.
I have also noticed that commenting this line in the compile.tmpl allows the project to compile with "Link Compile", but the issue with "Link Compile Download" remains.
In order not to mess up the whole configuration, I reset every compilation file I modified to its original state.
If anyone could enlighten me on the situation I would be thankful.
Thibault
SigmaStudio+ 2.0.6
ADAU1797
software
0
Hello Mr. Thibault,
I will chime in here with some quick observations. I do not work with this part and with these programming environments so Patrick or Toshita will most likely respond with better information and teach me a few things as well. However, with the idea of trying to help you faster I will fall back on my experience with writing programs on many different older languages but many troubleshooting techniques remain the same.
Your first screenshot.
For error messages I always look at the first thing mentioned. That is usually where the problem lies and the rest of the error message is usually about things that are dependent on the first item so it is just noise to ignore. With that in mind, here is the first line:
Sorry it is so small. It says that a file was not found and that file is the Self_Boot.hex file. You have it in an examples folder and it does have a very long folder structure making for a long file name. I have had issues with a PIC C compiler years ago where there was a limitation on the length of the file names so I had to move the project to a folder closer to the root folder of the drive. I do not suspect this is the problem but it is something I noticed.
Then I would check to see if the file is there? Is it under a different name?
If the file is indeed not there then why?
So let's move on...
The next error message is related, it is about a failure to create the hex file.
The error message there is about an "NVM Overlap Detected". In case you do not know this, NVM stand for Non-Volatile Memory. This would be flash or EEPROM. An overlap would mean that pointers or addresses are not correct. Perhaps the size is wrong? Often if the address size is wrong the memory will wrap around back to the start and overwrite the beginning of the memory so this may be what it is warning about. Therefore check your defiles for things like EEPROM or Flash size, page size, or number of bytes in the address? Something like that.
The last one you listed is back to something similar to the first. I am wondering if it is a long path issue or just missing?
Check your configurations. Chances are the files you received from us had paths that made sense on our machines but not yours. You may need to make some changes to the default paths where it will look for the files.
Hope this helps. Patrick and Toshita are usually very busy so I am not sure when they will be able to respond. This is why we do not support this part to all customers because we do not have the resources to support it.
This should be something simple... finding it is the challenge.
By the way, we are probably very distantly related....
Dave T
Hello Dave, thank you for your reply. I will have a look at every advice that you gave.
One of my colleagues will be back from holiday next week. Perhaps setting up SigmaStudio+ and XTensa on a new computer will fix a few issues.
Also, Thibault happens to be my first name, unfortunately, so I unfortunately don't think we are distantly related .
Thank you.
Thibault
Hello Thibault,
That is very much a first for me! Thibault is a somewhat common last name here in the USA/Canada. It is one of the names derived from a similar name as my last name Thibodeau. I have never seen it as a first name. That is interesting. I still say we are probably distantly related. I guess you can say all of us on this planet are distantly related! Too bad more people do not realize that so we could all get along a little better!
But we have to end this conversation thread with that. This is a technical forum! but, I do like to humanize the conversations. At this point this forum does not use any AI.
Dave T
Please log in to reply.