Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Hartley Sweeten 
Yeah That worked!!! After 2-3 months I can finally update this stupid 
thing.

Here's the full boot from J1. I don have a couple questions at the end.

U-Boot SPL 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29)
Trying to boot from MMC2


U-Boot 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29 -0600), Build: 
jenkins-github_Bootloader-Builder-32

CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
Reset Source: Global warm SW reset has occurred.
Reset Source: Power-on reset has occurred.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Board: BeagleBone Black
 not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net:   eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] ...
board_rev=[00C0] ...
Card did not respond to voltage select!
mmc_init: -95, time 12
Card did not respond to voltage select!
mmc_init: -95, time 13
Card did not respond to voltage select!
mmc_init: -95, time 13
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
Card did not respond to voltage select!
mmc_init: -95, time 13
Card did not respond to voltage select!
mmc_init: -95, time 13
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
2295 bytes read in 15 ms (149.4 KiB/s)
Loaded environment from /boot/uEnv.txt
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.9.105-ti-r114 ...
9818560 bytes read in 637 ms (14.7 MiB/s)
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb ...
loading /boot/dtbs/4.9.105-ti-r114/am335x-boneblack-uboot.dtb ...
61638 bytes read in 43 ms (1.4 MiB/s)
uboot_overlays: [fdt_buffer=0x6] ...
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1440 bytes read in 173 ms (7.8 KiB/s)
uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
4896 bytes read in 60 ms (79.1 KiB/s)
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
711 bytes read in 142 ms (4.9 KiB/s)
uboot_overlays: loading /lib/firmware/univ-bbb-EVA-00A0.dtbo ...
62064 bytes read in 240 ms (252 KiB/s)
loading /boot/initrd.img-4.9.105-ti-r114 ...
5799056 bytes read in 382 ms (14.5 MiB/s)
debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
net.ifnames=0] ...
debug: [bootz 0x8200 0x8808:587c90 8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Ramdisk to 8fa78000, end 8c90 ... OK
   reserving fdt memory region: addr=8800 size=7e000
   Loading Device Tree to 8f9f7000, end 8fa77fff ... OK

Starting kernel ...

[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.105-ti-r114 (root@a5-imx6q-wandboard-2gb) 
(gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP PREEMPT Fri 
Aug 17 11:05:53 UTC 2018
[0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), 
cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] OF: fdt:Machine model: TI AM335x BeagleBone Black
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 48 MiB at 0x9c80
[0.00] Memory policy: Data cache writeback
[0.00] CPU: All CPU(s) started in SVC mode.
[0.00] AM335X ES2.1 (sgx neon)
[0.00] percpu: Embedded 15 pages/cpu @df902000 s31820 r8192 d21428 
u61440
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  
Total pages: 129412
[0.00] Kernel command line: console=ttyO0,115200n8 
bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 
rootwait coherent_pool=1M net.ifnames=0
[0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 
bytes)
[0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 
bytes)
[0.00] Memory: 440224K/522240K available (12288K kernel code, 1139K 
rwdata, 4324K rodata, 1024K init, 459K bss, 32864K reserved, 49152K 
cma-reserved, 0K highmem)
[0.00] Virtual kernel

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Hartley Sweeten 
OK, I did the hold on the bb-cape-overlays.

Running the 'sudo apt upgrade' now. I'll let you know how it goes shortly.

It it fails to boot again to you want the full serial port log?

Hartley

On Friday, October 23, 2020 at 5:08:43 PM UTC-7, RobertCNelson wrote:
>
> I bet it's bb-cape-overlays, just lock it: 
>
> sudo apt-mark hold bb-cape-overlays 
>
> Regards, 
>
> On Fri, Oct 23, 2020 at 6:50 PM Hartley Sweeten  > wrote: 
> > 
> > Here's the rest. This is all before the 'apt upgrade'. 
> > 
> > Starting kernel ... 
> > 
> > [0.00] Booting Linux on physical CPU 0x0 
> > [0.00] Linux version 4.9.105-ti-r114 
> (root@a5-imx6q-wandboard-2gb) (gcc version 6.3.0 20170516 (Debian 
> 6.3.0-18+deb9u1) ) #1 SMP PREEMPT Fri Aug 17 11:05:53 UTC 2018 
> > [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), 
> cr=10c5387d 
> > [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> instruction cache 
> > [0.00] OF: fdt:Machine model: TI AM335x BeagleBone Black 
> > [0.00] efi: Getting EFI parameters from FDT: 
> > [0.00] efi: UEFI not found. 
> > [0.00] cma: Reserved 48 MiB at 0x9c80 
> > [0.00] Memory policy: Data cache writeback 
> > [0.00] CPU: All CPU(s) started in SVC mode. 
> > [0.00] AM335X ES2.1 (sgx neon) 
> > [0.00] percpu: Embedded 15 pages/cpu @df902000 s31820 r8192 
> d21428 u61440 
> > [0.00] Built 1 zonelists in Zone order, mobility grouping on. 
>  Total pages: 129412 
> > [0.00] Kernel command line: console=ttyO0,115200n8 
> bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 
> rootwait coherent_pool=1M net.ifnames=0 
> > [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) 
> > [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 
> bytes) 
> > [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 
> bytes) 
> > [0.00] Memory: 440220K/522240K available (12288K kernel code, 
> 1139K rwdata, 4324K rodata, 1024K init, 459K bss, 32868K reserved, 49152K 
> cma-reserved, 0K highmem) 
> > [0.00] Virtual kernel memory layout: 
> > [0.00] vector  : 0x - 0x1000   (   4 kB) 
> > [0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB) 
> > [0.00] vmalloc : 0xe000 - 0xff80   ( 504 MB) 
> > [0.00] lowmem  : 0xc000 - 0xdfe0   ( 510 MB) 
> > [0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB) 
> > [0.00] modules : 0xbf00 - 0xbfe0   (  14 MB) 
> > [0.00]   .text : 0xc0008000 - 0xc0d0   (13280 kB) 
> > [0.00]   .init : 0xc130 - 0xc140   (1024 kB) 
> > [0.00]   .data : 0xc140 - 0xc151cd58   (1140 kB) 
> > [0.00].bss : 0xc151e000 - 0xc1590ff0   ( 460 kB) 
> > [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, 
> Nodes=1 
> > [0.00] Preemptible hierarchical RCU implementation. 
> > [0.00]  Build-time adjustment of leaf fanout to 32. 
> > [0.00]  RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1. 
> > [0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, 
> nr_cpu_ids=1 
> > [0.00] NR_IRQS:16 nr_irqs:16 16 
> > [0.00] IRQ: Found an INTC at 0xfa20 (revision 5.0) with 128 
> interrupts 
> > [0.00] OMAP clockevent source: timer2 at 2400 Hz 
> > [0.23] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps 
> every 89478484971ns 
> > [0.51] clocksource: timer1: mask: 0x max_cycles: 
> 0x, max_idle_ns: 79635851949 ns 
> > [0.66] OMAP clocksource: timer1 at 2400 Hz 
> > [0.002095] clocksource_probe: no matching clocksources found 
> > [0.002417] Console: colour dummy device 80x30 
> > [0.002452] WARNING: Your 'console=ttyO0' has been replaced by 
> 'ttyS0' 
> > [0.002461] This ensures that you still see kernel messages. Please 
> > [0.002469] update your kernel commandline. 
> > [0.002496] Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656) 
> > [0.020746] pid_max: default: 32768 minimum: 301 
> > [0.021016] Security Framework initialized 
> > [0.021034] Yama: becoming mindful. 
> > [0.021093] AppArmor: AppArmor initialized 
> > [0.021181] Mount-cache hash table entries: 1024 (order: 0, 4096 
> bytes) 
> > [0.021194] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 
> bytes) 
> > [0.022359] CPU: Testing write buffer coherency: ok 
> > [0.022433] ftrace: allocating 39262 entries in 116 pages 
> > [0.133533] CPU0: thread -1, cpu 0, socket -1, mpidr 0 
> > [0.133613] Setting up static identity map for 0x8010 - 
> 0x80100060 
> > [0.167804] EFI services will not be available. 
> > [0.180740] Brought up 1 CPUs 
> > [0.180760] SMP: Total of 1 processors activated (995.32 BogoMIPS). 
> > [0.180770] CPU: All CPU(s) started

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Robert Nelson 
I bet it's bb-cape-overlays, just lock it:

sudo apt-mark hold bb-cape-overlays

Regards,

On Fri, Oct 23, 2020 at 6:50 PM Hartley Sweeten  wrote:
>
> Here's the rest. This is all before the 'apt upgrade'.
>
> Starting kernel ...
>
> [0.00] Booting Linux on physical CPU 0x0
> [0.00] Linux version 4.9.105-ti-r114 (root@a5-imx6q-wandboard-2gb) 
> (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP PREEMPT Fri Aug 
> 17 11:05:53 UTC 2018
> [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> instruction cache
> [0.00] OF: fdt:Machine model: TI AM335x BeagleBone Black
> [0.00] efi: Getting EFI parameters from FDT:
> [0.00] efi: UEFI not found.
> [0.00] cma: Reserved 48 MiB at 0x9c80
> [0.00] Memory policy: Data cache writeback
> [0.00] CPU: All CPU(s) started in SVC mode.
> [0.00] AM335X ES2.1 (sgx neon)
> [0.00] percpu: Embedded 15 pages/cpu @df902000 s31820 r8192 d21428 
> u61440
> [0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
> pages: 129412
> [0.00] Kernel command line: console=ttyO0,115200n8 
> bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 
> rootwait coherent_pool=1M net.ifnames=0
> [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
> [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> [0.00] Memory: 440220K/522240K available (12288K kernel code, 1139K 
> rwdata, 4324K rodata, 1024K init, 459K bss, 32868K reserved, 49152K 
> cma-reserved, 0K highmem)
> [0.00] Virtual kernel memory layout:
> [0.00] vector  : 0x - 0x1000   (   4 kB)
> [0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
> [0.00] vmalloc : 0xe000 - 0xff80   ( 504 MB)
> [0.00] lowmem  : 0xc000 - 0xdfe0   ( 510 MB)
> [0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)
> [0.00] modules : 0xbf00 - 0xbfe0   (  14 MB)
> [0.00]   .text : 0xc0008000 - 0xc0d0   (13280 kB)
> [0.00]   .init : 0xc130 - 0xc140   (1024 kB)
> [0.00]   .data : 0xc140 - 0xc151cd58   (1140 kB)
> [0.00].bss : 0xc151e000 - 0xc1590ff0   ( 460 kB)
> [0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
> [0.00] Preemptible hierarchical RCU implementation.
> [0.00]  Build-time adjustment of leaf fanout to 32.
> [0.00]  RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.
> [0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=1
> [0.00] NR_IRQS:16 nr_irqs:16 16
> [0.00] IRQ: Found an INTC at 0xfa20 (revision 5.0) with 128 
> interrupts
> [0.00] OMAP clockevent source: timer2 at 2400 Hz
> [0.23] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 
> 89478484971ns
> [0.51] clocksource: timer1: mask: 0x max_cycles: 0x, 
> max_idle_ns: 79635851949 ns
> [0.66] OMAP clocksource: timer1 at 2400 Hz
> [0.002095] clocksource_probe: no matching clocksources found
> [0.002417] Console: colour dummy device 80x30
> [0.002452] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
> [0.002461] This ensures that you still see kernel messages. Please
> [0.002469] update your kernel commandline.
> [0.002496] Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)
> [0.020746] pid_max: default: 32768 minimum: 301
> [0.021016] Security Framework initialized
> [0.021034] Yama: becoming mindful.
> [0.021093] AppArmor: AppArmor initialized
> [0.021181] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
> [0.021194] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 
> bytes)
> [0.022359] CPU: Testing write buffer coherency: ok
> [0.022433] ftrace: allocating 39262 entries in 116 pages
> [0.133533] CPU0: thread -1, cpu 0, socket -1, mpidr 0
> [0.133613] Setting up static identity map for 0x8010 - 0x80100060
> [0.167804] EFI services will not be available.
> [0.180740] Brought up 1 CPUs
> [0.180760] SMP: Total of 1 processors activated (995.32 BogoMIPS).
> [0.180770] CPU: All CPU(s) started in SVC mode.
> [0.182399] devtmpfs: initialized
> [0.221055] VFP support v0.3: implementor 41 architecture 3 part 30 
> variant c rev 3
> [0.221635] clocksource: jiffies: mask: 0x max_cycles: 0x, 
> max_idle_ns: 764504178510 ns
> [0.221668] futex hash table entries: 256 (order: 2, 16384 bytes)
> [0.225444] xor: measuring software checksum speed
> [0.264759]arm4regs  :  1217.000 MB/sec
> [0.304710]8regs :  1091.000 MB/sec
> [0.344709]

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Hartley Sweeten 
Here's the rest. This is all before the 'apt upgrade'.

Starting kernel ...

[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.105-ti-r114 (root@a5-imx6q-wandboard-2gb) 
(gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP PREEMPT Fri 
Aug 17 11:05:53 UTC 2018
[0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), 
cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] OF: fdt:Machine model: TI AM335x BeagleBone Black
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 48 MiB at 0x9c80
[0.00] Memory policy: Data cache writeback
[0.00] CPU: All CPU(s) started in SVC mode.
[0.00] AM335X ES2.1 (sgx neon)
[0.00] percpu: Embedded 15 pages/cpu @df902000 s31820 r8192 d21428 
u61440
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  
Total pages: 129412
[0.00] Kernel command line: console=ttyO0,115200n8 
bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 
rootwait coherent_pool=1M net.ifnames=0
[0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 
bytes)
[0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 
bytes)
[0.00] Memory: 440220K/522240K available (12288K kernel code, 1139K 
rwdata, 4324K rodata, 1024K init, 459K bss, 32868K reserved, 49152K 
cma-reserved, 0K highmem)
[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x - 0x1000   (   4 kB)
[0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
[0.00] vmalloc : 0xe000 - 0xff80   ( 504 MB)
[0.00] lowmem  : 0xc000 - 0xdfe0   ( 510 MB)
[0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)
[0.00] modules : 0xbf00 - 0xbfe0   (  14 MB)
[0.00]   .text : 0xc0008000 - 0xc0d0   (13280 kB)
[0.00]   .init : 0xc130 - 0xc140   (1024 kB)
[0.00]   .data : 0xc140 - 0xc151cd58   (1140 kB)
[0.00].bss : 0xc151e000 - 0xc1590ff0   ( 460 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] Preemptible hierarchical RCU implementation.
[0.00]  Build-time adjustment of leaf fanout to 32.
[0.00]  RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.
[0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=1
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] IRQ: Found an INTC at 0xfa20 (revision 5.0) with 128 
interrupts
[0.00] OMAP clockevent source: timer2 at 2400 Hz
[0.23] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 
89478484971ns
[0.51] clocksource: timer1: mask: 0x max_cycles: 
0x, max_idle_ns: 79635851949 ns
[0.66] OMAP clocksource: timer1 at 2400 Hz
[0.002095] clocksource_probe: no matching clocksources found
[0.002417] Console: colour dummy device 80x30
[0.002452] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[0.002461] This ensures that you still see kernel messages. Please
[0.002469] update your kernel commandline.
[0.002496] Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)
[0.020746] pid_max: default: 32768 minimum: 301
[0.021016] Security Framework initialized
[0.021034] Yama: becoming mindful.
[0.021093] AppArmor: AppArmor initialized
[0.021181] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.021194] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 
bytes)
[0.022359] CPU: Testing write buffer coherency: ok
[0.022433] ftrace: allocating 39262 entries in 116 pages
[0.133533] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[0.133613] Setting up static identity map for 0x8010 - 0x80100060
[0.167804] EFI services will not be available.
[0.180740] Brought up 1 CPUs
[0.180760] SMP: Total of 1 processors activated (995.32 BogoMIPS).
[0.180770] CPU: All CPU(s) started in SVC mode.
[0.182399] devtmpfs: initialized
[0.221055] VFP support v0.3: implementor 41 architecture 3 part 30 
variant c rev 3
[0.221635] clocksource: jiffies: mask: 0x max_cycles: 
0x, max_idle_ns: 764504178510 ns
[0.221668] futex hash table entries: 256 (order: 2, 16384 bytes)
[0.225444] xor: measuring software checksum speed
[0.264759]arm4regs  :  1217.000 MB/sec
[0.304710]8regs :  1091.000 MB/sec
[0.344709]32regs:  1088.000 MB/sec
[0.384709]neon  :  1665.000 MB/sec
[0.384720] xor: using function: neon (1665.000 MB/sec)
[0.384742] pinctrl core: initialized pinctrl subsystem
[0.386235] NET: Registered protocol family 16
[0.390094] DMA: preallocated 1024 KiB pool for atomic coherent

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Robert Nelson 
On Fri, Oct 23, 2020 at 6:20 PM Hartley Sweeten  wrote:
>
> Here is the uBoot output before I do an 'apt upgrade'
>
> U-Boot SPL 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29)
> Trying to boot from MMC2
>
>
> U-Boot 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29 -0600), Build: 
> jenkins-github_Bootloader-Builder-32
>
> CPU  : AM335X-GP rev 2.1
> I2C:   ready
> DRAM:  512 MiB
> No match for driver 'omap_hsmmc'
> No match for driver 'omap_hsmmc'
> Some drivers were not found
> Reset Source: Global warm SW reset has occurred.
> Reset Source: Power-on reset has occurred.
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Board: BeagleBone Black
>  not set. Validating first E-fuse MAC
> BeagleBone Black:
> BeagleBone: cape eeprom: i2c_probe: 0x54:
> BeagleBone: cape eeprom: i2c_probe: 0x55:
> BeagleBone: cape eeprom: i2c_probe: 0x56:
> BeagleBone: cape eeprom: i2c_probe: 0x57:
> Net:   eth0: MII MODE
> cpsw, usb_ether
> Press SPACE to abort autoboot in 2 seconds
> board_name=[A335BNLT] ...
> board_rev=[00C0] ...
> Card did not respond to voltage select!
> mmc_init: -95, time 12
> Card did not respond to voltage select!
> mmc_init: -95, time 13
> Card did not respond to voltage select!
> mmc_init: -95, time 13
> 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
> Card did not respond to voltage select!
> mmc_init: -95, time 13
> Card did not respond to voltage select!
> mmc_init: -95, time 13
> 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
> 2295 bytes read in 15 ms (149.4 KiB/s)
> Loaded environment from /boot/uEnv.txt
> 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.9.105-ti-r114 ...
> 9818560 bytes read in 638 ms (14.7 MiB/s)
> uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
> uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb ...
> loading /boot/dtbs/4.9.105-ti-r114/am335x-boneblack-uboot.dtb ...
> 61638 bytes read in 42 ms (1.4 MiB/s)
> uboot_overlays: [fdt_buffer=0x6] ...
> uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
> 1440 bytes read in 165 ms (7.8 KiB/s)
> uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
> 4896 bytes read in 58 ms (82 KiB/s)
> uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
> 711 bytes read in 134 ms (4.9 KiB/s)
> uboot_overlays: loading /lib/firmware/univ-bbb-EVA-00A0.dtbo ...
> 62064 bytes read in 235 ms (257.8 KiB/s)
> loading /boot/initrd.img-4.9.105-ti-r114 ...
> 5801348 bytes read in 383 ms (14.4 MiB/s)
> debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
> net.ifnames=0] ...
> debug: [bootz 0x8200 0x8808:588584 8800] ...
> ## Flattened Device Tree blob at 8800
>Booting using the fdt blob at 0x8800
>Loading Ramdisk to 8fa77000, end 8584 ... OK
>reserving fdt memory region: addr=8800 size=7e000
>Loading Device Tree to 8f9f6000, end 8fa76fff ... OK
>
> Starting kernel ...

Okay that's better, nothing wrong going on their..

can you share the rest of the boot?

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYggU8UB9qAfwae%2BjZeA99%3DNOt%3DAKkk7GTpV7aJTh_-L_g%40mail.gmail.com.

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Hartley Sweeten 
Here is the uBoot output before I do an 'apt upgrade'

U-Boot SPL 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29)
Trying to boot from MMC2


U-Boot 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29 -0600), Build: 
jenkins-github_Bootloader-Builder-32

CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
Reset Source: Global warm SW reset has occurred.
Reset Source: Power-on reset has occurred.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Board: BeagleBone Black
 not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net:   eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] ...
board_rev=[00C0] ...
Card did not respond to voltage select!
mmc_init: -95, time 12
Card did not respond to voltage select!
mmc_init: -95, time 13
Card did not respond to voltage select!
mmc_init: -95, time 13
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
Card did not respond to voltage select!
mmc_init: -95, time 13
Card did not respond to voltage select!
mmc_init: -95, time 13
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
2295 bytes read in 15 ms (149.4 KiB/s)
Loaded environment from /boot/uEnv.txt
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.9.105-ti-r114 ...
9818560 bytes read in 638 ms (14.7 MiB/s)
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb ...
loading /boot/dtbs/4.9.105-ti-r114/am335x-boneblack-uboot.dtb ...
61638 bytes read in 42 ms (1.4 MiB/s)
uboot_overlays: [fdt_buffer=0x6] ...
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1440 bytes read in 165 ms (7.8 KiB/s)
uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
4896 bytes read in 58 ms (82 KiB/s)
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
711 bytes read in 134 ms (4.9 KiB/s)
uboot_overlays: loading /lib/firmware/univ-bbb-EVA-00A0.dtbo ...
62064 bytes read in 235 ms (257.8 KiB/s)
loading /boot/initrd.img-4.9.105-ti-r114 ...
5801348 bytes read in 383 ms (14.4 MiB/s)
debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
net.ifnames=0] ...
debug: [bootz 0x8200 0x8808:588584 8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Ramdisk to 8fa77000, end 8584 ... OK
   reserving fdt memory region: addr=8800 size=7e000
   Loading Device Tree to 8f9f6000, end 8fa76fff ... OK

Starting kernel ...

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ceb4c778-4855-47f0-a5ac-1e8c63d16881o%40googlegroups.com.

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Hartley Sweeten 
The serial cable is plugged in. What do you want me to do?

On Friday, October 23, 2020 at 4:15:43 PM UTC-7, RobertCNelson wrote:
>
> On Fri, Oct 23, 2020 at 5:58 PM Hartley Sweeten  > wrote: 
> > 
> > I tried adding the UUID (found with blkid) to my uEnv.txt. Same result. 
> > 
> > 1) Install SDcard image 
> > 2) Boot 
> > 3) sudo apt update 
> > 4) sudo apt upgrade 
> > 5) Reboot, system hangs 
> > 
> > It does change the message: 
> > 
> > Begin: Running /scripts/local-block ... done. 
> > done. 
> > Gave up waiting for root file system device.  Common problems: 
> >  - Boot args (cat /proc/cmdline) 
> >- Check rootdelay= (did the system wait long enough?) 
> >  - Missing modules (cat /proc/modules; ls /dev) 
> > ALERT!  UUID=0159e561-b327-492f-a73a-b188b2217267 does not exist. 
>  Dropping to a shell! 
> > (initramfs) 
>
> It was around the v4.4.x era we stopped using uuid, as we had a kernel 
> fix.. 
>
> Do you have a serial cable you can plug into J1 so we can see what 
> u-boot is doing? 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2e564c78-7717-443c-9067-88c7c48cdfe7o%40googlegroups.com.

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Robert Nelson 
On Fri, Oct 23, 2020 at 5:58 PM Hartley Sweeten  wrote:
>
> I tried adding the UUID (found with blkid) to my uEnv.txt. Same result.
>
> 1) Install SDcard image
> 2) Boot
> 3) sudo apt update
> 4) sudo apt upgrade
> 5) Reboot, system hangs
>
> It does change the message:
>
> Begin: Running /scripts/local-block ... done.
> done.
> Gave up waiting for root file system device.  Common problems:
>  - Boot args (cat /proc/cmdline)
>- Check rootdelay= (did the system wait long enough?)
>  - Missing modules (cat /proc/modules; ls /dev)
> ALERT!  UUID=0159e561-b327-492f-a73a-b188b2217267 does not exist.  Dropping 
> to a shell!
> (initramfs)

