21 Replies Latest reply on Jul 18, 2019 11:44 AM by chicagobob

    wireless cape bricks the beaglebone

    chicagobob

      Latest img https://beagleboard.org/latest-images

      Follow the directions and the beagle board no longer boots.

      GREAT !!

      What is going on?

      Edit

      /boot/uEnv.txt

      > sudo nano /boot/uEnv.txt

      # Enable the overlay dtb

      (eMMC/hdmi/etc are disabled)

      dtb=am335x-boneblack-overlay.dtb

      # Enable the gateway/connectivity cape overlay:

      cape_enable=bone_capemgr.enable_partno=BB-BONE-WL183

      Write out & save edits.

        • Re: wireless cape bricks the beaglebone
          shabaz

          Hi Robert,

           

          I don't know the answer, but I know how to begin troubleshooting such types of issues.

          It will be worth removing any cape (in case it is interfering with the boot mode pins) and trying to start up the BBB without it.

          If that doesn't work, you could try other things like checking the supply and new image, but really you'll likely need a USB UART adapter connected to the serial console pins on the BBB. so that you can see what Linux is printing out upon startup, in case it is getting stuck somewhere. Ultimately you may need to burn a fresh image and try that, if it is getting stuck due to (say) corruption. But you won't know that for sure, until the serial output is monitored.

          3 of 3 people found this helpful
          • Re: wireless cape bricks the beaglebone
            jomoenginer

            Brink from my perspective means the board will no longer function thus it is like a brink laying on the table.  Is this the situation you are in now, or does the BB Black boot without the Wireless Cape installed?

             

            Which Wireless Cape do you have?

             

            The notes you have are more than likely from an older OS version for the BB Black, so if you are using the latest Debian 9.5 build, then I believe you do not have to perform these these steps; it should work out of the box.

            1 of 1 people found this helpful
            • Re: wireless cape bricks the beaglebone
              chicagobob

              Thanks so much for the replies. Sorry for the lack of clarity.

               

              I am trying to get the Element 14 wireless cape working on the Beagle bone black with the latest debian.

              These are new items purchased in the last 30 days.

               

              After making the changes to the /boot/uEnv.txt as instructed in the readme file I was not able to access the board via Putty again.

              Power lights blinking but no access. That OS will need to be replaced. 

              So I got an SD card and modified that. With the cape plugged in I was not able to access to the board via putty and HDMI is disabled

              but removing the cape allowed me access to the card again, Thanks for that advice.

              So far this has been a total let down. I am used to buying something plugging it in and it working if you follow the directions. Guess thats not the case.

               

              "but really you'll likely need a USB UART adapter connected to the serial console pins on the BBB. so that you can see what Linux is printing out upon startup"

              I don't have one and it seems that is the only solution since the directions on the element 14 website do not work.

              When  you look online you get a bunch of conflicting information so that's not helping.

              I will document this after its working as I try combinations of guesses and who knows what, to get this thing working.

              So far no luck.

              Why is something sold so hard to install

              1 of 1 people found this helpful
                • Re: wireless cape bricks the beaglebone
                  jomoenginer

                  Yeah, the BB Black is really just a dev board so it's basically "Plug and Pray".   However, many times the documentation for a device is for a specific image version so an attempt to use something else usually involves some discovery from the user.

                   

                  Have you tried it without making the edits in the uEnv.txt?  That is, just leave it at the defaults from where the image was burnt on the uSD card.

                   

                  Have you tried the BeagleBone forums?

                • Re: wireless cape bricks the beaglebone
                  chicagobob

                  Yes I have tried doing this without the uEnv.txt edits. The wifi cape lights do not even turn on and

                  worst part is when I get the turned on, I can not log into the beagleboard

                  1 of 1 people found this helpful
                  • Re: wireless cape bricks the beaglebone
                    chicagobob

                    More notes.  modified the uEnv.txt

                    using

                    uboot_overlay_addr0=/lib/firmware/BB-GATEWAY-WL1837-00A0.dtbo

                    this is the results.

                     

                    [    1.531472] bone_capemgr bone_capemgr: Invalid signature 'ffffffff' at slot 0

                    [    1.538694] bone_capemgr bone_capemgr: slot #0: No cape found

                    [    1.563883] bone_capemgr bone_capemgr: slot #1: No cape found

                    [    1.587457] usb 1-1: new full-speed USB device number 2 using musb-hdrc

                    [    1.592196] bone_capemgr bone_capemgr: slot #2: No cape found

                    [    1.620774] bone_capemgr bone_capemgr: slot #3: No cape found

                    [    1.620796] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-BONE-WL183'                                                                   VER 'N/A' PR '0'

                    [    1.620806] bone_capemgr bone_capemgr: slot #4: override

                    [    1.620819] bone_capemgr bone_capemgr: Using override eeprom data at slot 4

                    [    1.620833] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Ove                                                                  rride Manuf,BB-BONE-WL183'

                    [    1.621200] bone_capemgr bone_capemgr: initialized OK.

                    [    1.626133] bone_capemgr bone_capemgr: loader: failed to load slot-4 BB-BONE-                                                                  WL183:00A0 (prio 0)

                     

                    My uEnv.txt

                     

                    #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

                    uname_r=4.14.71-ti-r80

                    #uuid=

                    #dtb=am335x-boneblack-wl1835mod.dtb

                     

                    ###U-Boot Overlays###

                    ###Documentation: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

                    ###Master Enable

                    enable_uboot_overlays=1

                    ###

                    ###Overide capes with eeprom

                    uboot_overlay_addr0=/lib/firmware/BB-GATEWAY-WL1837-00A0.dtbo

                    #uboot_overlay_addr1=/lib/firmware/<file1>.dtbo

                    #uboot_overlay_addr2=/lib/firmware/<file2>.dtbo

                    #uboot_overlay_addr3=/lib/firmware/<file3>.dtbo

                    ###

                    ###Additional custom capes

                    # uboot_overlay_addr4=/lib/firmware/BB-GATEWAY-WL1837-00A0.dtbo

                    #uboot_overlay_addr5=/lib/firmware/<file5>.dtbo

                    #uboot_overlay_addr6=/lib/firmware/<file6>.dtbo

                    #uboot_overlay_addr7=/lib/firmware/<file7>.dtbo

                    ###

                    ###Custom Cape

                    #dtb_overlay=/lib/firmware/<file8>.dtbo

                    ###

                    ###Disable auto loading of virtual capes (emmc/video/wireless/adc)

                    disable_uboot_overlay_emmc=1

                    disable_uboot_overlay_video=1

                    disable_uboot_overlay_audio=1

                    #disable_uboot_overlay_wireless=1

                    #disable_uboot_overlay_adc=1

                    ###

                    ###PRUSS OPTIONS

                    ###pru_rproc (4.4.x-ti kernel)

                    #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo

                    ###pru_rproc (4.14.x-ti kernel)

                     

                     

                    # was not commented.

                    #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo

                     

                     

                    ###pru_uio (4.4.x-ti, 4.14.x-ti & mainline/bone kernel)

                    #uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo

                    ###

                    ###Cape Universal Enable

                    # enable_uboot_cape_universal=1

                    ###

                    ###Debug: disable uboot autoload of Cape

                    #disable_uboot_overlay_addr0=1

                    #disable_uboot_overlay_addr1=1

                    #disable_uboot_overlay_addr2=1

                    #disable_uboot_overlay_addr3=1

                    ###

                    ###U-Boot fdt tweaks... (60000 = 384KB)

                    #uboot_fdt_buffer=0x60000

                    ###U-Boot Overlays###

                     

                     

                    cmdline=coherent_pool=1M net.ifnames=0 quiet

                     

                     

                    #In the event of edid real failures, uncomment this next line:

                    #cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e

                     

                     

                    #Use an overlayfs on top of a read-only root filesystem:

                    #cmdline=coherent_pool=1M net.ifnames=0 quiet overlayroot=tmpfs

                     

                     

                    ##enable Generic eMMC Flasher:

                    ##make sure, these tools are installed: dosfstools rsync

                    #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

                    cape_enable=bone_capemgr.enable_partno=BB-BONE-WL183

                    • Re: wireless cape bricks the beaglebone
                      chicagobob

                      The Mystery continues. Why would

                      I have tried

                      dtb=am335x-boneblack-overlay.dtb

                      and

                      dtb=/boot/dtbs/4.14.71-ti-r80/am335x-boneblack-overlay.dtb

                      Both return that it could not find the file and did I name it correctly.

                      unable to find [dtb=/boot/dtbs/4.14.71-ti-r80/am335x-boneblack-overlay.dtb] did

                      you name it correctly? ...

                       

                      Then it goes FAILSAFE U-Boot which I think switches over the EMMC I think and things get worse from there.

                       

                      FAILSAFE: U-Boot UMS (USB Mass Storage) enabled, media now available over the us

                      b slave port ...

                      Unknown command 'ums' - try 'help'

                      loading /boot/initrd.img-4.14.71-ti-r80 ...

                      4530240 bytes read in 278 ms (15.5 MiB/s)

                      debug: [console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-BONE-WL183 root=/de

                      v/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet] ..

                      .

                      debug: [bootz 0x82000000 0x88080000:452040 0x88000000] ...

                      Kernel image @ 0x82000000 [ 0x000000 - 0x9ef200 ]

                      ERROR: Did not find a cmdline Flattened Device Tree

                      Could not find a valid device tree

                      ** Invalid partition 2 **

                      ** Invalid partition 3 **

                      ** Invalid partition 4 **

                      ** Invalid partition 5 **

                      ** Invalid partition 6 **

                      ** Invalid partition 7 **

                      switch to partitions #0, OK

                      mmc1(part 0) is current device

                      Scanning mmc 1:1...

                      gpio: pin 56 (gpio 56) value is 0

                      gpio: pin 55 (gpio 55) value is 0

                      gpio: pin 54 (gpio 54) value is 0

                      gpio: pin 53 (gpio 53) value is 1

                      switch to partitions #0, OK

                      mmc1(part 0) is current device

                      gpio: pin 54 (gpio 54) value is 1

                      Checking for: /uEnv.txt ...

                      Checking for: /boot.scr ...

                      Checking for: /boot/boot.scr ...

                      Checking for: /boot/uEnv.txt ...

                      gpio: pin 55 (gpio 55) value is 1

                      1682 bytes read in 16 ms (102.5 KiB/s)

                      Loaded environment from /boot/uEnv.txt

                      Using: dtb=am335x-boneblack-wl1835mod.dtb ...

                      Checking if uname_r is set in /boot/uEnv.txt...

                      gpio: pin 56 (gpio 56) value is 1

                      Running uname_boot ...

                      loading /boot/vmlinuz-4.1.15-ti-rt-r43 ...

                      7800752 bytes read in 443 ms (16.8 MiB/s)

                      loading /boot/dtbs/4.1.15-ti-rt-r43/am335x-boneblack-wl1835mod.dtb ...

                      60445 bytes read in 41 ms (1.4 MiB/s)

                      loading /boot/initrd.img-4.1.15-ti-rt-r43 ...

                      4096241 bytes read in 241 ms (16.2 MiB/s)

                      debug: [console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-BONE-WL183 root=UUI

                      D=9339406c-6b8c-4d44-b126-0f99bdea7c3f ro rootfstype=ext4 rootwait coherent_pool

                      =1M quiet cape_universal=enable] ...

                      debug: [bootz 0x82000000 0x88080000:3e80f1 0x88000000] ...

                      Kernel image @ 0x82000000 [ 0x000000 - 0x7707b0 ]

                      ## Flattened Device Tree blob at 88000000

                         Booting using the fdt blob at 0x88000000

                         Loading Ramdisk to 8fc17000, end 8ffff0f1 ... OK

                         Loading Device Tree to 8fc05000, end 8fc16c1c ... OK

                       

                       

                      Starting kernel ...

                       

                       

                      [    3.486284] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle

                      [    3.790699] cpu cpu0: cpu0 clock notifier not ready, retry

                      [    5.963706] bone_capemgr bone_capemgr: slot #0: No cape found

                      [    8.043704] bone_capemgr bone_capemgr: slot #1: No cape found

                      [   10.123700] bone_capemgr bone_capemgr: slot #2: No cape found

                      [   12.203700] bone_capemgr bone_capemgr: slot #3: No cape found

                      Loading, please wait...

                      fsck from util-linux 2.25.2

                      /init: 379: /init: touch: not found

                      Usage: mount [-r] [-w] [-o options] [-t type] [-f] [-i] [-n] device directory

                      Target filesystem doesn't have requested /sbin/init.

                      [   13.224018] bone_capemgr bone_capemgr: loader: failed to load slot-4 BB-BONE-

                      WL183:00A0 (prio 0)

                      mount: No such file or directory

                      Could not copy file: No such file or directory

                      No init found. Try passing init= bootarg.

                      (initramfs)

                       

                      Oh well the saga continues.

                      • Re: wireless cape bricks the beaglebone
                        chicagobob

                        I have found thing out. The reason I can not log into the Beagle when it looks like the WIFi is working is because it seems to be deadlocked.

                        Not sure what to do with that. If I get a chance later today I can update it.