Hi, same issue here. I get the following error when trying to load the slot:
[ 1598.682521] bone-capemgr bone_capemgr.8: part_number 'bone_eqep0', version 'N/A' [ 1598.682703] bone-capemgr bone_capemgr.8: slot #9: generic override [ 1598.682754] bone-capemgr bone_capemgr.8: bone: Using override eeprom data at slot 9 [ 1598.682805] bone-capemgr bone_capemgr.8: slot #9: 'Override Board Name,00A0,Override Manuf,bone_eqep0' [ 1598.683068] bone-capemgr bone_capemgr.8: slot #9: Requesting part number/version based 'bone_eqep0-00A0.dtbo [ 1598.683121] bone-capemgr bone_capemgr.8: slot #9: Requesting firmware 'bone_eqep0-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 1598.683625] bone-capemgr bone_capemgr.8: slot #9: dtbo 'bone_eqep0-00A0.dtbo' loaded; converting to live tree [ 1598.688201] of_resolve: Could not find symbol 'eqep0' [ 1598.693733] bone-capemgr bone_capemgr.8: slot #9: Failed to resolve tree I also tried to recompile the DTS but I get the same error. Could you please help? I'm working on the following kernel: Linux beaglebone 3.8.13-bone32 #3 SMP Mon Jan 13 18:02:42 CET 2014 armv7l GNU/Linux Thanks Lorenzo Il giorno mercoledì 8 gennaio 2014 23:54:41 UTC+1, [email protected] ha scritto: > > Hi: > > Can you make the eqep driver works? > I need some help, because I can't....I trying and trying.....and nothing. > I rebuild the kernel with EQEP, but when I try load the dtbo files, always > the same: -sh - invalid argument..... > I can load other capes, like pwm etc....but not the eqep driver. > > I really apreciate if you can share some information... > > Thanks > > Em quarta-feira, 24 de julho de 2013 14h19min13s UTC-3, tbh escreveu: >> >> My overall goal is like the title says: I need to read a quad encoder >> count, and I have a beaglebone black. Eventually, I'll be using c++. Any >> help on how to proceed or links on things I should read are appreciated. >> >> I've seen 3 ways of reading an encoder on the beaglebone: (1)polling >> GPIO >> pins<http://bwgz57.wordpress.com/2012/04/11/beaglebone-with-a-rotary-encoder/>, >> >> (2)using interrupts in a kernel driver, and (3)using the eQEP built in to >> the hardware of the beaglebone SOC. I'm interested in (3) because it seems >> to me that it would be the most efficient. However, it seems like most >> people are using (2), and I can't find a whole lot on how to do (3). >> >> Here's what I have found so far in case it's useful to anyone else. >> - the TRM for the bealgebone >> SOC<http://www.ti.com/lit/ug/spruh73h/spruh73h.pdf>. >> Section 15.4 is where the eQEP is documented. >> - A thread >> here<https://groups.google.com/forum/embed/?place=forum/beagleboard&showsearch=true&showpopout=true&showtabs=true&hideforumtitle=true&parenturl=http%3A%2F%2Fbeagleboard.org%2FCommunity%2FForums#%21searchin/beagleboard/quadrature/beagleboard/GzRSJYjs60M/Vs67S0SRon4J>apparently >> about enhancing an already working eQEP driver. >> - A thread from the TI Community asking about linux drivers for >> eQEP<http://e2e.ti.com/support/arm/sitara_arm/f/791/t/276433.aspx> >> . >> - A wiki page from a TI presentation about using eQEP with one of their >> dev >> boards<http://processors.wiki.ti.com/index.php/Omapl137_linux_eqep_driver> >> . >> - Two threads with the same original post, and slightly different >> responses. They are a bit over my head. >> thread1<http://comments.gmane.org/gmane.linux.kernel.input/21481> >> thread2 <http://en.it-usenet.org/thread/18798/20687/> >> - A reference in some comments on a blog >> post<http://bwgz57.wordpress.com/2012/04/11/beaglebone-with-a-rotary-encoder/>that >> they got an eQEP driver working to read a quad encoder (but without >> any explanation). >> >> I know people are working on the problem of making (3) easy to use. Is >> there some other link on how to do it that is eluding me? >> >> If there's not, in the meantime, I'm interested in device drivers, and I >> think it's practical information, so I'd like to learn as much about them >> as I can. Perhaps I'll even get to the point where I can help the ongoing >> eQEP effort. I'm rather inexperienced in driver writing, though. I've been >> wading through the linux device drivers book<http://lwn.net/Kernel/LDD3/>, >> so I guess that's a start. However, I've never recompiled my own kernel, >> which it looks like I'll probably have to do, and I've never even >> cross-compiled. Could somebody help me out with a place to start? >> >> In the meantime, I'll be looking at method (2). Thanks in advance. >> > -- 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/groups/opt_out.
