On Sun, Dec 28, 2014 at 5:51 PM, Rick Mann <[email protected]> wrote: > After re-tracing my steps, I'm still no closer to figuring this out. One > thing I did notice is that the first time I tried to apply the overlay, the > log showed a failure and a second attempt: > > [31360.880445] bone-capemgr bone_capemgr.9: part_number 'podtique', version > 'N/A' > [31360.880629] bone-capemgr bone_capemgr.9: slot #8: generic override > [31360.880675] bone-capemgr bone_capemgr.9: bone: Using override eeprom data > at slot 8 > [31360.880722] bone-capemgr bone_capemgr.9: slot #8: 'Override Board > Name,00A0,Override Manuf,podtique' > [31360.880984] bone-capemgr bone_capemgr.9: slot #8: Requesting part > number/version based 'podtique-00A0.dtbo > [31360.881031] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware > 'podtique-00A0.dtbo' for board-name 'Override Board Name', version '00A0' > [31360.917917] bone-capemgr bone_capemgr.9: failed to load firmware > 'podtique-00A0.dtbo' > > [31428.883458] bone-capemgr bone_capemgr.9: part_number 'podtique', version > 'N/A' > [31428.883639] bone-capemgr bone_capemgr.9: slot #9: generic override > [31428.883686] bone-capemgr bone_capemgr.9: bone: Using override eeprom data > at slot 9 > [31428.883734] bone-capemgr bone_capemgr.9: slot #9: 'Override Board > Name,00A0,Override Manuf,podtique' > [31428.883989] bone-capemgr bone_capemgr.9: slot #9: Requesting part > number/version based 'podtique-00A0.dtbo > [31428.884037] bone-capemgr bone_capemgr.9: slot #9: Requesting firmware > 'podtique-00A0.dtbo' for board-name 'Override Board Name', version '00A0' > [31428.890324] bone-capemgr bone_capemgr.9: slot #9: dtbo > 'podtique-00A0.dtbo' loaded; converting to live tree > [31428.890721] bone-capemgr bone_capemgr.9: slot #9: #2 overlays > [31428.891182] bone-capemgr bone_capemgr.9: slot #9: Applied #2 overlays. > > Then I removed it and tried again. > > Also, when it says "Using override eeprom data at slot 8," what does that > mean? I have a physical cape attached, a SparkFun prototype cape with EEPROM, > but the EEPROM is unflashed (I assume). If I can get this manual overlay to > work, I'll next try to flash the EEPROM with the right stuff to get it all > loaded at boot.
The capemgr in v3.8.x is setup to read the eeprom, so when we echo a custom overlay... It's just very vocal that it's just not using the eeprom.. Nothing to worry about.. > Robert, I have yet to try the steps you gave me earlier for building a new > kernel with the USB changes for audio. I don't know if that kernel would make > a difference? It might... Disabling DMA mode seems to help some usb devices. On every kernel release, ti keep's adding more workarounds, so at some point, dma on the musb will be stable.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
