Hi Michael, It's a plain linux. I'm considering upgrading kernel as last option. Variscite doesn't support another kernel for this SoM so this would be a really hard work. I'm looking for a solution on this kernel and mainly trying to understand why usbhost_48m_fck is not getting enabled. I'm contacting Variscite in parallel. Thanks for your reply, best regards! 2015-11-23 16:57 GMT-02:00 Michael Trimarchi <michael@xxxxxxxxxxxxxxxxxxxx>: > Hi Daniel > > > On Mon, Nov 23, 2015 at 7:45 PM, Daniel. <danielhilst@xxxxxxxxx> wrote: >> Hi every body! >> >> I'm running a (2.6.37) kernel based on linux-omap tree >> (http://arago-project.org/git/projects/?p=linux-omap3.git;a=summary). >> The board is a SoM from Variscite (var-som-am3517). >> >> I've compiled the ehci-hcd as a module. When I enable it I got this dump: >> http://pastebin.com/5idXXBBi >> > > Do you have an android device? or it's just plain linux. > For option 2 I suggest to move on newest kernel > > Michael > >> Googling arroud I found that this can be triggered while trying to >> access uhh registers when usbhost_48m_fck is not enabled. This is what >> I think is happening since the message >> "Clock usbhost_48m_fck didn't enable in 100000 tries" is aways present >> before the crash, and since the crash happens at first read o uhh >> registers. I just can't figure out why usbhost_48m_fck is not getting >> enabled and how to check if is trully disabled. >> >> Any ideas? >> >> Thanks in advance! >> Regards, >> >> -- >> "Do or do not. There is no try" >> Yoda Master >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-omap" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- > | Michael Nazzareno Trimarchi Amarula Solutions BV | > | COO - Founder Cruquiuskade 47 | > | +31(0)851119172 Amsterdam 1018 AM NL | > | [`as] http://www.amarulasolutions.com | -- "Do or do not. There is no try" Yoda Master -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
