Hi,
I would like to ask if there is a current provision for a module that does the following:
- while in AW designer, one can drop the module where user can type in text for documentation like design title, version, revision etc. and potentially save these (bytes) information within the flash memory. That burned info can be later gathered and used to display info outside of the AW environment (e.g. hardware displays).
If this not available, how can a module be made? When I review the module designer documentation, there is no mention of string as a data type.
- This is different from the annotation text that is currently available within AWE 8.
- During the flash step where the AWB is burned into the flash, the user can place a name to the file. This is usually within a limited amount of bytes. It is possible to maybe
address this within the flash manager step where the documentation bytes/strings can be done here and potentially saved in a predictable spot in flash. And then later on the firmware during initialization can just pickup these info bytes and use it for its purposes.
In a way if a target is burned already, the user cannot know what is burned within the hardware without connecting to the full AW Server/designer. In addition, if there are 2 copies of the same hardware and one has design A and the other one design B burned in, and the hardware can either display something, a module described above would help to identify which is which.
Thanks,
EEnrique
11:27am
Hello EEnrique,
There is currently no provision in the road map for the functionality you describe, however you could write text files to flash on your own to do what you're describing. You cannot however, control the address at which anything is written. Allocation of FLASH storage is always at the next free address following whatever was previously allocated.
To identify which design is on specific hardware, you could use the AWE API to read named files from code in the BSP, but unfortunately, you cannot write an Audio Weaver module to do writing to or reading from flash
With that being said, I can see the reason behind your inquiry and I will push the discussion to our software development team.
Thanks,
Kevin
1:08pm
Hi Kevin,
Thank you for your response. I see what you meant about burning a text file via the flash manager but where it lands within the flash memory can be very dependent on how big the executable (awb) will land.
Please do discuss the possibility of maybe expanding the flash manager dialog. I can imagine maybe the user just enter the info and just flash address offset.
Thanks again.
EEnrique