Required on every boot

Since I first used this tool, I’ve found that I need to set it up again (e.g. run dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/dacdsp-default.xml) on every reboot in order to get any audio output from my DAC+ DSP.

This isn’t too much of an inconvenience as I rarely reboot my Pi, but I’m just worried whether it’s symptomatic of a more serious problem.

Pi 4, Raspbian Buster, Linux 4.19.97-v7l+

[thomasschalch]

I’ve just received my first hifiberry DAC+ DSP board and I came across the same issue. So I’m not an expert at all, but maybe this helps you:

• The DAC+ DSP board seems to have a selfboot jumper located right behind the TOSLINK input. As far as I understand, if this selfboot jumper is set, the DSP program is loaded from the persistent storage (EEPROM) right after powering on. Setting this jumper solved the issue for me. (source: https://support.hifiberry.com/hc/en-us/search?utf8=✓&query=selfboot&commit=Search )
• The dsptoolkit command install-profle writes the DSP program to the EEPROM and loads it on the DSP. (source: https://github.com/hifiberry/hifiberry-dsp/blob/master/doc/dsptoolkit.md )

It would be great, if an expert ( @hifiberry ?) could confirm my statements. It would be very helpful, if this jumper would also be mentioned in the datasheet of the DAC+ DSP ( https://www.hifiberry.com/docs/data-sheets/datasheet-dac-dsp/ ). The jumper on my DAC+ DSP board was not set when buying it. Is this really the intended default setting?

[georgefst]

Anyway, this is solved (although I’d reiterate that the jumper should be mentioned in documentation somewhere).