after uncommenting the line:
*#dtb=am335x-boneblack-overlay.dtb *

...my beaglebone has trouble loading the kernel and drops to a shell.  i've 
managed to record the debug output from uart0:

*Starting kernel ...*

*[    0.000453] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'*
*[    0.000463] This ensures that you still see kernel messages. Please*
*[    0.000471] update your kernel commandline.*
*[    3.554658] omap_voltage_late_init: Voltage driver support not added*
*[    3.676455] bone_capemgr bone_capemgr: slot #0: No cape found*
*[    3.736442] bone_capemgr bone_capemgr: slot #1: No cape found*
*[    3.796440] bone_capemgr bone_capemgr: slot #2: No cape found*
*[    3.856434] bone_capemgr bone_capemgr: slot #3: No cape found*
*Loading, please wait...*
*Gave up waiting for root device.  Common problems:*
* - Boot args (cat /proc/cmdline)*
*   - Check rootdelay= (did the system wait long enough?)*
*   - Check root= (did the system wait for the right device?)*
* - Missing modules (cat /proc/modules; ls /dev)*
*ALERT!  /dev/disk/by-uuid/4ccbfb5c-9e82-4bed-aa38-a0d7a10e2404 does not 
exist.  Dropping to a shell!*
*(initramfs) cat /proc/cmdline*
*console=ttyO0,115200n8 
bone_capemgr.enable_partno=BB-I2C1,BB-CAN1,BB-SPIDEV1 
root=UUID=4ccbfb5c-9e82-4bed-aa38-a0d7a10e2404 ro rootfstype=ext4 rootwait 
fixrtc coherent_pool=1M quiet*


On Tuesday, July 21, 2015 at 7:13:19 PM UTC-7, RobertCNelson wrote:
>
> On Tue, Jul 21, 2015 at 1:17 PM,  <[email protected] <javascript:>> 
> wrote: 
> > After I have enabled SPI1 using the SPI overlay everything seems to be 
> > configured correctly. However when I check the pins to see if they are 
> in 
> > the correct mode, they are still configured for gpio.  I run dmesg and 
> it 
> > outputs that these pins are already requested by mcasp. 
> > 
> > my config for the 4.1 kernel in the /boot/uEnv.txt file is: 
> > 
> > ##Example v4.1.x 
> > 
> cape_disable=bone_capemgr.disable_partno=BB-SPIDEV0,BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
>  
>
> > cape_enable=bone_capemgr.enable_partno=BB-I2C1,BB-CAN1,BB-SPIDEV1 
> > 
> > 
> > when i run the command 'ls -la /dev/spi*' it show the following: 
> > 
> > crw-rw---- 1 root spi 153, 1 Jul 21 17:18 /dev/spidev1.0 
> > crw-rw---- 1 root spi 153, 0 Jul 21 17:18 /dev/spidev1.1 
> > 
> > 
> > However the pins are still configured to be gpio: 
> > 
> > root@beaglebone:/sys/kernel/debug/pinctrl/44e10800.pinmux# more pins 
> > 
> > ... 
> > 
> > pin 100 (44e10990.0) 00000027 pinctrl-single 
> > pin 101 (44e10994.0) 00000027 pinctrl-single 
> > pin 102 (44e10998.0) 00000027 pinctrl-single 
> > pin 103 (44e1099c.0) 00000027 pinctrl-single 
> > 
> > ... 
> > 
> > 
> > but... 
> > root@beaglebone:~# cat /sys/devices/platform/bone_capemgr/slots 
> >  0: PF----  -1 
> >  1: PF----  -1 
> >  2: PF----  -1 
> >  3: PF----  -1 
> >  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-I2C1 
> >  5: P-O-L-   1 Override Board Name,00A0,Override Manuf,BB-CAN1 
> >  6: P-O-L-   2 Override Board Name,00A0,Override Manuf,BB-SPIDEV1 
> > 
> > 
> > Also, when i run dmesg i get: 
> > 
> > root@beaglebone:~# dmesg | grep spi 
> > [   18.526603] pinctrl-single 44e10800.pinmux: pin 44e10990.0 already 
> > requested by 48038000.mcasp; cannot claim for 481a0000.spi 
> > [   19.028093] pinctrl-single 44e10800.pinmux: pin-100 (481a0000.spi) 
> status 
> > -22 
> > [   19.162354] pinctrl-single 44e10800.pinmux: could not request pin 100 
> > (44e10990.0) from group pinmux_bb_spi1_pins  on device pinctrl-single 
> > [   20.010557] omap2_mcspi 481a0000.spi: Error applying setting, reverse 
> > things back 
>
> mcasp = hdmi audio... 
>
> Since you want: 
>
> > 
> cape_disable=bone_capemgr.disable_partno=BB-SPIDEV0,BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
>  
>
>
> set: 
>
> dtb=am335x-boneblack-overlay.dtb 
>
> in /boot/uEnv.txt 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://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.

Reply via email to