-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRC error with Sony STR-DH550 #10
Comments
Looks like a USB/HID packet is lost. Could be hardware or software bug/problem.
|
I use Raspberry PI Zero W with custom kernel 4.14.37+. Are there some specific things you'd need to know? You can find the relevant part of dmesg log (kern.log) from https://pastebin.com/RTvyqTdt |
I tried this again with the latest version of the driver and the "ipod" userspace program, and now there is no CRC errors anymore and the gadget is detected by the amplifier. However, I cannot get the speaker-test to work, running
seems to run for about 10 seconds but no sound is heard. After that, it dies with last messages:
Any hints on what might be the issue? EDIT2: Realized I can attach the trace file instead of using pastebin, here it is: Also I noticed that using any the amplifier's OSD to navigate the contents (with the default "ipod" userspace app) the amplifier hangs when selecting anything (like artists). I assume this is a limitation of the userspace app? |
Hi.
I got the driver and the userspace application to work and tested the driver with my Sony STR-DH550 amplifier. The amplifier tries to read the "iPod" but I see that the process (the "ipod" userspace program) shows a CRC error:
ERRO[0025.020803] << PACKET error=packet decode: crc mismatch: recv 53 != calc 8c len=0
ERRO[0025.021055] << PACKET error=packet decode: crc mismatch: recv 70 != calc 94 len=0
I uploaded the trace file to https://pastebin.com/TUa5nt4U
In the file, the process runs for a while, then stops to the CRC error. After a while it runs ok for some time and then another CRC error appers. That's when I stopped the trace.
Any ideas what might be wrong?
The text was updated successfully, but these errors were encountered: