Attached is the sample code for Audio Talk through on EVAL-SC589-EZLITE for I2S mode of operation.
Attached is the sample code for Audio Talk through on EVAL-SC589-EZLITE for I2S mode of operation.
Hi Sachin,
Many thanks for providing the updated code, it is very helpful.
One issue I have found is the code does not seem to always load/run properly (or at all). About half the time I try to run, the code appears to fail and exits at __lib_prog_term.
I repeat the procedure a second time and it then runs fine. I’m not sure if it is something to do with the way I am using the de-bugger? The procedure I use is as follows:
1. Build code (target SC584)
2. Click on Debug (target EZKit)
3. The De-bugger loads all 3 cores (this takes over a minute to complete)
4. Click on Multicore Run: code runs till Core 0 halts.
5. Click on Core 1 in the Debug/Call trace window and then click on single core run (F5)
6. Usually this fails the first time and exits as mentioned. I then click on Terminate followed by Remove All Terminated.
7. Repeat the procedure starting from (2) above. Typically it runs the 2nd time.
This means every time I need to change the code or simply reset and restart it, it takes about 3 minutes. That becomes painful when trying to debug various things.
Is there a better sequence I could use to improve the success rate? Is there a simpler way to restart the code for example after hitting a break point (rather than having to go through the whole Terminate/Re-launch procedure?
If anyone else has any insights I’d be grateful to hear them
Reverb
Hi Sachin,
Many thanks for providing the updated code, it is very helpful.
One issue I have found is the code does not seem to always load/run properly (or at all). About half the time I try to run, the code appears to fail and exits at __lib_prog_term.
I repeat the procedure a second time and it then runs fine. I’m not sure if it is something to do with the way I am using the de-bugger? The procedure I use is as follows:
1. Build code (target SC584)
2. Click on Debug (target EZKit)
3. The De-bugger loads all 3 cores (this takes over a minute to complete)
4. Click on Multicore Run: code runs till Core 0 halts.
5. Click on Core 1 in the Debug/Call trace window and then click on single core run (F5)
6. Usually this fails the first time and exits as mentioned. I then click on Terminate followed by Remove All Terminated.
7. Repeat the procedure starting from (2) above. Typically it runs the 2nd time.
This means every time I need to change the code or simply reset and restart it, it takes about 3 minutes. That becomes painful when trying to debug various things.
Is there a better sequence I could use to improve the success rate? Is there a simpler way to restart the code for example after hitting a break point (rather than having to go through the whole Terminate/Re-launch procedure?
If anyone else has any insights I’d be grateful to hear them
Reverb