It was around the v4.4.x era we stopped using uuid, as we had a kernel fix..

Do you have a serial cable you can plug into J1 so we can see what
u-boot is doing?

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgn5q8C3Mt8Ty2wwjiYJPUHDRP7fR%3DWeppbH3EhETeG7A%40mail.gmail.com.

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Hartley Sweeten 
OK, another annoyance...

I jut reinstalled my SDcard image and the UUID changed.

The last install (that broke after the apt upgrade) was 
0159e561-b327-492f-a73a-b188b2217267.
After this install its now 60fc6cad-2e3f-408d-a2f8-5f2320240203.

Is it possible that something during the apt upgrade is changing the 
mmcblk1p1 UUID?

Aside... I can kind of understand why the system will not boot if the UUID 
changes but prior to adding the UUID= to uEnv.txt my system was booting 
from /dev/mmcblk1p1. That _should_ have still worked but it didn't.

Getting rather annoyed by this

Hartley

On Friday, October 23, 2020 at 3:58:15 PM UTC-7, Hartley Sweeten wrote:
>
> I tried adding the UUID (found with blkid) to my uEnv.txt. Same result.
>
> 1) Install SDcard image
> 2) Boot
> 3) sudo apt update
> 4) sudo apt upgrade
> 5) Reboot, system hangs
>
> It does change the message:
>
> Begin: Running /scripts/local-block ... done.
> done.
> Gave up waiting for root file system device.  Common problems:
>  - Boot args (cat /proc/cmdline)
>- Check rootdelay= (did the system wait long enough?)
>  - Missing modules (cat /proc/modules; ls /dev)
> ALERT!  UUID=0159e561-b327-492f-a73a-b188b2217267 does not exist.  
> Dropping to a shell!
> (initramfs)
>
> Hartley
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/758c747a-0e74-45b7-bd5a-91a81c464a75o%40googlegroups.com.

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Hartley Sweeten 
I tried adding the UUID (found with blkid) to my uEnv.txt. Same result.

