Re: [beagleboard] u-boot fix for phantom UART character hang at boot
I’m back and up and running with my new serial debug cable. Maybe you can help me understand this. I have 2 BBB’s one Original BBB and an Arrow industrial temperature BBB. Both were flashed from the same microSD card image. Original BBB has new u-boot on it and will boot successfully. (see below Boot Log Original new u-boot.txt) Then I connected to the new Arrow BBB before loading the new u-boot. It boots OK. (see Boot Log Arrow BBB old u-boot.txt) Then I loaded the same new u-boot on the Arrow BBB and now it will not complete the boot. (see Boot Log Arrow BBB new u-boot.txt) The | character at the end of this boot log file was a rotating line pattern that continued forever like it is waiting for something. All the BBB blue LED’s are on. I really appreciate you taking the time to look at this, Kirk ** ** Boot Log Original new u-boot.txt ** ** U-Boot SPL 2015.10-2-gec579ac-dirty (May 05 2016 - 11:39:07) bad magic U-Boot 2015.10-2-gec579ac-dirty (May 05 2016 - 11:39:07 -0500) Watchdog enabled I2C: ready DRAM: 512 MiB Reset Source: Power-on reset has occurred. MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment Net:not set. Validating first E-fuse MAC cpsw gpio: pin 53 (gpio 53) value is 1 Card did not respond to voltage select! Card did not respond to voltage select! gpio: pin 56 (gpio 56) value is 0 gpio: pin 55 (gpio 55) value is 0 gpio: pin 54 (gpio 54) value is 0 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 1013 bytes read in 14 ms (70.3 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-3.8.13-bone70 ... 5617184 bytes read in 326 ms (16.4 MiB/s) loading /boot/dtbs/3.8.13-bone70/am335x-boneblack.dtb ... 26098 bytes read in 22 ms (1.1 MiB/s) loading /boot/initrd.img-3.8.13-bone70 ... 2865938 bytes read in 174 ms (15.7 MiB/s) debug: [console=ttyO0,115200n8 text capemgr.disable_partno=BB-BONELT-HDMI,BB-BON ELT-HDMIN root=UUID=9579490e-1d99-4afc-89f6-496ad41aef7a ro rootfstype=ext4 rootwait quiet init=/lib/systemd/systemd] ... debug: [bootz 0x8200 0x8808:2bbb12 0x8800] ... Kernel image @ 0x8200 [ 0x00 - 0x55b620 ] ## Flattened Device Tree blob at 8800 Booting using the fdt blob at 0x8800 Loading Ramdisk to 8fd44000, end 8b12 ... OK Loading Device Tree to 8fd3a000, end 8fd435f1 ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.372834] omap2_mbox_probe: platform not supported [0.527766] tps65217-bl tps65217-bl: no platform data provided [0.591300] bone-capemgr bone_capemgr.9: slot #0: No cape found [0.628407] bone-capemgr bone_capemgr.9: slot #1: No cape found [0.665515] bone-capemgr bone_capemgr.9: slot #2: No cape found [0.702625] bone-capemgr bone_capemgr.9: slot #3: No cape found [0.721297] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [0.782963] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [0.794660] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [0.801933] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single Loading, please wait... systemd-fsck[205]: rootfs: clean, 112865/227584 files, 658849/909056 blocks Debian GNU/Linux 7 beaglebone ttyO0 BeagleBoard.org Debian Image 2015-03-01 Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian default username:password is [debian:temppwd] The IP Address for usb0 is: 192.168.7.2 beaglebone login: *** ** Boot Log Arrow BBB old u-boot.txt * *** U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06) U-Boot 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06), Build: jenkins-github_Bootloader-Builder-105 Watchdog enabled I2C: ready DRAM: 512 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 Using default environment Net:not set. Validating first E-fuse MAC cpsw Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 Card did not respond to voltage select! Card did not respond to voltage select! gpio: pin 56 (gpio 56) value is 0 gpio: pin 55 (gpio 55) value is 0 gpio: pin 54 (gpio 54) value is 0 switch to partitions #0, OK mmc1(part 0) is current device gpio: pin 54 (gpio 54) value is 1
Re: [beagleboard] u-boot fix for phantom UART character hang at boot
So it looks like I have get a serial cable?? Or is the bootloader log written to a file somewhere. I can't find it. (it does boot up most of the time) Thanks, Kirk -- 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/c4560beb-7142-405f-a118-97c7e468117a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] u-boot fix for phantom UART character hang at boot
Does anyone know if this version: Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux already has the "u-boot fix for phantom UART character hang at boot" My application cycles the power and re-boots often and occasionally it hangs up at boot with just the blue power LED on. Thanks, Kirk -- 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/5aad848c-b801-47b3-bee6-cb6a32f43847%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] WiFi access point on UWN200 USB WiFi adapter
My Beaglebone Black is running: Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux I'm successfully using a UWN200 USB Wi-Fi adapter. I do all my work via WiFi. The UWN200 uses a Ralink/MediaTek MT7601 based USB Wifi chip. Now I'm trying to configure it to boot up in access point mode so I can connect directly to the BBB from my laptop without joining the WiFi router. I've googled and searched and read many procedures. Some older, Some for different USB WiFi adapters. Some for older Linux versions. I have 2 pages of web links saved. (including this one from Beagleboard "Debian 3.8.13-bone-68 and RALINK 7601 driver" which ends with a rather depressing: "I fear this is a losing battle...") I have yet to find a coherent list of steps I can take to get access point mode running. I would greatly appreciate any help I can get on this. Thanks, Kirk -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] PyBBIO on Beaglebone Black
I just updated my Beaglebone Black to: Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux I installed the PyBBIO library and created the following test program: ** begin code *** from bbio import * from bbio.libraries.RotaryEncoder import RotaryEncoder encoder = RotaryEncoder(RotaryEncoder.EQEP2b) def setup(): print in setup def loop(): print in loop run(setup, loop) end code everything works as expected until I add the line: encoder = RotaryEncoder(RotaryEncoder.EQEP2b) When I ctrl-c to exit the loop I get errors. (see below) in loop in loop in loop^C Error in atexit._run_exitfuncs: Traceback (most recent call last): File /usr/lib/python2.7/atexit.py, line 24, in _run_exitfuncs func(*targs, **kargs) File /usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py, line 21, in bbio_cleanup for cleanup in ADDITIONAL_CLEANUP: TypeError: must be string, not int Error in sys.exitfunc: Traceback (most recent call last): File /usr/lib/python2.7/atexit.py, line 24, in _run_exitfuncs func(*targs, **kargs) File /usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py, line 21, in bbio_cleanup for cleanup in ADDITIONAL_CLEANUP: TypeError: must be string, not int root@beaglebone:/kirkpy# Any help figuring this out would be much appreciated, Kirk -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: PyBBIO v0.9.3
I just updated my Beaglebone Black to: Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux I installed the PyBBIO library and created the following test program: ** begin code *** from bbio import * from bbio.libraries.RotaryEncoder import RotaryEncoder encoder = RotaryEncoder(RotaryEncoder.EQEP2b) def setup(): print in setup def loop(): print in loop run(setup, loop) end code everything works as expected until I add the line: encoder = RotaryEncoder(RotaryEncoder.EQEP2b) When I ctrl-c to exit the loop I get errors. (see below) in loop in loop in loop^C Error in atexit._run_exitfuncs: Traceback (most recent call last): File /usr/lib/python2.7/atexit.py, line 24, in _run_exitfuncs func(*targs, **kargs) File /usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py, line 21, in bbio_cleanup for cleanup in ADDITIONAL_CLEANUP: TypeError: must be string, not int Error in sys.exitfunc: Traceback (most recent call last): File /usr/lib/python2.7/atexit.py, line 24, in _run_exitfuncs func(*targs, **kargs) File /usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py, line 21, in bbio_cleanup for cleanup in ADDITIONAL_CLEANUP: TypeError: must be string, not int root@beaglebone:/kirkpy# Any help figuring this out would be much appreciated, Kirk On Friday, February 13, 2015 at 4:24:45 PM UTC-8, Alexander Hiam wrote: I just released PyBBIO version 0.9.3 - details here: http://graycat.io/beaglebone/pybbio-update-version-0-9-3/ PyBBIO: https://github.com/graycatlabs/PyBBIO -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] eQEP on Beaglebone Black on Latest Debian
I just updated my Beaglebone Black to: Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux I'm trying to get the eQEP working. I would like to use the alternate pinout for eQEP2 that doesn't conflict with the HDMI. I think it should use PyBBIO-eqep2b-00A0.dtbo When I use the command: echo bone_eqep2b /sys/devices/bone_capemgr.9/slots I get: -bash: /sys/devices/bone_capemgr.9/slot: No such file or directory dmesg shows: [ 156.166488] bone-capemgr bone_capemgr.9: part_number 'bone_eqep2b', version 'N/A' [ 156.17] bone-capemgr bone_capemgr.9: slot #7: generic override [ 156.166712] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 7 [ 156.166760] bone-capemgr bone_capemgr.9: slot #7: 'Override Board Name,00A0,Override Manuf,bone_eqep2b' [ 156.167027] bone-capemgr bone_capemgr.9: slot #7: Requesting part number/version based 'bone_eqep2b-00A0.dtbo [ 156.167075] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 'bone_eqep2b-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 156.240762] bone-capemgr bone_capemgr.9: failed to load firmware 'bone_eqep2b-00A0.dtbo' If I try: echo bone_eqep2 /sys/devices/bone_capemgr.9/slots I don't get the No such file or directory error dmesg shows: [ 312.600610] bone-capemgr bone_capemgr.9: part_number 'bone_eqep2', version 'N/A' [ 312.600799] bone-capemgr bone_capemgr.9: slot #8: generic override [ 312.600845] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 8 [ 312.601071] bone-capemgr bone_capemgr.9: slot #8: 'Override Board Name,00A0,Override Manuf,bone_eqep2' [ 312.605781] bone-capemgr bone_capemgr.9: slot #8: Requesting part number/version based 'bone_eqep2-00A0.dtbo [ 312.605841] bone-capemgr bone_capemgr.9: slot #8: Requesting firmware 'bone_eqep2-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 312.605907] bone-capemgr bone_capemgr.9: slot #8: dtbo 'bone_eqep2-00A0.dtbo' loaded; converting to live tree [ 312.606448] bone-capemgr bone_capemgr.9: slot #8: #3 overlays [ 312.620816] pinctrl-single 44e10800.pinmux: pin 44e108b8 already requested by hdmi.13; cannot claim for 48304180.eqep [ 312.632288] pinctrl-single 44e10800.pinmux: pin-46 (48304180.eqep) status -22 [ 312.639920] pinctrl-single 44e10800.pinmux: could not request pin 46 on device pinctrl-single [ 312.675364] eqep 48304180.eqep: unable to select pin group [ 312.677533] bone-capemgr bone_capemgr.9: slot #8: Applied #3 overlays. I would very much appreciate some help to figure this out, Kirk -- 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. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Beaglebone Black eQEP
On Monday, March 16, 2015 at 1:45:56 PM UTC-7, RobertCNelson wrote: On Mon, Mar 16, 2015 at 3:28 PM, kirkmit...@gmail.com javascript: wrote: I'm trying to get quadrature encoder signals into my new Beaglebone Black board. I have a Rev. C BBB running: Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l GNU/Linux *** 1st question: I understand that recent Debian distributions on the BBB have eQEP drivers included. Does the above version have the eQEP drivers? If not, which version do I need? It was added in bone48 https://github.com/RobertCNelson/bb-kernel/commit/b7bc988c048b69f03b71c72f7c544f2348f378d0 either upgrade or grab the latest release. http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases Regards, -- Robert Nelson https://rcn-ee.com/ I'm a newbie at Linux so bear with me. Are you saying it would be possible to upgrade to add the eQEP support without wiping the BBB clean and installing the latest Linux relase? If so can you please point to documentation on how to do that? I've installed a few libraries and configured some things for WiFi and it would be nice not to have to do that all again. Thanks for your help Kirk -- 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. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Beaglebone Black eQEP
I'm trying to get quadrature encoder signals into my new Beaglebone Black board. I have a Rev. C BBB running: Linux beaglebone 3.8.13-bone47 #1 SMP Fri Apr 11 01:36:09 UTC 2014 armv7l GNU/Linux *** 1st question: I understand that recent Debian distributions on the BBB have eQEP drivers included. Does the above version have the eQEP drivers? If not, which version do I need? *** 2nd question: I copied the pre-compiled dtbo files from here: https://github.com/Teknoman117/beaglebot/tree/master/encoders/dts to /lib/firmware as explained in the readme file. The files I copied are: bone_eqep0-00A0.dtbo bone_eqep1-00A0.dtbo bone_eqep2-00A0.dtbo bone_eqep2b-00A0.dtbo Problem is when I issue this command: root@beaglebone:/sys/devices/bone_capemgr.9# echo bone_eqep2b /sys/devices/bone_capemgr.9/slots -bash: echo: write error: Invalid argument you can see it gives me an invalid argument error. And I don't see the slots file change to indicate that it has loaded the eQEP driver. This is what I see in the slots file: 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI Do you know what I'm doing wrong? Thanks, Kirk -- 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. For more options, visit https://groups.google.com/d/optout.
