Latest images
Sometimes I generate tables in SRAM.
For example, in the case of ‘EarTest_08T9_hiLo.asm’ which was attached in "AVRasm2 Debugging - AddEvent Repeated Event", sine and cosine tables are generated in the SRAM space for every given frequency (actually, the N bits of one cycle). Also, the result/table of the delta bit stream (to output a sinewave) is also saved in SRAM.
Saving the SRAM data is not implemented. So, as a workaround, I add a temporary routine in the code to copy the table in SRAM, that needs to be verified, into the MCU internal EEPROM (so that I can save it for study).
I hope it is not difficult to also allow the saving of SRAM data. But I guess we all agree that there is no need to load data into SRAM, for the time being in the least, as it is the case for EEPROM.
Thank you.
For example, in the case of ‘EarTest_08T9_hiLo.asm’ which was attached in "AVRasm2 Debugging - AddEvent Repeated Event", sine and cosine tables are generated in the SRAM space for every given frequency (actually, the N bits of one cycle). Also, the result/table of the delta bit stream (to output a sinewave) is also saved in SRAM.
Saving the SRAM data is not implemented. So, as a workaround, I add a temporary routine in the code to copy the table in SRAM, that needs to be verified, into the MCU internal EEPROM (so that I can save it for study).
I hope it is not difficult to also allow the saving of SRAM data. But I guess we all agree that there is no need to load data into SRAM, for the time being in the least, as it is the case for EEPROM.
Thank you.
