yeah, forgot the boot log
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] ...
board_rev=[00C0] ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** Bad device 0:2 0x82000000 **
** Bad device 0:2 0x82000000 **
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0: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
mmc0 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 ...
** 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
1853 bytes read in 18 ms (99.6 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.4.62-ti-r99 ...
8599176 bytes read in 563 ms (14.6 MiB/s)
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb ...
loading /boot/dtbs/4.4.62-ti-r99/am335x-boneblack-uboot.dtb ...
53128 bytes read in 28 ms (1.8 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
uboot_overlays: loading /lib/firmware/AM335X-20-00A0.dtbo ...
378 bytes read in 40 ms (8.8 KiB/s)
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1105 bytes read in 171 ms (5.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
4169 bytes read in 165 ms (24.4 KiB/s)
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
695 bytes read in 37 ms (17.6 KiB/s)
uboot_overlays: loading /lib/firmware/univ-bbb-EVA-00A0.dtbo ...
54726 bytes read in 73 ms (731.4 KiB/s)
loading /boot/initrd.img-4.4.62-ti-r99 ...
6328001 bytes read in 419 ms (14.4 MiB/s)
debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=UUID=7b2b27e9-0af3-479f-b022-cd2642d6d1cd ro rootfstype=ext4 rootwait]
...
debug: [bootz 0x82000000 0x88080000:608ec1 88000000] ...
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f9f7000, end 8ffffec1 ... OK
reserving fdt memory region: addr=88000000 size=75000
Loading Device Tree to 8f97f000, end 8f9f6fff ... OK
................
[ 4.002095] bone_capemgr bone_capemgr: Baseboard:
'A335BNLT,00C0,2916BBBK1D39'
[ 4.009614] bone_capemgr bone_capemgr:
compatible-baseboard=ti,beaglebone-black - #slots=4
[ 4.018121] bone_capemgr bone_capemgr: slot #0: auto loading handled by
U-Boot
[ 4.025470] bone_capemgr bone_capemgr: slot #1: auto loading handled by
U-Boot
[ 4.032803] bone_capemgr bone_capemgr: slot #2: auto loading handled by
U-Boot
[ 4.040094] bone_capemgr bone_capemgr: slot #3: auto loading handled by
U-Boot
[ 4.047884] bone_capemgr bone_capemgr: initialized OK.
..........................
▒ٹtxt...
On Wednesday, May 3, 2017 at 5:27:49 PM UTC-7, michael c wrote:
>
> Linux arm 4.4.62-ti-r99 #1 SMP Sat Apr 22 15:16:58 UTC 2017 armv7l armv7l
> armv7l GNU/Linux
> Ubuntu 16.04
>
> upon booting slots looks like this
> # cat slots
> 0: ------ -1
> 1: ---l-- -1
> 2: ---l-- -1
> 3: ---l-- -1
>
> i can't write to /gpio/export or to any pin files.
>
> i tried replacing the kernel (would prefer 4.4.59)
> and Ubuntu a couple times but it's obviously deeper then that.
> need to reinstall uBoot maybe how?
> really at a loss and our custom hardware is showing up tomorrow. argh!
> same thing on the two BBB boards i have here at my disposal, so i spread
> the problem from flashing eMMC images cross them?
>
> thanks ,
> Michael
>
>
--
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/7b890a99-6d23-4e0c-9ba4-b60a8ef214d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