1) Install SDcard image
2) Boot
3) sudo apt update
4) sudo apt upgrade
5) Reboot, system hangs

It does change the message:

Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=0159e561-b327-492f-a73a-b188b2217267 does not exist.  Dropping 
to a shell!
(initramfs)

Hartley

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e32f1319-e123-45bd-a99e-4556699e6f1fo%40googlegroups.com.

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-23 Thread 'Jeremias Ramirez' via BeagleBoard 

That looks good.
In the meantime I try to fully understand what are you doing and how to 
replicate it, you say you will add the other items in the config later. How 
do you will do that? I have an VirtualBox snapshot on my laptop (another Qt 
installation) just after the -make step, so, to try re-run the ./configure 
plus -make combo when we can include OpenGL I just ran -make clean, but 
this don't solve that re-run ./configure doesn't seem to take all the new 
paths.
In the past, I opt to reinstall Ubuntu just for make sure the new 
installation will be clean, but i hate do that, i think that in certain 
moment i will not be able to do that anymore without expend another week 
configuring the IDE.

Thank you very much for your help.
Jeremias.
El viernes, 23 de octubre de 2020 a las 17:01:15 UTC-3, jonn...@gmail.com 
escribió:

> Okay, a bit of success.
> With it picking up the older toolchain, look in the folders you are using 
> for any '.qt*. files. There are files that get created as '.' when running 
> the configure script.
>
> For me,
>
> I downloaded Qt 5.12.5 and unpacked it in a folder.
> Then I created 3 folders for the prefix, extprefix and hostprefix:
>
> *prefix  ~/opt/qt512bb/install *
> *extprefix ~/opt/qt512bb/binaries  *
> *hostprefix  ~/opt/qt512bb/tool*
>
>
> Then I created a build folder to build qt in and moved to that folder to 
> build
>
> *mkdir -p ~/opt/qt512bb/build*
> *cd ~/opt/qt512bb/build*
>
>
> Then I ran the configure script from the build folder as such.
>
> *../qt-everywhere-src-5.12.5/configure -platform linux-g++-64 -release 
> -opengl es2 -device linux-beagleboard-g++ -device-option 
> CROSS_COMPILE=~/develop/bbuild/gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
>  
> -sysroot ~/develop/bbuild/sysroot -opensource -confirm-license -make libs 
> -prefix ~/opt/qt512bb/install -extprefix ~/opt/qt512bb/binaries -hostprefix 
> ~/opt/qt512bb/tool -nomake tests -v -libdir 
> ~/develop/bbuild/sysroot/lib/arm-linux-gnueabihf*
>
>
> This was just to verify the config and make sure it passes the configure 
> stage. Currently running make and will see if it compiles then will add the 
> other items in the config. 
> Also, I am using the default qmake.conf file.
>
> Helpful links:
>
> https://stackoverflow.com/questions/45983717/qt-sysroot-prefix-extprefix-and-hostprefix-options
>
> https://stackoverflow.com/questions/49139731/error-while-creating-qmake-for-a-qt-static-build
>
>
> Jon
>
>
> On Fri, Oct 23, 2020 at 5:44 AM 'Jeremias Ramirez' via BeagleBoard <
> beagl...@googlegroups.com> wrote:
>
>> Well, i'm not sure if this is something useful, but, I try to use an 
>> older version of the Linaro compiler.
>> I was using 7.5 and i try 6.5
>> I think there's something weird updating links, because i change the 
>> ./configure, and the script still trying to use the 7.5v, look:
>>
>> + cd qtbase
>> + /opt/qt5bbb/qt5/qtbase/configure -top-level -no-gcc-sysroot -device 
>> linux-beagleboard-g++ -device-option CROSS_COMPILE=
>> */opt/gcc-linaro-6.5.0-2018.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf*-
>>  
>> -sysroot /mnt/bbb-rootfs -opensource -confirm-license -optimized-qmake 
>> -reduce-exports -release -make libs -prefix /usr/local/qt5bbb -hostprefix 
>> /usr/local/qt5bbb -qt-zlib -qt-libpng -no-openssl -opengl es2 -eglfs -v
>>  = /opt/qt5bbb/qt5/qtbase 
>>  = /opt/qt5bbb/qt5/qtbase 
>>  = /opt/qt5bbb/qt5/qtbase 
>> Creating qmake...
>> make: Nothing to be done for 'first'.
>> Command line: -no-gcc-sysroot -device linux-beagleboard-g++ 
>> -device-option CROSS_COMPILE=/
>> *opt/gcc-linaro-6.5.0-2018.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf*-
>>  
>> -sysroot /mnt/bbb-rootfs -opensource -confirm-license -optimized-qmake 
>> -reduce-exports -release -make libs -prefix /usr/local/qt5bbb -hostprefix 
>> /usr/local/qt5bbb -qt-zlib -qt-libpng -no-openssl -opengl es2 -eglfs -v
>>
>> This is the Qt Open Source Edition.
>>
>> You have already accepted the terms of the Open Source license.
>>
>> Running configuration tests...
>>
>> + cd */opt/qt5bbb/qt5/config.tests && 
>> /opt/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf*-g++
>>  
>> -pipe -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mthumb -march=armv7-a 
>> -mtune=cortex-a8 -mfpu=neon -mthumb -mfloat-abi=hard -fuse-ld=gold -o 
>> conftest-out conftest.cpp
>>
>> + 
>> */opt/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf-g+*+
>>  
>> -dumpmachine
>> > armv8l-linux-gnueabihf
>>
>>
>> I rename the 7.5v folder and still giving me the same paths here.
>>
>> Best regards.
>>
>> El jueves, 22 de octubre de 2020 a las 22:39:35 UTC-3, jonn...@gmail.com 
>> escribió:
>>
>>> Yeah, I tried with Debian 9.13 64-bit and it still shows the same error 
>>> for the OpenGL ES libs. 
>>>
>>> Must be missing something.
>>>
>>> Jon
>>>
>>> On Thu, Oct 22, 2020 at 2:03 PM 'Jeremias Ramirez' via BeagleBoard <
>>>

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Hartley Sweeten 
Robert,

