Additionally, this is a reason for you to buy a serial debug cable, or module. With such a device, you'd probably know exactly why the board fails to boot, or at minimum have a really good idea based on uboot output.
On Wed, Dec 14, 2016 at 5:18 PM, William Hermans <[email protected]> wrote: > That cape does work on the Beaglebone green. However, the Beaglebone > green, and Beaglebone black both have ethernet, where the Beaglebone green > wireless has a wifi network interface. So, this is an assumption but here > are two points of contention: > > > 1. Since the BBGW has wifi and the Beaglebone black has ethernet it > could be failing because of a networking interface conflict. > 2. Since all Beaglebone have an EEPROM that when flashed properly hold > a board identification string" The board file you've chosen may fail to > load at boot. > > So, if you look here: https://github.com/RobertCNelson/dtb-rebuilder/ > blob/4.4-ti/src/arm/am335x-boneblack-emmc-overlay.dts#L36 then compare it > to this: https://github.com/RobertCNelson/dtb-rebuilder/ > blob/4.4-ti/src/arm/am335x-bonegreen-wireless.dts#L36 You'll note the > difference. However I'm not convinced that is the problem. I'm thinking the > problem probably lies here: https://github.com/ > RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x- > bonegreen-wireless.dts#L12 As f you note in the BBB equivalent file here: > https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x- > boneblack-emmc-overlay.dts#L10-L13 there is no listing for the wireless > hardware module as an include file. > > With that said, it's going to be more complicated than that. As the files > for the BBB will probably not have the proper network interface > configuration for the wireless interface: ethernet versus wireless. So I'm > fairly sure just adding the #include would not work. However . . . it may > be possible that https://github.com/RobertCNelson/dtb-rebuilder/ > blob/4.4-ti/src/arm/am335x-boneblack-wireless-emmc-overlay.dts would > work. I'd double check with Robert first however. To make sure nothing bad > would happen. I wouldn't think so, but thats what I *think*, and not what I > *know* as fact. > > On Wed, Dec 14, 2016 at 4:52 PM, codemonkey <[email protected]> wrote: > >> When I uncomment "#dtb=am335x-boneblack-emmc-overlay.dtb" and add a line >> for BB-SPIDEV1 as follows: >> >> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 >> >> uname_r=4.4.38-bone-rt-r14 >> ###uuid= >> #dtb= >> >> ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..) >> >> ##BeagleBone Black: HDMI (Audio/Video) disabled: >> dtb=am335x-boneblack-emmc-overlay.dtb >> cape_enable=bone_capemgr.enable_partno=BB-SPIDEV1 >> >> ... (nothing is changed beyond this point) >> >> >> The system appears to fail during boot. This has worked for a long time >> on the BBB and I'm trying to move a running application to the BBGW. >> >> root@bbgw:/home/cd5# uname -a >> Linux bbgw 4.4.38-bone-rt-r14 #1 PREEMPT RT Mon Dec 12 10:10:25 UTC 2016 >> armv7l GNU/Linux >> >> I have also tried to use config-pin, but I haven't been able to find any >> documentation that will allow me to work through the problems. >> For example: >> >> cd5@bbgw:~$ sudo ./config-pin P8_18 low >> P8_18 pinmux file not found! >> cape-universala overlay not found >> run "config-pin overlay cape-universala" to load the cape >> root@bbgw:/home/cd5# ./config-pin overlay cape-universala >> Loading cape-universala overlay >> root@bbgw:/home/cd5# ./config-pin overlay BB-SPIDEV1 >> Loading BB-SPIDEV1 overlay >> bash: line 0: echo: write error: File exists >> Error loading device tree overlay file: BB-SPIDEV1 >> >> It appears that cape-universala loads both spidev0 and spidev1 - I need >> the spidev0 pins available for gpio >> >> Trying to push on: >> >> root@bbgw:/home/cd5# ./config-pin -l p8_18 >> default gpio gpio_pu gpio_pd >> root@bbgw:/home/cd5# ./config-pin -i p8_18 >> Pin name: P8_18 >> Function if no cape loaded: gpio >> Function if cape loaded: default gpio gpio_pu gpio_pd >> Function information: gpio2_1 default gpio2_1 gpio2_1 gpio2_1 >> Cape: cape-universala cape-universal cape-universaln >> Kernel GPIO id: 65 >> PRU GPIO id: 97 >> root@bbgw:/home/cd5# ./config-pin -q p8_18 >> Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P8_18_pinmux/state >> >> I can't see where to go from here except to post this hoping that someone >> can help with either the uEnv.txt problem or the config-pin problems. >> >> When all is configured properly I should have spidev1 (the second spi >> bus) enabled along with a long list of gpios needed for the application. >> >> Thanks in advance, >> Tim >> >> >> >> >> -- >> 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/ms >> gid/beagleboard/1546c704-46ee-41b3-8f01-ec0dbafcada6%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/1546c704-46ee-41b3-8f01-ec0dbafcada6%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/CALHSORpf-5-m7TuoW0NBzoW-8Pn4prDg7WEqqpoH3Ve9vnm4EA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
