How to erase/write spcific NVM(MCU flash) part with Stellalink+AutoDevKit Studio on AVAS EVK?

[decemberdream]

Hello,

As far as I known, ST released two kinds of AVAS EVK which one is based on AEK-MCU-C1MLIT1(https://www.st.com/en/solutions-reference-designs/sl-ssasf011101v1.html ) and another is based on AEK-AUD-C1D9031(https://www.st.com/en/evaluation-tools/aekd-stereoavas.html#overview ).

I have both EVKs now but I have a issue on #2 case below.

1. AEK-MCU-C1MLIT1 with PLS Programmer/debugger tool + UDE StarterKit SW
   • As you know well, AEK-MCU-C1MLIT1 board includes PLS Programmer/debugger tool inside itself. So, Under this environment(PLS Programmer/debugger tool + UDE StarterKit SW), I can write/erase specific NVM part to change WAV file(.hex format) and the way is explained very well on UM2719 like below.
2. AEK-AUD-C1D9031 with StellaLink Programming/Debugging tool + autodevkitspc5studio
   • SWAEK-AUD-C1D9031 board doesn't include PLS Programmer/debugger tool inside itself. So, I bought a stellalink(AEK-AUD-D1D9031 can support this). But Under this environment(StellaLink Programmer/debugger tool + autodevkitspc5studio SW), I don't know how to write/erase specific NVM part to change WAV file(.hex format). I made the environment which can debug with OpenOCD but I can't find any document for NVM erasing/writing...

Could you help me from this trouble?

Thanks,

[ATROI · Accepted solution]

Hi Decemberman,

There isn't a script to erase a specific block memory yet, but you could use this one as an example:

spc582b_dis_FLASH_ERASE_ALL.cfg.

you can find this file under C:\AutoDevKitStudio-2.4.0\openocd\scripts\utility.

Read the readme.txt file first. 

Replace the command path from: 

C:\StellarLINK\openocd\bin\openocd.exe -d0 -s C:\StellarLINK\openocd\scripts -f utility\spc582b_dis_FLASH_ERASE_ALL.cfg

to:

C:\AutoDevKitStudio-2.4.0\openocd\bin\openocd.exe -d0 -s C:\AutoDevKitStudio-2.4.0\openocd\openocd\scripts -f utility\spc582b_dis_FLASH_ERASE_ALL.cfg.

For more info, see the UM of OpenOCD online.

Thanks,

AutoDevKit Team