ADAU1772 IC 2-WinE2PromLoader Creates 16KB File
Thread Summary
The user encountered issues with the WinE2PromLoader tool creating a 16KB file instead of the expected 4KB when uploading to EEPROM. The support engineer confirmed that SigmaStudio pads the exported file with zeros and suggested truncating the .hex file manually to 6KB, ensuring data integrity around the 580-5A0 offset range. The user also asked about increasing the complexity of their SigmaStudio routing, specifically how to configure paths for FPGA source and ADC inputs, and whether the DSP core should be enabled for certain settings like PGA boost or volume sliders.AI Generated Content
The WinE2PromLoader tool does not auto-configure itself to the EEPROM you are using or the necessary minimum file size.
The appropriate filesize is 4KB. I can go into the register control section, configure settings, Link/Compile/Connect, and then back out to the PromLoader and set Mem Size to 4KB and clear eeprom, verify cleared by "read E2Prom to Display", which creates a 4KB file. I then go to the Config tab, ADAU1772, write latest compilation to E2PROM. I can then read E2PROM and verify it is programmed and see that the filesize remains 4KB. Now I want to save this 4KB to a file by UpLoad E2PROM to File. "Mem size" setting remains 4 KB but it is writing a 16KB file. I need a 4KB file and want to later clear the E2PROM and DownLoad File to E2prom. I am using HxD as a bin/hex editor and it goes whacky with the 16KB file. Is there a way to force the created filesize to 4KB? I think it worked once but I don't know what the magic sequency was to do it. The ultimate goal is to get this file and have the project fpga program it to the project E2PROMs. If I create a new project from this one it will create a 4KB E2PROM file in the IC2 folder, but I shouldn't have to do that.
sigma studio
software
4.7
e2prom
adau1772
processors and dsp
Integrated/Special Purpose A/D Converters
Processors and Microcontrollers
Audio CODECs
Show More
Let me retry explaining this (it gets confusing...)
If I use SigmaStudio 4.7 to edit settings of our pre-existing project and then save the project as a new project title, it will create a 2KB BIN file and a 11KB HEX E2PROM file. However the WinE2PromLoader utility will not successfully use this 2KB BIN file. If you click on "Browse for File" at the top and highlight that file and then Display File the Values contents will show all zeroes and not the file data. If you use HxD to view the BIN file contents they are there and correct.
The E2prom section shows page size 32Bytes and 32KBytes as defaults. If you have a project loaded you can drop the Mem Size down to 4KB for 100% Mem Usage. My expectation is to be able to create a 2KB BIN file with the Upload to File that would be compatible with the Download File to Eprom as well. This is because we need to be able to write the E2PROM with out FPGA. Different file size different checksum and our failure symptoms look like it could be due to a CS mismatch. It is not creating the small filesize we expect - it creates a larger one that HxD goes into a mode converting the BIN to ASCII codes or something... :-(
Hello bklein,
We really will need your files to verify all of this.
Is it possible to obtain your files?
Dave T
Just sent to your personal email.
Hi bklein ,
I'll be taking over this issue from Dave, and he forwarded me your files. I'll be looking into this tomorrow, and will provide an update shortly after. Thanks!
TBM
Ok. I just discovered that a hex file works for the DownLoad File to E2Prom option. I remain confused about the E2Prom Mem Size and Mem Usage data windows.
Can we have a Teams meeting to discuss our issues?
Hi bklein ,
So, to clear up some confusion, the E2Prom Loader in SigmaStudio can only accept a .hex file to download into the E2Prom. The loader cannot accept a .bin file format for loading the E2Prom. Though it can generate a .bin, this file would be used for programming an additional external flash or custom code into a system controller.
In terms of the exported file size, I believe SigmaStudio is defaulted to pad the exported file with zeros. I do not believe there is a way to change this. However, I was able to open the exported file in Notepad++ and delete a large amount of the padded zeros from the original 16KB file, and got it down to about 6KB. There are some bytes of data around the offset range of 580 to 5A0 that must be included for the ADAU1772 to SELFBOOT your project correctly. This seems like SigmaStudio generates your exported .hex file based on how the onboard EEPROM needs its data partitioned. Deleting the padded zeros after the 5A0 offset range appears to be the smallest you can truncate your .hex file. (16KB down to 6KB).
And to explain the Mem Size and Usage % question, if for instance you format your EEPROM to be 4KB, and we load in your E2PROM.Hex file, I can see in Notepad++ there's 180 lines of 8bytes = 1440 bytes in your file. When downloading this file into the EEPROM you will observe a Mem Usage % of (1440 / 4096) = ~35%.
I'll attach a .zipped folder that contains the truncated 6KB file for you to test on your setup.
Truncated File.rar
And apologies, but our team is very busy with other work at this time, and will not be available to arrange a TEAMS meeting. I will do my best to interact with your findings on this post, and hopefully work towards a solution to your questions. Thanks!
Best,
TBM
Bottom line is that whatever the file size becomes by using WinE2PromLoader, the hex file should work to program the E2prom - so I won't worry about it.
I need now to increase the complexity of my SigmaStudio Routing. Paths are:
1. Source by FPGA, DAC_SDATA to Serial In 0/1 Input ASRC, ASRC enabled, route to Output Select Inputs ASRC 0/1, which then output audio to DAC's 0/1.
2. AIN's0-3 selected as Core Input Selections AIN0-3. Nomenclature changes to ADC 0-3 which should be the digital conversion data, selected by Output ASRC Source Select. Output ASRC enabled. SOUT Source Outputs ASRC 0-3. This then should combine them for output ADC_SDATA0 via Channel 0.
I don't get how the SigmaStudio schematic should look like for the above though. Are digital input/outputs different icons than audio ones?
I also don't understand if the DSP core should be enabled or not. What determines this? If for example I set PGA boost, or PGA/ADC Volumes sliders, does that create coefficients that must be programmed (and DSP core enabled). Are these Program data or coefficient data?
Why does the READ/WRITE utility provide write coefficient data but not read?
How do I send you my files, I don't see the option.
Thanks!
Please log in to reply.