I really can't remember what the original image file was that I started 
with. I only have the /etc/dogtag info.

The image "file" I am using is one I created using the 
/opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh 
script. This was done after installing the original image and then 
installing just what I needed for some Qt development.

I did remember to remove the "quiet" from the command line after installing 
the image again. I then tried doing an 'apt install ..' for individual 
packages that needed updated. It appears one of the openssh packages is 
what is breaking the boot.

I got this after updating openssh-client, openssh-server, 
openssh-sftp-server, and openssl:

[3.270685] Freeing unused kernel memory: 1024K
Loading, please wait...
[3.311056] usb 1-1.1: new full-speed USB device number 3 using musb-hdrc
starting version 232
[3.367799] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
[3.384045] random: systemd-udevd: uninitialized urandom read (16 bytes 
read)
[3.393865] random: udevadm: uninitialized urandom read (16 bytes read)
[3.425391] usb 1-1.1: New USB device found, idVendor=046d, 
idProduct=c534
[3.439037] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[3.455036] usb 1-1.1: Product: USB Receiver
[3.463011] usb 1-1.1: Manufacturer: Logitech
[3.492331] input: Logitech USB Receiver as 
/devices/platform/ocp/4740.usb/47401c00.usb/musb-hdrc.1/usb1/1-1/1-1.1/1-1.1:1.0/0003:046D:C534.0001/input/input1
[3.587187] hid-generic 0003:046D:C534.0001: input,hidraw0: USB HID 
v1.11 Keyboard [Logitech USB Receiver] on usb-musb-hdrc.1-1.1/input0
[3.629415] input: Logitech USB Receiver as 
/devices/platform/ocp/4740.usb/47401c00.usb/musb-hdrc.1/usb1/1-1/1-1.1/1-1.1:1.1/0003:046D:C534.0002/input/input2
[3.722058] hid-generic 0003:046D:C534.0002: input,hiddev0,hidraw1: USB 
HID v1.11 Mouse [Logitech USB Receiver] on usb-musb-hdrc.1-1.1/input1
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block 
... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mmcblk1p1 does not exist.  Dropping to a shell!
(initramfs)

