ADUSB2Z 1.4 connection problem
Thread Summary
The user is experiencing connection issues with an ADUSB2Z 1.4 when interfacing with an ADAU1452. The problem is likely due to multiple masters on the I2C bus, causing the ADUSB2Z to not receive an ACK. The solution involves ensuring the uC is not communicating with the DSP while the ADUSB2Z is connected, and verifying the IOVDD voltage is correct (3.3V).AI Generated Content
Hello,
I got an issue with an ADUSB2Z 1.4 that is only rarely connecting to our ADAU1452.
The hardware setup is:
and I very often get the following message:
Reconnecting the USB cable, exchange USB cable, change USB port, restarting the computer, reinstalling the device-driver and updating Sigma Studio did not help to solve the issue.
Our ADUSB2Z 1.3 broke some days ago and I did not have this much trouble with it but neither could I guarantee that the 1.3 version would work now or if there is another problem.
Could someone recommend a procedure how we could find the source of the problem?
Kind regards
Audio Signal Processors
adau1452
ADUSB2Z
sigmastudio
SigmaDSP Audio Processors
I had that issue and warmings when I connected the I2C of the USBi to the master I2C port of the ADAU1452. 2 masters on the same bus ! when I connected the USBi to the slave I2C port everything worked as expected.
Hello Logoho,
There can be several reasons for this. Usually this is because there was no ACK received from the DSP and so the message appears. I have had it appear for simple things like no power on the eval board. I do not expect that in your case. So the question is why are you not getting the ACK?
basereflex is correct that the USBI cannot work in a multi-master system so if you do have another master, like a uC, then you need to be certain that it is not trying to use the bus when the USBi is using the bus.
Also, there can be an issue with the USBi in I2C comms where it hangs up when loading in large files or where there are a lot of readbacks/meters enabled in the project. This issue was fixed a couple of years ago so how old is your eval board?
It is also good to look at the I2C bus on a scope to see if it is not seeing the ACK and also be certain that the correct address is being sent. MAke sure the address pins on the DSP are stable and do not change.
What are the IOVDD voltages on your PCB? Are they up to where they should be? 3.3V? If you are using 1.8V then you need to change the USBi voltage setting.
This is a start. Let me know what you find.
Dave T
Hello,
our uC and the DSP programmer use the same I2C bus which causes the problem.
When I stop the uC communication to the DSP, everything works just fine. So I need to know when the debugger is communicating to the DSP. Is there a pin on the Programmer (EVAL-ADUSB2Z V1.4) that can be used to inform the uC that it must stop the communication to the DSP? Or do anyone have a recommendation of how to implement this?
Thx
Please log in to reply.