BTW, you can use the dtc command to decompile the dtbo - will not generate the source as was but you can have an idea of what there are inside the file.
Em ter., 19 de jan. de 2021 às 00:23, Vinicius Juvinski < [email protected]> escreveu: > Great :) > > to load the dtbo you need to copy inside the /lib/firmware and add in one > of uboot_overlay_addr0=/lib/firmware/<file0>.dtbo (can be 0, 1, 2 or 3) the > name of your dtbo file: > ex:. > uboot_overlay_addr0=/lib/firmware/univ-bbgw-Ex-00A0.dtbo > > but if is working, is working :) > > Em ter., 19 de jan. de 2021 às 00:09, Yendor <[email protected]> > escreveu: > >> Sorry spoke to soon I now have eth0 in ifconfig (Happy Days): >> >> ifconfig -a >> can0: flags=128<NOARP> mtu 16 >> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >> txqueuelen 10 (UNSPEC) >> RX packets 0 bytes 0 (0.0 B) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> device interrupt 42 >> >> can1: flags=128<NOARP> mtu 16 >> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >> txqueuelen 10 (UNSPEC) >> RX packets 0 bytes 0 (0.0 B) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> device interrupt 43 >> >> eth0: flags=-28605<UP,BROADCAST,RUNNING,MULTICAST,DYNAMIC> mtu 1500 >> inet 192.168.1.112 netmask 255.255.255.0 broadcast 192.168.1.255 >> inet6 fe80::1642:fcff:fee7:1793 prefixlen 64 scopeid 0x20<link> >> ether 14:42:fc:e7:17:93 txqueuelen 1000 (Ethernet) >> RX packets 1589 bytes 278073 (271.5 KiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 201 bytes 22179 (21.6 KiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> device interrupt 55 >> >> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 >> inet 127.0.0.1 netmask 255.0.0.0 >> inet6 ::1 prefixlen 128 scopeid 0x10<host> >> loop txqueuelen 1000 (Local Loopback) >> RX packets 88 bytes 7389 (7.2 KiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 88 bytes 7389 (7.2 KiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >> inet 192.168.7.2 netmask 255.255.255.0 broadcast 192.168.7.255 >> inet6 fe80::1642:fcff:fee7:1795 prefixlen 64 scopeid 0x20<link> >> ether 14:42:fc:e7:17:95 txqueuelen 1000 (Ethernet) >> RX packets 1100 bytes 163004 (159.1 KiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 282 bytes 77966 (76.1 KiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> usb1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 >> inet 192.168.6.2 netmask 255.255.255.0 broadcast 192.168.6.255 >> ether 14:42:fc:e7:17:99 txqueuelen 1000 (Ethernet) >> RX packets 0 bytes 0 (0.0 B) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> >> >> On Tuesday, January 19, 2021 at 1:00:12 PM UTC+10 Yendor wrote: >> >>> A little more info, >>> >>> I reached out to support at Seeed and they where able to send me a dtbo >>> and vEnv.txt files (Big thank you to Seeed for doing that) but the gate >>> isn't open source and this is about all the help they can give. >>> >>> They gave me a univ-bbgw-Ex-00A0.dtbo which is different to the found in >>> lib/firmware on the "AM3358 Debian 10.3 2020-04-06 4GB SD IoT" I'm current >>> running, so not knowing much I copied over the dtbo over the default one >>> and rebooted, no difference. >>> >>> so the question is, how do I use this new dtbo file? >>> >>> uEnv.txt nothing really stood out (besides disabling the wireless, would >>> have thought the video and audio should be disabled too): >>> >>> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 >>> >>> uname_r=4.9.80-ti-r98 >>> #uuid= >>> #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/<file0>.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/<file4>.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) >>> #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 cape_universal=enable >>> >>> #In the event of edid real failures, uncomment this next line: >>> #cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable >>> 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 cape_universal=enable >>> 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 >>> >>> On Tuesday, January 19, 2021 at 7:44:21 AM UTC+10 Yendor wrote: >>> >>>> output of version.sh: >>>> >>>> git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46] >>>> eeprom:[A335BNLTGW1ASENSECAP1905] >>>> model:[TI_AM335x_BeagleBone_Green_Wireless] >>>> dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06] >>>> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot >>>> 2019.04-00002-g07d5700e21]:[location: dd MBR] >>>> UBOOT: Booted Device-Tree:[am335x-bonegreen-wireless-uboot-univ.dts] >>>> UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0] >>>> UBOOT: Loaded Overlay:[BB-ADC-00A0] >>>> UBOOT: Loaded Overlay:[BB-BBGW-WL1835-00A0] >>>> UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0] >>>> kernel:[4.19.94-ti-r42] >>>> nodejs:[v10.15.2] >>>> /boot/uEnv.txt Settings: >>>> uboot_overlay_options:[enable_uboot_overlays=1] >>>> >>>> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo] >>>> uboot_overlay_options:[enable_uboot_cape_universal=1] >>>> pkg check: to individually upgrade run: [sudo apt install >>>> --only-upgrade <pkg>] >>>> pkg:[bb-cape-overlays]:[4.14.20200403.0-0rcnee0~buster+20200403] >>>> pkg:[bb-wl18xx-firmware]:[1.20200322.0-0rcnee0~buster+20200322] >>>> pkg:[kmod]:[26-1] >>>> pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~buster+20190327] >>>> pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305] >>>> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video >>>> plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc >>>> admin spi iio docker tisdk weston-launch xenomai cloud9ide] >>>> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 >>>> root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M >>>> net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet] >>>> dmesg | grep remote >>>> [ 11.325862] remoteproc remoteproc0: 4a334000.pru is available >>>> [ 11.337638] remoteproc remoteproc1: 4a338000.pru is available >>>> dmesg | grep pru >>>> [ 11.325862] remoteproc remoteproc0: 4a334000.pru is available >>>> [ 11.326048] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 >>>> probed successfully >>>> [ 11.337638] remoteproc remoteproc1: 4a338000.pru is available >>>> [ 11.337829] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 >>>> probed successfully >>>> dmesg | grep pinctrl-single >>>> [ 0.917887] pinctrl-single 44e10800.pinmux: 142 pins, size 568 >>>> dmesg | grep gpio-of-helper >>>> [ 0.930374] gpio-of-helper ocp:cape-universal: ready >>>> lsusb >>>> Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub >>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>>> END >>>> >>>> uEVnv.txt: >>>> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 >>>> >>>> uname_r=4.19.94-ti-r42 >>>> #uuid= >>>> #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/<file0>.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/<file4>.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.14.x-ti kernel) >>>> #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo >>>> ###pru_rproc (4.19.x-ti kernel) >>>> uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo >>>> ###pru_uio (4.14.x-ti, 4.19.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 lpj=1990656 >>>> rng_core.default_quality=100 quiet >>>> >>>> #In the event of edid real failures, uncomment this next line: >>>> #cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 >>>> rng_core.default_quality=100 quiet video=HDMI-A-1:1024x768@60e >>>> >>>> ##enable Generic eMMC Flasher: >>>> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh >>>> >>>> >>>> Looks like nothing is assigned to the dtb, I'll give assigning >>>> 'am335x-boneblack-emmc-overlay.dtb' in the uEnv.txt a go a see what it >>>> looks like, as I don't think the green-wirelees has a ethernet socket? >>>> >>>> On Tuesday, January 19, 2021 at 7:35:39 AM UTC+10 [email protected] >>>> wrote: >>>> >>>>> Ok >>>>> >>>>> Could you please run the version.sh script under >>>>> /opt/scripts/tools/version.sh >>>>> >>>>> Take a look at the /boot/uEnv.txt a line dtb= >>>>> If is commented -with a #dtb= or if there is dtb=anything >>>>> >>>>> >>>>> >>>>> Sent from my iPhone >>>>> >>>>> >>>>> Em 18 de jan. de 2021, à(s) 18:01, Yendor <[email protected]> >>>>> escreveu: >>>>> >>>>> Hi, >>>>> >>>>> >>>>> Had to google device tree blob (DTB), so the short answer is I don't >>>>> know. But I found a command that may shed some light >>>>> >>>>> cat /proc/device-tree/model: >>>>> TI AM335x BeagleBone Green Wireless >>>>> >>>>> if you want to see the output of some commands just let me know, >>>>> thanks for the help. >>>>> >>>>> On Tuesday, January 19, 2021 at 6:18:11 AM UTC+10 >>>>> [email protected] wrote: >>>>> >>>>>> >>>>>> Hi >>>>>> >>>>>> What dtb you are using? >>>>>> There is any message regarding Ethernet on the dmesg? >>>>>> >>>>>> >>>>>> >>>>>> Em seg., 18 de jan. de 2021 às 16:48, Yendor <[email protected]> >>>>>> escreveu: >>>>>> >>>>>>> Thanks for the reply Chris, >>>>>>> It is been plug into a network with a DHCP server provide by a >>>>>>> pfsense firewall. >>>>>>> >>>>>>> I think my problem is that the standard image (AM3358 Debian 10.3 >>>>>>> 2020-04-06 4GB SD IoT) is not finding the ethernet adapter as I don't >>>>>>> see >>>>>>> it in ifconfig, I only see the ethernet over usb connections. >>>>>>> >>>>>>> note this is a customs board by SeeedStudio: >>>>>>> [image: SCG_Back.jpg][image: SCG_Front.jpg] >>>>>>> On Monday, January 18, 2021 at 7:18:27 PM UTC+10 Chris Green wrote: >>>>>>> >>>>>>>> Yendor <[email protected]> wrote: >>>>>>>> > >>>>>>>> > Hi, >>>>>>>> > Recently I got a seeedStudio senseCap LoRa gateway to try out for >>>>>>>> a LoRa >>>>>>>> > project we have coming up. Upon requesting if we could get root >>>>>>>> access to >>>>>>>> > the OS we were told that it was not been provided at this time. >>>>>>>> So I went >>>>>>>> > to explore mode and found that we could connect to the console >>>>>>>> and it >>>>>>>> > Identified itself as a beaglebone green (but could not get access >>>>>>>> with >>>>>>>> > default passwords). >>>>>>>> > >>>>>>>> > So after reading some documents and the beagleboard.org website >>>>>>>> I worked >>>>>>>> > out I could boot from a uSD and get console and ssh access with >>>>>>>> the default >>>>>>>> > password. >>>>>>>> > >>>>>>>> > But it doesn’t look like it able to start the ethernet interface >>>>>>>> and was >>>>>>>> > wondering if anyone here can help debug to why it wont >>>>>>>> start/enable. >>>>>>>> > >>>>>>>> Rather basic question, but you never know, is the BBB/Cape >>>>>>>> connected >>>>>>>> to a network that has a DHCP server on it? >>>>>>>> >>>>>>>> -- >>>>>>>> Chris Green >>>>>>>> · >>>>>>>> >>>>>>>> -- >>>>>>> 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/fa167a4a-0bcb-4111-996e-95d4a7ec349an%40googlegroups.com >>>>>>> <https://groups.google.com/d/msgid/beagleboard/fa167a4a-0bcb-4111-996e-95d4a7ec349an%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>> -- >>>>> 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/bcbb6e9c-1e2a-4128-a0be-3914bae1634an%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/beagleboard/bcbb6e9c-1e2a-4128-a0be-3914bae1634an%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> -- >> 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/0aed9829-f514-492a-8882-5ab21d769589n%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/0aed9829-f514-492a-8882-5ab21d769589n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/CAB6xwCr_nQs_wTqd4n3wQCMabormGiH5%2Bz5GTUqZB2oot8KXSw%40mail.gmail.com.