A quick google search says that there may be a problem with the UUID. Isn't 
the SDcard flasher supposed to set that?

Hartley
On Friday, October 23, 2020 at 2:53:22 PM UTC-7, RobertCNelson wrote:
>
> On Fri, Oct 23, 2020 at 4:12 PM Hartley Sweeten  > wrote: 
> > 
> > Ok, this happened again. I forgot that an 'apt upgrade' breaks my setup. 
> > 
> > I reinstalled my default image on the BBB. For reference: 
> > 
> > ~$ cat /etc/dogtag 
> > BeagleBoard.org Debian Image 2018-01-21 
>
> Can you share the "file" name of this image? Such that i can test. 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Robert Nelson 
On Fri, Oct 23, 2020 at 4:12 PM Hartley Sweeten  wrote:
>
> Ok, this happened again. I forgot that an 'apt upgrade' breaks my setup.
>
> I reinstalled my default image on the BBB. For reference:
>
> ~$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2018-01-21

Can you share the "file" name of this image? Such that i can test.

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiJRw4GbyGNng%3DsgtjLuQd5SC3kBN9S77raBc%3DyWazkmA%40mail.gmail.com.

Re: [beagleboard] Unable to boot after 'apt upgrade' to Debian 9.13

2020-10-23 Thread Hartley Sweeten 
Ok, this happened again. I forgot that an 'apt upgrade' breaks my setup.

