Re: [Machinekit] Re: Machinekit + Debian Stretch on the BeagleBone Black

2017-12-27 Thread TJoseph Powderly 
No, I don't. Nothing connected.  So board is bad?

On Dec 27, 2017 21:52, "Robert Nelson"  wrote:

On Mon, Dec 25, 2017 at 10:56 AM, TJoseph Powderly  wrote:
> Robert
> sorry prev post used MachineKoder's image not yours,
> (i have too many cf's here attempting to get the job done, my bad)
> i will make clean images from your latest
> https://rcn-ee.net/rootfs/bb.org/testing/2017-12-24/
stretch-machinekit/bone-debian-9.3-machinekit-armhf-2017-12-24-4gb.img.xz
> and report back
> thanks tomp


Yeah no eMMC is showing up..

Either your eMMC has completely failed, or you have a cape plugged
into the pins used to communicate with the eMMC..

You have nothing plugged into P8/P9 right?

Regards,

--
Robert Nelson
https://rcn-ee.com/

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Re: Machinekit + Debian Stretch on the BeagleBone Black

2017-12-27 Thread Robert Nelson 
On Mon, Dec 25, 2017 at 10:56 AM, TJoseph Powderly  wrote:
> Robert
> sorry prev post used MachineKoder's image not yours,
> (i have too many cf's here attempting to get the job done, my bad)
> i will make clean images from your latest
> https://rcn-ee.net/rootfs/bb.org/testing/2017-12-24/stretch-machinekit/bone-debian-9.3-machinekit-armhf-2017-12-24-4gb.img.xz
> and report back
> thanks tomp


Yeah no eMMC is showing up..

Either your eMMC has completely failed, or you have a cape plugged
into the pins used to communicate with the eMMC..

You have nothing plugged into P8/P9 right?

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Re: Machinekit + Debian Stretch on the BeagleBone Black

2017-12-24 Thread TJoseph Powderly 

 Robert
Hello & merry Christmas,

I'm the guy who couldnt flash the BBB due to  'mmcblk1 not found'
You suggested logging the boot till the error
here's the log
sorry its quite long
and
i also booted again (with CF but no btn #2) 
then hit SpaceBar to interrupt auto boot
and ran a couple commands in the shell? that may shed some light

the cf card was programmed via
'sudo dd bs=10M status=progress 
if=./bbb_machinekit_debian-stretch_05_12_2017.img of=/dev/sda'

dont screw up christmas for this!

---begin boot log monitored by PL2303 serial cnxd to BBB J1
--- serial connection via  'cu -l /dev/ttyUSB0 115200'--
U-Boot SPL 2017.11-2-g7b415acfc1 (Nov 20 2017 - 13:57:33)
Trying to boot from MMC1


U-Boot 2017.11-2-g7b415acfc1 (Nov 20 2017 - 13:57:33 -0600), Build: 
jenkins-github_Bootloader-Builder-11

CPU  : AM335X-GP rev 2.0
I2C:   ready
DRAM:  512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
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=[0A5A] ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** Bad device 0:2 0x8200 **
** Bad device 0:2 0x8200 **
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 ...
gpio: pin 55 (gpio 55) value is 1
2106 bytes read in 25 ms (82 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.91-ti-rt-r137 ...
8962072 bytes read in 602 ms (14.2 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.91-ti-rt-r137/am335x-boneblack-uboot.dtb ...
57290 bytes read in 79 ms (708 KiB/s)
uboot_overlays: [fdt_buffer=0x6] ...
uboot_overlays: loading /lib/firmware/AM335X-20-00A0.dtbo ...
378 bytes read in 65 ms (4.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1105 bytes read in 352 ms (2.9 KiB/s)
uboot_overlays: uboot loading of [/lib/firmware/BB-HDMI-TDA998x-00A0.dtbo] 
disabled by /boot/uEnv.txt [disable_uboot_overlay_video=1]...
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
695 bytes read in 72 ms (8.8 KiB/s)
uboot_overlays: loading /lib/firmware/AM335X-PRU-UIO-00A0.dtbo ...
853 bytes read in 71 ms (11.7 KiB/s)
uboot_overlays: loading /lib/firmware/univ-bbb-Exx-00A0.dtbo ...
92641 bytes read in 228 ms (396.5 KiB/s)
loading /boot/initrd.img-4.4.91-ti-rt-r137 ...
5527321 bytes read in 382 ms (13.8 MiB/s)
debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait 
init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh] ...
debug: [bootz 0x8200 0x8808:545719 8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   Loading Ramdisk to 8faba000, end 8719 ... OK
   reserving fdt memory region: addr=8800 size=84000
   Loading Device Tree to 8fa33000, end 8fab9fff ... OK

Starting kernel ...

[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.4.91-ti-rt-r137 
(root@a4-imx6q-wandboard-2gb) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) 
) #1 SMP PREEMPT RT Tue Nov 7 03:25:55 UTC 2017
[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] Machine model: TI AM335x BeagleBone Black
[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.0 (sgx neon )
[0.00] PERCPU: Embedded 14 pages/cpu @df8d1000 s25120 r8192 d24032 
u57344
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  
Total pages: 129408
[0.00] Kernel command line: console=ttyO0,115200n8 
bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 
rootwait

Re: [Machinekit] Re: Machinekit + Debian Stretch on the BeagleBone Black

2017-12-18 Thread Robert Nelson 
On Mon, Dec 18, 2017 at 10:35 AM, TJoseph Powderly  wrote:
> Hello
> yes i have usb to serial ( db9) adapters that i use to talk to old cnc
> machines with newer laptops
> i dont know how to use it with BBB.
> I suspect you mean something else,
> where can i read about it?

Make sure it's a 3.3v one..

Plug it into J1, pinout listed here:

https://elinux.org/Beagleboard:BeagleBone_Black_Serial

fire up tio/screen/gtkterm/etc and just log the serial output from the flasher..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Re: Machinekit + Debian Stretch on the BeagleBone Black

2017-12-18 Thread Robert Nelson 
On Mon, Dec 18, 2017 at 9:56 AM, TJoseph Powderly  wrote:
> Hello
> here is result ( ssh'd in with debian:temppwd )
> """
> debian@beaglebone:~$ cat /boot/uEnv.txt
> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
>
> uname_r=4.9.67-ti-r82
> #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/.dtbo
> #uboot_overlay_addr1=/lib/firmware/.dtbo
> #uboot_overlay_addr2=/lib/firmware/.dtbo
> #uboot_overlay_addr3=/lib/firmware/.dtbo
> ###
> ###Additional custom capes
> #uboot_overlay_addr4=/lib/firmware/.dtbo
> #uboot_overlay_addr5=/lib/firmware/.dtbo
> #uboot_overlay_addr6=/lib/firmware/.dtbo
> #uboot_overlay_addr7=/lib/firmware/.dtbo
> ###
> ###Custom Cape
> #dtb_overlay=/lib/firmware/.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_uio (4.4.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...
> #uboot_fdt_buffer=0x6
> ###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
>
> ##Example v3.8.x
> #cape_disable=capemgr.disable_partno=
> #cape_enable=capemgr.enable_partno=
>
> ##Example v4.1.x
> #cape_disable=bone_capemgr.disable_partno=
> #cape_enable=bone_capemgr.enable_partno=
>
> ##enable Generic eMMC Flasher:
> ##make sure, these tools are installed: dosfstools rsync
> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
>
> debian@beaglebone:~$
> """

Thanks!  /boot/uEnv.txt is perfect...  Do you have a usb-serial
adapter, and can you log the serial boot sequence leading up the error
in the flasher?

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.