Project is crashing when 3072/2 instruction cycles (half) reached. How to use all 3072 instruction cycles on 96 kHz
I am running a 96 kHz project on ADAU1452. Everything is ok till 1536 cycles are reached. Sometimes it is still running but showing "error in PM1".
Sometimes it crashes with all PLL settings set to highly incorrect values. Everything must be restarted to get out of that.
Audio Signal Processors
adau1452
hardware
SigmaDSP Audio Processors
4.6
error in PM1
Show More
Hello Raimonds,
Could you please attach your sigma studio project?
And is there any particular reason that you are still using SS4.6?
We would recommend you use the latest version SS4.7.
Regards,
Harish
Thanks for the question! I saw bugs in 4.7. At least, the "Export system files" was not working for a strange reason.
I guess I should use an even older version because the project was started in 2017.
I started the new topic about that. Please participate!
Hello Raimonds,
I responded to your other post but I also want the answer here in case someone reads this one.
We have an instruction monitor utility.
This monitor actually gives you the exact instructions used and you can see over time if it did overrun. This post explains how to use the overrun monitor that gives you some information.
The "Error in PM1" is an entirely different issue. Are you using the Panic Flag and Panic Error trapping functionality of the core? There is a certain way to use it and you have to clear the errors before it is used. This error you are seeing in PM1 is most likely not any real problem.
If you need to use the panic manager function of the core then I would need to explain more about it. I looked for an older post but did not find a good one. I found this one that I explained a little about it but not how to use it. I think I have it as a document on my computer. Let me know if you need to use this. I do not expect you do.
(+) ADAU1452 intermittently reporting strange panic codes - Q&A - SigmaDSP Processors & SigmaStudio Dev. Tool - EngineerZone
Dave T
Thanks Dave!
Just to say it is solved!
It was because of the use of the "150" version of ADAU1452 with an internal clock of 147 MHz
Raimonds
Please log in to reply.