I reinstalled my default image on the BBB. For reference:

~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2018-01-21
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 9.9 (stretch)
Release:9.9
Codename:   stretch

Not sure what other information may be helpful.

This install has worked for me with no issues for quite a while. But, it's 
pretty behind and should be upgraded:

~$ sudo apt upgrade
...
127 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 86.5 MB of archives.
After this operation, 1,395 kB disk space will be freed.

But it appears every time I try an 'apt upgrade' it _seems_ to go ok but 
when I reboot I get the error about:

[0.001030] clocksource_probe: no matching clocksources found
[1.313075] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[1.487481] omap_hsmmc 481d8000.mmc: prop pinctrl-0 index 0 invalid 
phandle
[1.522508] omap_voltage_late_init: Voltage driver support not added
[1.529663] PM: Cannot get wkup_m3_ipc handle
[1.807970] bone_capemgr bone_capemgr: slot #0: No cape found
[1.839041] bone_capemgr bone_capemgr: slot #1: No cape found
[1.871724] bone_capemgr bone_capemgr: slot #2: No cape found
[1.904358] bone_capemgr bone_capemgr: slot #3: No cape found
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mmcblk1p1 does not exist.  Dropping to a shell!
(initramfs)

Does anyone have an suggestions or ideas about why this is not working?

Thanks,
Hartley

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e8ccb6cc-8604-4feb-9cb0-93cc01642ff9o%40googlegroups.com.

Re: [beagleboard] Re: Selecting which glibc to use

2020-10-23 Thread jonnymo 
You could download the 2.28 version of glibc and build using that.
See this link for an example:
https://wiki.beyondlogic.org/index.php?title=Cross_Compiling_BusyBox_for_ARM


Cheers,

Jon

On Fri, Oct 23, 2020 at 1:02 PM din...@gmail.com  wrote:

> Glibc should already be part of your beaglebone debian distro. Glibc
> version is something your distro and your cross toolchain must agree on.
>
> Easiest solution is to build busybox statically.
>
> If you insist on a dynamically linked executable, you can try building
> with another cross toolchain.
>
> Regards,
> Dimitar
>
> В 21:15:15 UTC+3на петък, 23 октомври 2020 г. Mark A. Yoder написа:
>
>> I've cross compiled busybox and when I run it on the bone I get:
>> ./busybox.dynamic: /lib/arm-linux-gnueabihf/libm.so.6: version
>> `GLIBC_2.29' not found (required by ./busybox.dynamic)
>>
>> So, two questions:
>> When cross compiling, how do I get it to compile against glic 2.28?
>>
>> How do I install glic 2.29 on my Bone?
>>
>> --Mark
>>
> --
> 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 beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/52652f9f-ace9-41af-9a33-49bdff86f281n%40googlegroups.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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAG99bkqhLECJ0GxqFu5UeNQvwfkoT1AbZ%3DDca4ogTYAb8kRYPg%40mail.gmail.com.

[beagleboard] Re: Selecting which glibc to use

2020-10-23 Thread din...@gmail.com 
Glibc should already be part of your beaglebone debian distro. Glibc 
version is something your distro and your cross toolchain must agree on.

Easiest solution is to build busybox statically.

If you insist on a dynamically linked executable, you can try building with 
another cross toolchain.

Regards,
Dimitar

В 21:15:15 UTC+3на петък, 23 октомври 2020 г. Mark A. Yoder написа:

> I've cross compiled busybox and when I run it on the bone I get:
> ./busybox.dynamic: /lib/arm-linux-gnueabihf/libm.so.6: version 
> `GLIBC_2.29' not found (required by ./busybox.dynamic)
>
> So, two questions:
> When cross compiling, how do I get it to compile against glic 2.28?
>
> How do I install glic 2.29 on my Bone?
>
> --Mark
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/52652f9f-ace9-41af-9a33-49bdff86f281n%40googlegroups.com.

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-23 Thread jonnymo 
Okay, a bit of success.
With it picking up the older toolchain, look in the folders you are using
for any '.qt*. files. There are files that get created as '.' when running
the configure script.

For me,

I downloaded Qt 5.12.5 and unpacked it in a folder.
Then I created 3 folders for the prefix, extprefix and hostprefix:

*prefix  ~/opt/qt512bb/install *
*extprefix ~/opt/qt512bb/binaries  *
*hostprefix  ~/opt/qt512bb/tool*


Then I created a build folder to build qt in and moved to that folder to
build

*mkdir -p ~/opt/qt512bb/build*
*cd ~/opt/qt512bb/build*


Then I ran the configure script from the build folder as such.

*../qt-everywhere-src-5.12.5/configure -platform linux-g++-64 -release
-opengl es2 -device linux-beagleboard-g++ -device-option
CROSS_COMPILE=~/develop/bbuild/gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
-sysroot ~/develop/bbuild/sysroot -opensource -confirm-license -make libs
-prefix ~/opt/qt512bb/install -extprefix ~/opt/qt512bb/binaries -hostprefix
~/opt/qt512bb/tool -nomake tests -v -libdir
~/develop/bbuild/sysroot/lib/arm-linux-gnueabihf*


