KABD-4100 (AKA Wondom/Sure JAB5) Resetting to some default setting after power off
Thread Summary
The user encountered an issue with the ADAU1701 in a Dayton Audio KABD-4100 4ch amp where the program was lost after power cycling. The solution was to complete the process by writing the latest compilation to the E2PROM. However, other users reported similar issues even after writing to E2PROM, suggesting potential firmware or hardware problems with the ICP5 programmer.AI Generated Content
Hello all,
I'm using a Dayton Audio KABD-4100 (aka Wondom/Sure JAB5) 4ch amp. It has the ADAU1701 chipset. I'm using a Dayton Audio KPX In-Circuit Programmer USB to get my sigmastudio schematic loaded.
I built the speaker cabs as a mono 3-way and Have left the KPX attached, and mounted in the cabinet such that I can tune the speaker over time without having to open the cabinets.
I am able to edit the SCH and upload it to the adau1701 with no issues.
However, when I power the cabinet off, the ADAU1701 seems to loose the program. When I power it back on, it is working, but not as expected: I hear high frequency audio at low volumes for about 1 sec, then nothing, sometimes it cuts in and out depending on the input levels.
I am able to attach the USB cable and reload the program and then it works properly again until powered off.
Hope someone can shed some light on this.
Thanks!
3487.CD-3way-test1.dspproj
Edit Notes
Added product number
[edited by: emassa at 3:23 PM (GMT -5) on 21 Nov 2022]
Audio Signal Processors
SigmaDSP Audio Processors
adau1701
OK I found my issue. I wasn't completing the process by “Write Latest Compilation to E2PROM”
I'm glad that you have solved your issue. Thank you for notifying us.
Regards,
Harish
Im having the same issue, but its hapening even after writting the program to the eeprom.
It started ever since I updated the firmware on icp5 to work with the PCUI software, but seems it cant go back.. submited the issue to wondom but all i got so far was silence
Did you find a solution to this? Encountering the same issue.
I also have this exact same issue with a Wondom JAB4. I know this thread is an oldie but any solutions to this?
Im using a JAB4 and ICP5. It's like it defaults back to the demo program after a power-cycle regardless of what I program the EEPROM with. Wondom support just keep repeating the just press “Write Latest Compilation to E2PROM” as if I hadn't tried it. I have also tried programming the EEPROM .hex file which is generated when you 'export system files' from SS.
Like you, I can edit my sch in SS (attach the Pot's to filters etc), program it to the ADAU1701 and change parameters etc in real time and the changes are reflected on the HW (and from my speakers!). When I power cycle the board it then defaults to what I can only imagine is a demo/factory-test program which changes things completely.
I'm at the point where I have a ton of Wondom products and little confidence in them!
Hope you can help!
Hello steventyson,
I just spent a lot of time locating and downloading documentation for the JAB-4 and I am a bit frustrated at the difficulty of obtaining a schematic diagram of the board. I did find some info in the user guides that is pointing to the issues. However, I cannot point directly to exactly what it wrong.
To suvccessfully program the EEPROM you must do two things.
1) Take the DSP out of "Selfboot" mode by lowering the voltage on the Selfboot pin
2) Take the EEPROM out of "Write Protect" mode, "WP". I could not find any reference to both of these in the documentation. There should be jumpers or some way to do it.
If the EEPROM is in Write Protect mode then it will never be able to take in the new program because writing to the EEPROM is blocked.
The Selfboot issue is more for keeping the DSP from trying to boot up when SigmaStudio issues a Reset which can happen.
I have used some of these Wondom products and enjoyed them but it was the JAB-5.
Odd things I am noticing is that the pinout of the programming port is nothing like the pinout of the USBi.
Also, the WP seems to be brought out to the programmer. I do not know exactly how this connects to the USBi and I do not know their programmer.
This is how we expect the programmer to be connected. This is our 10-way pinout.
Pin 4 is a power pin which in this schematic illuminates an LED. It is not connected on many boards.
We do not connect to a WP pin. We expect that to be done on the target board with a switch or jumper or some other creative way.
I really hate to say this but the folks at Wondom need to show you how to defeat the Write Protect on their board!
Dave T
Hi Dave,
Many thanks for your detailed, thorough response to my question/comments both on this thread and the other one!
Your comments definitely pointed me in the right direction and, interestingly enough, Wondom also responded with a suggestion to pull the WP pin low as well. This may have been in response to me forwarding a link to this thread.
I tried doing this by just adding a toggle switch between WP and GND, and when WP and GND are connected together I can program the E2 just fine (as SS appeared to be able to do previously btw!) but this time the E2 is 'actually' being programmed and my SS code runs happily even after a power-cycle and no ICP5 connected.
This all sounds like a 'case-closed' situation although I have suggested that perhaps Wondom take a look at the ICP5 FW (which may be pulling the WP at the wrong time?) or the JAB4 HW to see whats up. I've only had a brief look at the ICP5 layout but can see that the WP pin connects to an analog switch which probably means that they are pulling it one way or the other via FW.
Anyhow, many many thanks for your help with this, Dave. Much appreciated and has saved me a lot of headaches!
S.
Actually, Dave, is there any issue with holding write protect low all the time?
Please log in to reply.