my USBi "locks" during "Link Compile Download"
Hi everybody,
I have a problem with a new simple board with an ADAU1701. I'm trying to control it with an USBi (I have both version 1.2 and 1.3).
When I perform a "link compile download" it looks like the USB get frozen .... the SCL line remains low, the yellow led on the USBi
keeps blinking .... in this state the USBi is "locked", that is the only way to come out of this situation is to disconnect the USB cable.
It's the same with version 1.2 and 1.3.
Now I checked everything on the board and connection and it's OK. This is confirmed by the fact that more simple actions, like
trying to use the "register control" window of the 1701 work OK, I can read and write with no problems if I do this as first action instead of downloading a program. Even reading all the registers is possible and OK.
It looks like downloading a firmware actually brings the USBi into a strange state where it keeps the SCL low.
I performed several checks and I can confirm that it's the USBi that actually pulls the SCL low.
I even tried to change the I2C pullups ... from 10k to 2K almost nothing changes ... sometimes I can download the firmware for one or two attempts, then everything locks .....
Is there any "firmware" or driver upgrade for the USBi? I'm actually using the latest beta Sigmastudio 3.11 Build 1 .
Isn't it a bug that actually it can LOCK the SCL down without ever recovering?
Moreover, is the 1701 too sensible to I2C pull-up value? What is a safe value to use ?
In a different situation I once run into problems when I discovered that everything was working with an USBi attached (the firmware was loaded by a microcontroller, the USBi was used to monitor the situation) while disconnecting the USBi caused everything to stop ... I changed by trial and error the pullups and ended up using 10k.
Audio Signal Processors
SigmaDSP Audio Processors
adau1701
Hello Daniele,
Sorry for the long delay in responding. We did find that there is a software issue where the USBi can lock up when transferring large blocks of data like when you program a part. There is an interrupt that is missed and results in the USBi holding the SCL low and is stuck in a loop. The only way to recover is the unplug the USB cable and reboot it. It does not happen every time but often enough. We did produce a fix that is a software update of the firmware on the USBi itself. I am not sure what the new REV will be, either V1.4 or V1.3-D. It will also take a while for this to show up in distribution. So I do not have all the answers right now.
Regarding the I2C pull-ups. There are 10K pull-up on the USBi board. R1 and R2. So this may have been why your board was only working with the USBi connected. If you have a lot of I2C devices on the bus then there may be a lot of capacitance slowing down the signal edges. So adding another weak pull-up may have been enough to make the difference.
Dave T
Hi Dave,
How do we access the latest firmware and update our USBi interface boards?
I'm also experiencing what seems to be a lock up issue with the USBi interface and the ADAU1701 in my design. It happens very often especially when I'm using level detector meters in my schematic. If I don't enable these detectors (via the rocker switch provided in the block) then it happens a lot less often, if at all. Is there correlation between these meters and perhaps the amount of data having to be sent up/down the USBi interface via I2C in order to graphically display the volume level on the meter?
I'm using SigmaStudio3.12 beta but has happened with previous versions for as long as I can remember...
Alex
Hello Alex,
Sorry for the delay. We been discussing internally how to handle updates of customer's units. For right now if you return it to me directly then we will either swap it out with a new/reprogrammed unit or reprogram your existing unit. So contact me directly and I will reply with the shipping address. This goes for anyone else who is having problems and is reading this post.
Regarding your questions about the level detectors. Yes, it does place a higher communication's burden on the USBi when the meters are enabled. The more meters the higher the communications traffic. So only turn on the meters that you are actively looking at is a good practice.
Thanks,
Dave T
This question has been assumed as answered either offline via email or with a multi-part answer. This question has now been closed out. If you have an inquiry related to this topic please post a new question in the applicable product forum.
Thank you,
EZ Admin
Please log in to reply.