This was just to verify the config and make sure it passes the configure
stage. Currently running make and will see if it compiles then will add the
other items in the config.
Also, I am using the default qmake.conf file.

Helpful links:
https://stackoverflow.com/questions/45983717/qt-sysroot-prefix-extprefix-and-hostprefix-options
https://stackoverflow.com/questions/49139731/error-while-creating-qmake-for-a-qt-static-build


Jon


On Fri, Oct 23, 2020 at 5:44 AM 'Jeremias Ramirez' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Well, i'm not sure if this is something useful, but, I try to use an older
> version of the Linaro compiler.
> I was using 7.5 and i try 6.5
> I think there's something weird updating links, because i change the
> ./configure, and the script still trying to use the 7.5v, look:
>
> + cd qtbase
> + /opt/qt5bbb/qt5/qtbase/configure -top-level -no-gcc-sysroot -device
> linux-beagleboard-g++ -device-option CROSS_COMPILE=
> */opt/gcc-linaro-6.5.0-2018.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf*-
> -sysroot /mnt/bbb-rootfs -opensource -confirm-license -optimized-qmake
> -reduce-exports -release -make libs -prefix /usr/local/qt5bbb -hostprefix
> /usr/local/qt5bbb -qt-zlib -qt-libpng -no-openssl -opengl es2 -eglfs -v
>  = /opt/qt5bbb/qt5/qtbase
>  = /opt/qt5bbb/qt5/qtbase
>  = /opt/qt5bbb/qt5/qtbase
> Creating qmake...
> make: Nothing to be done for 'first'.
> Command line: -no-gcc-sysroot -device linux-beagleboard-g++ -device-option
> CROSS_COMPILE=/
> *opt/gcc-linaro-6.5.0-2018.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf*-
> -sysroot /mnt/bbb-rootfs -opensource -confirm-license -optimized-qmake
> -reduce-exports -release -make libs -prefix /usr/local/qt5bbb -hostprefix
> /usr/local/qt5bbb -qt-zlib -qt-libpng -no-openssl -opengl es2 -eglfs -v
>
> This is the Qt Open Source Edition.
>
> You have already accepted the terms of the Open Source license.
>
> Running configuration tests...
>
> + cd */opt/qt5bbb/qt5/config.tests &&
> /opt/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf*-g++
> -pipe -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mthumb -march=armv7-a
> -mtune=cortex-a8 -mfpu=neon -mthumb -mfloat-abi=hard -fuse-ld=gold -o
> conftest-out conftest.cpp
>
> +
> */opt/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf-g+*+
> -dumpmachine
> > armv8l-linux-gnueabihf
>
>
> I rename the 7.5v folder and still giving me the same paths here.
>
> Best regards.
>
> El jueves, 22 de octubre de 2020 a las 22:39:35 UTC-3, jonn...@gmail.com
> escribió:
>
>> Yeah, I tried with Debian 9.13 64-bit and it still shows the same error
>> for the OpenGL ES libs.
>>
>> Must be missing something.
>>
>> Jon
>>
>> On Thu, Oct 22, 2020 at 2:03 PM 'Jeremias Ramirez' via BeagleBoard <
>> beagl...@googlegroups.com> wrote:
>>
>>> I don't know how path vars work in this kind of files, but, if you see
>>> that file, at the start includes an linux.conf file, that file also make
>>> reference to the $varPaths whom we are trying to especify.
>>>
>>> El jue., 22 de oct. de 2020 17:09, jonnymo  escribió:
>>>
 Yeah, I just downloaded 5.12.9 and tied that but got the same end
 result but more info in the log.
 Also, I am following these two links and ensured both my Host and BB
 have the proper libs installed and such.

 https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/#comment-1706
 https://wiki.qt.io/BeagleBone_Black_Beginners_Guide

 Also, I have edits the qmake.conf and added the following but still no
 go:















 *QMAKE_LFLAGS   += -Wl,-rpath-link,$$[QT_SYSROOT]/lib# Extra
 stuff (OpenGL, DirectFB, ...)QMAKE_INCDIR_EGL=
 $$[QT_SYSROOT]/usr/include \

Re: [beagleboard] Selecting which glibc to use

2020-10-23 Thread jonnymo 
What process did you use to cross compile?

What I do when cross compiling is to rsync the /sbin,  /lib, /usr/lib and
/usr/include from the BB to the build host in a sysroot folder. Then direct
the build to this location for the libs and includes.
Ex:
rsync -avz debian@192.168.7.2:/lib sysroot


Cheers,

Jon

On Fri, Oct 23, 2020 at 11:15 AM Mark A. Yoder 
wrote:

