On Tue, Jul 18, 2017 at 12:49 AM, Nguyễn Hồng Quân <[email protected]> wrote:
> Hi Robert > > That /boot/uEnv.txt still doesn't work. > > Here is my content: > > ###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/BB-UART1-00A0.dtbo > #uboot_overlay_addr5=/lib/firmware/<file5>.dtbo > #uboot_overlay_addr6=/lib/firmware/<file6>.dtbo > #uboot_overlay_addr7=/lib/firmware/<file7>.dtbo > > But after restarting BBB, the slot 4 is still absent: > > $ cat /sys/devices/platform/bone_capemgr/slots > 0: ---l-- -1 > 1: ------ -1 > 2: ---l-- -1 > 3: ---l-- -1 > > Log at the stage of cape_mgr initialization: > > $ journalctl > Feb 11 16:28:01 arm kernel: bone_capemgr bone_capemgr: Baseboard: > 'A335BNLT,00C0,2016BBBK2436' > Feb 11 16:28:01 arm kernel: bone_capemgr bone_capemgr: > compatible-baseboard=ti,beaglebone-black - #slots=4 > Feb 11 16:28:01 arm kernel: bone_capemgr bone_capemgr: slot #0: auto > loading handled by U-Boot > Feb 11 16:28:01 arm kernel: bone_capemgr bone_capemgr: slot #1: auto > loading handled by U-Boot > Feb 11 16:28:01 arm kernel: bone_capemgr bone_capemgr: slot #2: auto > loading handled by U-Boot > Feb 11 16:28:01 arm kernel: bone_capemgr bone_capemgr: slot #3: auto > loading handled by U-Boot > Feb 11 16:28:01 arm kernel: bone_capemgr bone_capemgr: initialized OK. > Feb 11 16:28:01 arm kernel: PM: bootloader does not support rtc-only! > > I updated the image to: > > $ cat /etc/dogtag > rcn-ee.net console Ubuntu Image 2017-07-14 > $ uname -a > Linux arm 4.4.68-ti-r111 #1 SMP Wed Jun 28 13:40:31 UTC 2017 armv7l armv7l > armv7l GNU/Linux > With u-boot overlays, just ignore the slots and kernel messages.. Did you try using, /dev/ttyS1 ? It should be active. 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhKka9qCj28hyZkVNVK46Zzez%2BwtUgAMx7ZcSO2ftGq6w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
