On Tue, May 9, 2017 at 10:16 AM, Gaurav S <[email protected]> wrote:

> Hello All,
> With LCD, it seems like SPI is behaving awkwardly. I have two beagle bone
> boards one with LCD plugged in (SYS1) and the other stand alone beagle bone
> (SYS2), both running latest debian lxqt 2gb image (may 7 2017). The curious
> thing over here is that before u-boot spi was working just fine with the
> LCD.
>
> Following are the results from each of the systems:
>
> SYS1 (beaglebone + LCD4)
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.4.62-ti-r99 #1 SMP Sat Apr 22 14:21:03 UTC 2017 armv7l
> GNU/Linux
> debian@beaglebone:~$ dmesg | grep bone
> [    0.000000] Kernel command line: console=ttyO0,115200n8
> bone_capemgr.enable_partno=BB-SPIDEV1 bone_capemgr.uboot_capemgr_enabled=1
> root=UUID=e4c7e2e7-0fbf-494c-8d84-305d291d2b7a ro rootfstype=ext4
> rootwait coherent_pool=1M net.ifnames=0 quiet
> [    2.376478] bone_capemgr bone_capemgr: Baseboard:
> 'A335BNLT,00C0,2516BBBK2265'
> [    2.376509] bone_capemgr bone_capemgr: 
> compatible-baseboard=ti,beaglebone-black
> - #slots=4
> [    2.376544] bone_capemgr bone_capemgr: slot #0: auto loading handled by
> U-Boot
> [    2.376566] bone_capemgr bone_capemgr: slot #1: auto loading handled by
> U-Boot
> [    2.376587] bone_capemgr bone_capemgr: slot #2: auto loading handled by
> U-Boot
> [    2.376629] bone_capemgr bone_capemgr: slot #3: auto loading handled by
> U-Boot
> [    2.376655] bone_capemgr bone_capemgr: enabled_partno PARTNO
> 'BB-SPIDEV1' VER 'N/A' PR '0'
> [    2.376667] bone_capemgr bone_capemgr: slot #4: override
> [    2.376681] bone_capemgr bone_capemgr: slot #4: auto loading handled by
> U-Boot
> [    2.377276] bone_capemgr bone_capemgr: initialized OK.
> [    6.851318] systemd[1]: Set hostname to <beaglebone>.
> debian@beaglebone:/dev$ ls sp*
> ls: cannot access sp*: No such file or directory
>
>
>
> SYS2 (stand along beagle bone)
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.4.62-ti-r99 #1 SMP Sat Apr 22 14:21:03 UTC 2017 armv7l
> GNU/Linux
> debian@beaglebone:~$ dmesg|grep bone
> [    0.000000] Kernel command line: console=ttyO0,115200n8
> bone_capemgr.enable_partno=BB-SPIDEV1 bone_capemgr.uboot_capemgr_enabled=1
> root=UUID=599ccfe6-2803-4ea0-9141-2bb571994e70 ro rootfstype=ext4
> rootwait coherent_pool=1M net.ifnames=0 quiet
> [    2.445200] bone_capemgr bone_capemgr: Baseboard:
> 'A335BNLT,00C0,2516BBBK22E8'
> [    2.445233] bone_capemgr bone_capemgr: 
> compatible-baseboard=ti,beaglebone-black
> - #slots=4
> [    2.445270] bone_capemgr bone_capemgr: slot #0: auto loading handled by
> U-Boot
> [    2.445291] bone_capemgr bone_capemgr: slot #1: auto loading handled by
> U-Boot
> [    2.445337] bone_capemgr bone_capemgr: slot #2: auto loading handled by
> U-Boot
> [    2.445359] bone_capemgr bone_capemgr: slot #3: auto loading handled by
> U-Boot
> [    2.445379] bone_capemgr bone_capemgr: enabled_partno PARTNO
> 'BB-SPIDEV1' VER 'N/A' PR '0'
> [    2.445390] bone_capemgr bone_capemgr: slot #4: override
> [    2.445403] bone_capemgr bone_capemgr: slot #4: auto loading handled by
> U-Boot
> [    2.446010] bone_capemgr bone_capemgr: initialized OK.
> [   17.551299] systemd[1]: Set hostname to <beaglebone>.
> debian@beaglebone:~$ cd /dev
> debian@beaglebone:/dev$ ls sp*
> spidev1.0  spidev1.1  spidev2.0  spidev2.1
>

What does lsmod have to say about which drivers are loaded on each system ?

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORpkapT4JWQDhUhiyKOdJx7svii9ZB%2B-5j%2BTa2ow5J%2BZQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to