> I've cross compiled busybox and when I run it on the bone I get:
> ./busybox.dynamic: /lib/arm-linux-gnueabihf/libm.so.6: version
> `GLIBC_2.29' not found (required by ./busybox.dynamic)
>
> So, two questions:
> When cross compiling, how do I get it to compile against glic 2.28?
>
> How do I install glic 2.29 on my Bone?
>
> --Mark
>
> --
> 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 beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/7d30c709-1b4b-48ec-a8dc-79b1809cce2dn%40googlegroups.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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAG99bkrBea0PfQUnFUXP_PMDS6H53sYLHJQ23h0ayaXpXYD6sw%40mail.gmail.com.

[beagleboard] Selecting which glibc to use

2020-10-23 Thread Mark A. Yoder 
I've cross compiled busybox and when I run it on the bone I get:
./busybox.dynamic: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.29' 
not found (required by ./busybox.dynamic)

So, two questions:
When cross compiling, how do I get it to compile against glic 2.28?

How do I install glic 2.29 on my Bone?

--Mark

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7d30c709-1b4b-48ec-a8dc-79b1809cce2dn%40googlegroups.com.

[beagleboard] RNG compliant with NIST Special Publication 800-22 Test Suite

2020-10-23 Thread cephassch 
Hi,
Would like to check if anyone has checked or confirmed on the RNG 
on-board AM3358 (Beagle Bone Black) to be compliant to NIST Special 
Publication 800-22 Test Suite ? Or at least compliant to NIST SP800-90A 
rev. 1

Thank you. 

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/88641046-a9e3-439b-8f39-05fa688ca19eo%40googlegroups.com.

Re: [beagleboard] Re: Cannot properly ./configure to install Qt with eglfs and opegles2 support.

2020-10-23 Thread 'Jeremias Ramirez' via BeagleBoard 
Well, i'm not sure if this is something useful, but, I try to use an older 
version of the Linaro compiler.
I was using 7.5 and i try 6.5
I think there's something weird updating links, because i change the 
./configure, and the script still trying to use the 7.5v, look:

+ cd qtbase
+ /opt/qt5bbb/qt5/qtbase/configure -top-level -no-gcc-sysroot -device 
linux-beagleboard-g++ -device-option CROSS_COMPILE=
*/opt/gcc-linaro-6.5.0-2018.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf*-
 
-sysroot /mnt/bbb-rootfs -opensource -confirm-license -optimized-qmake 
-reduce-exports -release -make libs -prefix /usr/local/qt5bbb -hostprefix 
/usr/local/qt5bbb -qt-zlib -qt-libpng -no-openssl -opengl es2 -eglfs -v
 = /opt/qt5bbb/qt5/qtbase 
 = /opt/qt5bbb/qt5/qtbase 
 = /opt/qt5bbb/qt5/qtbase 
Creating qmake...
make: Nothing to be done for 'first'.
Command line: -no-gcc-sysroot -device linux-beagleboard-g++ -device-option 
CROSS_COMPILE=/
*opt/gcc-linaro-6.5.0-2018.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf*-
 
-sysroot /mnt/bbb-rootfs -opensource -confirm-license -optimized-qmake 
-reduce-exports -release -make libs -prefix /usr/local/qt5bbb -hostprefix 
/usr/local/qt5bbb -qt-zlib -qt-libpng -no-openssl -opengl es2 -eglfs -v

This is the Qt Open Source Edition.

You have already accepted the terms of the Open Source license.

Running configuration tests...

+ cd */opt/qt5bbb/qt5/config.tests && 
/opt/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf*-g++
 
-pipe -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mthumb -march=armv7-a 
-mtune=cortex-a8 -mfpu=neon -mthumb -mfloat-abi=hard -fuse-ld=gold -o 
conftest-out conftest.cpp

+ 
*/opt/gcc-linaro-7.5.0-2019.12-x86_64_armv8l-linux-gnueabihf/bin/armv8l-linux-gnueabihf-g+*+
 
-dumpmachine
> armv8l-linux-gnueabihf


I rename the 7.5v folder and still giving me the same paths here.

Best regards.

El jueves, 22 de octubre de 2020 a las 22:39:35 UTC-3, jonn...@gmail.com 
escribió:

> Yeah, I tried with Debian 9.13 64-bit and it still shows the same error 
> for the OpenGL ES libs. 
>
> Must be missing something.
>
> Jon
>
> On Thu, Oct 22, 2020 at 2:03 PM 'Jeremias Ramirez' via BeagleBoard <
> beagl...@googlegroups.com> wrote:
>
>> I don't know how path vars work in this kind of files, but, if you see 
>> that file, at the start includes an linux.conf file, that file also make 
>> reference to the $varPaths whom we are trying to especify.
>>
>> El jue., 22 de oct. de 2020 17:09, jonnymo  escribió:
>>
>>> Yeah, I just downloaded 5.12.9 and tied that but got the same end result 
>>> but more info in the log.  
>>> Also, I am following these two links and ensured both my Host and BB 
>>> have the proper libs installed and such.
>>>
>>> https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/#comment-1706
>>> https://wiki.qt.io/BeagleBone_Black_Beginners_Guide
>>>
>>> Also, I have edits the qmake.conf and added the following but still no 
>>> go:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *QMAKE_LFLAGS   += -Wl,-rpath-link,$$[QT_SYSROOT]/lib# Extra 
>>> stuff (OpenGL, DirectFB, ...)QMAKE_INCDIR_EGL= 
>>> $$[QT_SYSROOT]/usr/include \  
>>> $$[QT_SYSROOT]/usr/include/GLES2 \  
>>> $$[QT_SYSROOT]/usr/include/arm-linux-gnueabihf \  
>>> $$[QT_SYSROOT]/usr/include/arm-linux-gnueabihf/bitsQMAKE_LIBDIR_EGL   
>>>  = $$[QT_SYSROOT]/lib \  $$[QT_SYSROOT]/usr/lib \  
>>> 
>>> $$[QT_SYSROOT]/usr/lib/arm-linux-gnueabihfQMAKE_INCDIR_OPENGL_ES2 = 
>>> $${QMAKE_INCDIR_EGL}QMAKE_LIBDIR_OPENGL_ES2 = 
>>> $${QMAKE_LIBDIR_EGL}QMAKE_INCDIR_OPENVG = 
>>> $${QMAKE_INCDIR_EGL}QMAKE_LIBDIR_OPENVG = $${QMAKE_LIBDIR_EGL}*
>>>
>>>
>>> QMAKE_LIBS_EGL  = -lEGL -lIMGegl -lsrv_um
>>> QMAKE_LIBS_OPENGL_ES2   = -lGLESv2 $${QMAKE_LIBS_EGL}
>>> QMAKE_LIBS_OPENVG   = -lOpenVG $${QMAKE_LIBS_EGL}
>>>
>>> DISTRO_OPTS += hard-float
>>>
>>> # No need for any special EGL device integration.
>>> # Prioritize the default, compiled-in integration over any plugins.
>>>
>>> 
>>>
>>> With 5.12.9 and all the libs and stuff in place, I now see this in the 
>>> log file.
>>>
>>> + 
>>> PKG_CONFIG_SYSROOT_DIR=/home/jomodev/development/beaglbone/bbbuild/sysroot 
>>> PKG_CONFIG_LIBDIR=/home/jomodev/development/beaglbone/bbbuild/sysroot/usr/lib/pkgconfig:/home/jomodev/development/beaglbone/bbbuild/sysroot/usr/share/pkgconfig:/home/jomodev/development/beaglbone/bbbuild/sysroot/usr/lib/arm-linux-gnueabihf/pkgconfig
>>>  
>>> /usr/bin/pkg-config --cflags glesv2
>>> header entry 'config.qtbase_gui.libraries.opengl_es2.headers.0' passed 
>>> condition.
>>> GLES2/gl2.h not found in [] and global paths.
>>>   => source produced no result.
>>> Trying source 1 (type

[beagleboard] Re: Date/time update of second BBB

2020-10-23 Thread Tarmo 
On Friday, October 23, 2020 at 8:29:20 AM UTC+3 biggu...@gmail.com wrote:

> I have two BeagleBone Black boards connected together with an Ethernet 
> cable. One BBB has a battery backed RTC the other does not. Is there a 
> simple way for the second BBB to update its date/time from the first BBB?


If they were both connected to Internet, you wouldn't have to do anything 
as the second BBB would update its time via NTP as soon as it's online.

If they're not connected to Internet, it should be a matter of running an 
NTP server on the BBB with battery packed RTC. The other one can run an NTP 
client. First tutorial I came upon:
https://vitux.com/how-to-setup-ntp-server-and-client-on-debian-10/

I don't know how the NTP server will behave if there's no Internet in the 
first BBB. Configuration may require some tweaks to account for this.

--
Kind regards,
Tarmo

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/fd7a2741-aca4-408e-80aa-b3f8a43a3386n%40googlegroups.com.