Marvell Wireless Upgrades: Hubs on other USB ports cause failures!
|Reported by:||mfoster||Owned by:||rchokshi|
|Keywords:||Cc:||alanc@…, rchokshi@…, marcelo|
|Deployments affected:||Action Needed:|
After many hours at the USB protocol analyzer, we can see some device combinations that routinely induce Boot2 upgrade or downgrade failures on the Marvell wireless module. All of these tests were performed booting from NAND.
Specifically, if a USB2 hub is present on one of the system's USB ports, with a USB1 device attached to it, the wireless upgrade will fail with nearly 100% certainty. It appears that the presence of the Split transactions which occur in this configuration confuse the Marvell module.
USB Protocol data for this failure is at:
If a USB2 hub is present on one of the system's USB ports with a USB2 device attached to it, there is a very high probability that the wireless upgrade will fail.
If a USB2 hub is present on one of the system's USB ports with no USB devices attached, the wireless upgrade will succeed.
Note that it is the character of the USB traffic which appears to determine success of firmware upgrades. IMPORTANT NOTE is that we believe that the failures seen during programming attempts correlate well with failures loading the runtime RAM-based code in the normal driver.
Change History (18)
Changed 10 years ago by mfoster
comment:9 follow-up: ↓ 10 Changed 10 years ago by jg
- Cc marcelo added
- Milestone changed from BTest-2 to BTest-3
comment:11 Changed 9 years ago by jg
- Component changed from distro to wireless
- Priority changed from blocker to high
comment:14 follow-up: ↓ 15 Changed 9 years ago by jg
- Owner changed from mbletsas to rchokshi
- Verified unset