Power On/ Off Delay to avoid clicks and pops
Hello Brett,
The library block MUTE is meant to do just this. However it needs a WRITE from an external micro-controller.
It is possible to tweak this block to operate without an external WRITE?
Kindly also look into my unanswered queries posted earlier.
Thanks in advance.
KKSL
Hi KKSL,
Sorry that I have not been able to address your other questions yet. Over the last 3 weeks, I have been out of the office for about 2 weeks, so unfortunately I have not been able to respond promptly to everyone's questions on the forum. I will do my best to catch up and get answers out to everybody's questions.
I want to confirm that I understand your question correctly. Do you want to use a mute cell on self-boot? For example, I am picturing a scenario where you first do a standard self-boot operation with the mute cell enabled, and then you un-mute after the core has started. If that's the case, then I have a solution that might work.
If you follow method 2 on this post about self-boot eeprom generation, you can manually create a download sequence to get the system up and running: https://ez.analog.com/message/5759#5759
My idea is to add a few additional parameter RAM writes at the very end of the sequence that would un-mute the mute cell. This would basically self-boot the chip, get the core up and running with the outputs muted, and then finally un-mute them so they can slew up at startup. Does that make sense?
Thank you for your early reply and for the solution!
Yes, you have pictured my query correctly.
I am going to implement the suggested solution and let you know how it works.
It is exciting to know how much you can get done without using a micro-controller and I am going to do just that.
Let's see....
Kindly also check your PM.
Thanks again,
KKSL
Great! Keep me posted of your progress.
Done!!
After Link-Compile-Download, I un-muted the mute cell. That added the extra code. Then I dragged it all to the sequencer window and followed the outlined steps there after.
Export sequence data actually generated two files: *IC_1.hex and *IC_2.hex. I used the first file.
Just out of curiosity, what is the 2nd file? It only has 8 bytes.
Thanks a lot again.
KKSL
Hi KKSL,
The second file actually contains a "footer" for the EEPROM image. This file should be generated, so this is just a bug. Please ignore the second file. I will try to make sure that it is not generated on subsequent SigmaStudio builds.
Please log in to reply.