[beagleboard] BeagleBone Blue: Hack to boot when DC power is restored to DC Jack?
Colleagues,
I have an embedded application for a beaglebone blue in which it is a
NTP client and provides a precision pulse-per-second (PPS) TTL output to
an acoustic modem, all deep inside a pressure housing in an underwater
robotic vehicle
(https://www.whoi.edu/what-we-do/explore/underwater-vehicles/nereid-under-ice).
Our C code running on the beaglebone blue monitors the DC Jack
voltage, and executes a clean shutdown if DC Jack voltage is lost for a
period of time (system("sudo shutdown --poweroff 0 Shutting down due to
loss of DC power")).
Unfortunately for us, when power is restored to the DC Jack, the
beaglebone blue CPU does not power on automatically. The OSD3358 powers
up when the "POW" button is pressed, which pulls down the PMIC_IN_PB_IN
pin D20 on the OSD3358, but of course this button is inaccessible in our
application.
Does anyone have a tested hardware hack that will cause the
BeagleBone Blue to automatically reboot when power is restored to the DC
jack? I am thinking maybe a capacitor in series with a resistor between
DC jack and the based of an NPN transistor, whose emitter is grounded,
and collector momentarily pulls down PMIC_IN_PB_IN when DC power is
restored to the board. But there may be simpler solutions. Any
thoughts are welcome.
Thanks and Best Regards,
-Louis
--
---------
Louis L. Whitcomb, Ph.D.
Professor, Department of Mechanical Engineering
115 Hackerman Hall, 3400 N. Charles Street
Johns Hopkins University, Baltimore, MD, 21218-2681
l...@jhu.edu, 410-516-6724, https://dscl.lcsr.jhu.edu
-
--
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/16a4987b-bd2e-9ea4-d083-0557f5449b6d%40jhu.edu.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Notes on installing Ubuntu 18.04.2 with ROS melodic and robotcontrol pre-installed for Beaglebone Blue
: systemctl status robotcontrol ● robotcontrol.service - robotcontrol Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; vendor preset: enabled) Active: inactive (dead) since Tue 2019-04-16 22:42:46 UTC; 1min 55s ago Process: 676 ExecStop=/usr/bin/rc_kill (code=exited, status=0/SUCCESS) Process: 672 ExecStart=/etc/robotcontrol/link_to_startup_program (code=exited, status=0/SUCCESS) Process: 532 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, status=0/SUCCESS) Main PID: 672 (code=exited, status=0/SUCCESS) Apr 16 22:42:39 beaglebone systemd[1]: Starting robotcontrol... Apr 16 22:42:42 beaglebone rc_startup_routine[532]: robotcontrol startup routine complete Apr 16 22:42:46 beaglebone systemd[1]: Started robotcontrol. Apr 16 22:42:46 beaglebone systemd[672]: robotcontrol.service: Executable /etc/robotcontrol/link_to_startup_program missing, skipping: No Apr 16 22:42:46 beaglebone rc_kill[676]: No existing robot control program is running. 9. You can change which program robotcontrol runs on boot with the command "sudo dpkg-reconfigure librobotcontrol", and read the put put and prompts. 10. Here is output of "systemctl status robotcontrol" when rc_blink is set to automatically load upon boot: beagle@beaglebone:~$ systemctl status robotcontrol ● robotcontrol.service - robotcontrol Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-04-16 22:49:36 UTC; 57s ago Process: 499 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, status=0/SUCCESS) Main PID: 574 (link_to_startup) Tasks: 3 (limit: 1024) CGroup: /system.slice/robotcontrol.service └─574 /etc/robotcontrol/link_to_startup_program Apr 16 22:49:31 beaglebone systemd[1]: Starting robotcontrol... Apr 16 22:49:32 beaglebone rc_startup_routine[499]: robotcontrol startup routine complete Apr 16 22:49:36 beaglebone systemd[1]: Started robotcontrol. 11. That is it. Read the manual here: http://strawsondesign.com/docs/librobotcontrol/index.html Note that the manual includes a nice project template for robot 12. To update or install additional ubuntu binary packages, including additional ROS melodic packages, you will need to connect your BBBL to the internet. The easiest way to do this is to connect via WiFi (read the manual, #11 above), or connect a USB-Ethernet adapter to the BBBL's USB host connection, and connect to a DHCP Ethernet router. -- - Louis L. Whitcomb, Ph.D. Professor, Department of Mechanical Engineering 115 Hackerman Hall, 3400 N. Charles Street Johns Hopkins University, Baltimore, MD, 21218-2681 l...@jhu.edu, 410-516-6724, https://dscl.lcsr.jhu.edu -< -- 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/7867fe54-fc94-8f5f-c15f-3919fe17f4c7%40jhu.edu. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Beaglebone Blue Ubuntu 18.04.2 problem with robotcontrol
Robert, That was it! Everything works! Thank you! -Louis On 4/14/19 8:38 PM, Robert Nelson wrote: eeprom:[A335BNLTBLA21717EL003552] model:[TI_AM335x_BeagleBone_Blue] dogtag:[BeagleBoard.org ROS Image 2019-03-03] bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.09-2-g08ae12f051]:[location: dd MBR] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.05-rc1-2-g35aecb]:[location: dd MBR] Bootloader installed on the eMMC is too old and breaking things.. Just run: sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 and reboot. Regards, -- 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/cb1bc933-8a7a-4413-1db3-e350f705c5eb%40jhu.edu. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Beaglebone Blue Ubuntu 18.04.2 problem with robotcontrol
Hello, I am running Robert's Ubuntu image with ROS pre-installed on a BeaglewBone Blue, and have not figured out how to get the full robotcontrol system to work. This is the image I am running: https://rcn-ee.net/rootfs/bb.org/testing/2019-03-03/bionic-ros-iot/bone-ubuntu-18.04.2-ros-iot-armhf-2019-03-03-6gb.img.xz Here is a typical error: beagle@beaglebone:~$ rc_check_battery ERROR in rc_adc_init, failed to open iio adc interface : No such file or directory Perhaps kernel or device tree is too old I did a source install of the robotcontrol utilities, no change. Some additional clues are below. I must be missing something obvious. I would be grateful for any pointers. Thanks and Best Regards, -Louis beagle@beaglebone:~$ uname -a Linux beaglebone 4.19.25-ti-rt-r12 #1bionic SMP PREEMPT RT Fri Mar 1 07:53:07 UTC 2019 armv7l armv7l armv7l GNU/Linux beagle@beaglebone:~$ beagle@beaglebone:~$ rc_test_drivers Kernel: 4.19.25-ti-rt-r12 BeagleBoard.org ROS Image 2019-03-03 Debian: buster/sid PASSED: gpio 0 PASSED: gpio 1 PASSED: gpio 2 PASSED: gpio 3 PASSED: pwm0 PASSED: pwm1 PASSED: pwm2 PASSED: eqep0 PASSED: eqep1 PASSED: eqep2 ERROR: pru-rproc driver not loaded PASSED: uart1 PASSED: uart2 PASSED: uart4 PASSED: uart5 PASSED: i2c1 PASSED: i2c2 PASSED: spi PASSED: LED ERROR: ADC iio driver not loaded Currently running on a: MODEL_BB_BLUE Robot Control library Version: 1.0.4 beagle@beaglebone:~$ sudo systemctl status robotcontrol.service ● robotcontrol.service - robotcontrol Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-04-14 22:00:35 UTC; 8min ago Process: 3313 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, status=255) Apr 14 22:00:35 beaglebone systemd[1]: Starting robotcontrol... Apr 14 22:00:35 beaglebone rc_startup_routine[3313]: timeout reached while waiting for PRU remoteproc dr Apr 14 22:00:35 beaglebone rc_startup_routine[3313]: TIMEOUT REACHED Apr 14 22:00:35 beaglebone systemd[1]: robotcontrol.service: Control process exited, code=exited status= Apr 14 22:00:35 beaglebone systemd[1]: robotcontrol.service: Failed with result 'exit-code'. Apr 14 22:00:35 beaglebone systemd[1]: Failed to start robotcontrol. beagle@beaglebone:~$ beagle@beaglebone:~$ more /var/log/robotcontrol/startup_log.txt start time (s): 2282.24 time (s): 2282.33 GPIO loaded time (s): 2282.34 PWM loaded time (s): 2282.35 eQEP loaded TIMEOUT_REACHED timeout reached while waiting for PRU remoteproc driver beagle@beaglebone:~$ beagle@beaglebone:~$ sudo /opt/scripts/tools/version.sh git:/opt/scripts/:[36a476c67f707ba2698bfb30452ebd2951162ce2] eeprom:[A335BNLTBLA21717EL003552] model:[TI_AM335x_BeagleBone_Blue] dogtag:[BeagleBoard.org ROS Image 2019-03-03] bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.09-2-g08ae12f051]:[location: dd MBR] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.05-rc1-2-g35aecb]:[location: dd MBR] kernel:[4.19.25-ti-rt-r12] nodejs:[v8.10.0] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[enable_uboot_cape_universal=1] pkg check: to individually upgrade run: [sudo apt install --only-upgrade ] pkg:[bb-cape-overlays]:[4.4.20190404.0-0rcnee0~bionic+20190404] pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~bionic+20190227] pkg:[kmod]:[24-1ubuntu3.2rcnee0~bionic+20190208] pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~bionic+20190327] groups:[beagle : beagle adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai] cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet] dmesg | grep pinctrl-single [1.402492] pinctrl-single 44e10800.pinmux: 142 pins, size 568 dmesg | grep gpio-of-helper beagle@beaglebone:~$ - Louis L. Whitcomb, Ph.D. Professor, Department of Mechanical Engineering 115 Hackerman Hall, 3400 N. Charles Street Johns Hopkins University, Baltimore, MD, 21218-2681 l...@jhu.edu, 410-516-6724, https://dscl.lcsr.jhu.edu - -- 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/067af4d2-69ab-d8e0-fa6c-2fd80e9914ce%40jhu.edu. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Roboticscape support under Ubuntu 16.04 LTS on Beaglebone Black Wireless + Robotics Cape
Hi Robert:
Just checking in to see if you have had a chance to look into the
combination of the robotics cape under Ubuntu that we discussed via
email on 11/27/2017? The beaglebone blue worked great under Ubuntu, but
the roboticscape does not. If not, perhaps you can point me in the
right direction on how to fix this.
Wishing you safe and happy holidays!
Best Regards,
-Louis
-
Louis L. Whitcomb, Ph.D.
Professor, Department of Mechanical Engineering
115 Hackerman Hall, 3400 N. Charles Street
Johns Hopkins University, Baltimore, MD, 21218-2681
l...@jhu.edu, 410-516-6724, dscl.me.jhu.edu
-
On 11/27/2017 04:14 PM, Robert Nelson wrote:
Yeah, i need to fix that combination. My robotic's cape is at work,
and i'm at home today with the furnace guys over..
Regards,
On Mon, Nov 27, 2017 at 10:00 AM, Louis L. Whitcomb <l...@jhu.edu> wrote:
Dear Robert and Jason:
I am trying to work out the details getting the EduMIP running with ROS
under Ubuntu 16.04 on the Beaglebone Blue and also the Beaglebone Black
wireleess+ Robotics Cape, and hope you may office some pointers. I have the
latest version of roboticscape installed ("sudo apt-get install
roboticscape").
ubuntu@arm:~$ sudo apt-get install roboticscape
[sudo] password for ubuntu:
Reading package lists... Done
Building dependency tree
Reading state information... Done
roboticscape is already the newest version
(0.3.4-git20170602-0rcnee4~xenial+20171108).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Here are my 2 quesions:
1. On the Beaglebone Blue under Ubuntu 16.04, when you run a rc_xxx program
it reports the error "ERROR: pru-rproc driver missing", but then runs
normally. Example:
ubuntu@arm:~$ rc_balance
ERROR: pru-rproc driver missing
Inner Loop controller D1:
So far I have been ignoring this message.
Question: any thoughts?
2. On the Beaglebone Black wireless + robotics cape, under Ubuntu 16.04,
when you run rc_xxx program it reports numerous startup errors. Some
programs such as rc_check_battery run normally after printing numerous
errors. Other programs such as rc_balance print a continuous stram of
"ERROR: uart4 must be initialized first" and fail to operate properly,
perhaps due to the stream of "ERROR: uart4 must be initialized first"
messages (see below).
The warning messages for rc_balance begin with this (longer transcript at
the end of this email)
ubuntu@arm:~$ rc_balance
WARNING: RoboticsCape library should only be run on BB Blue, Black, and
Black wireless when the roboticscape device tree is in use.
If you are on a BB Black or Black Wireless, please execute
"configure_robotics_dt.sh" and reboot to enable the device tree
can't open: /sys/devices/platform/ocp/ocp:P9_28_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_23_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_11_pinmux/state
Pinmux: No such file or directory
So I ran Robotics_Cape_Installer/device_tree$ sudo
./configure_robotics_dt.sh, but configure_robotics_dt.sh appears to only
support Debian:
ubuntu@arm:~/Robotics_Cape_Installer/device_tree$ sudo
./configure_robotics_dt.sh
ERROR: This is not Debian Jessie.
Flash the latest Jessie image to your BBB
or use the Wheezy branch of this installer.
ubuntu@arm:~/Robotics_Cape_Installer/device_tree$
Question: Do you have suggestions on how to fix this?
Thanks and Best Regards,
-Louis
ubuntu@arm:~$ rc_balance
WARNING: RoboticsCape library should only be run on BB Blue, Black, and
Black wireless when the roboticscape device tree is in use.
If you are on a BB Black or Black Wireless, please execute
"configure_robotics_dt.sh" and reboot to enable the device tree
can't open: /sys/devices/platform/ocp/ocp:P9_28_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_23_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_11_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_22_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_21_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_26_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_24_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_30_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_29_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_31_pinmux/state
Pinmux: No such file or directory
WARNING: missing PINMUX driver
You probbaly just need a newer kernel
ERROR: ti-eqep driver not loaded for eqep0
WA
[beagleboard] Roboticscape support under Ubuntu 16.04 LTS on Beaglebone Black Wireless + Robotics Cape
failed to initialize UART4 for dsm ERROR: trying to disable motors before they have been initialized ERROR: uart4 must be initialized first RUNNING: Hold upright to balance. θ| θ_ref |φ| φ_ref |γ| D1_u | D3_u | vBatt |arm_state| 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 8.449 |DISARMED |ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 0.000 | 8.449 |DISARMED |ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ERROR: uart4 must be initialized first ubuntu@arm:~/Robotics_Cape_Installer/device_tree$ rc_check_battery can't open: /sys/devices/platform/ocp/ocp:P9_28_pinmux/state Pinmux: No such file or directory can't open: /sys/devices/platform/ocp/ocp:P9_23_pinmux/state Pinmux: No such file or directory can't open: /sys/devices/platform/ocp/ocp:P9_11_pinmux/state Pinmux: No such file or directory can't open: /sys/devices/platform/ocp/ocp:P9_22_pinmux/state Pinmux: No such file or directory can't open: /sys/devices/platform/ocp/ocp:P9_21_pinmux/state Pinmux: No such file or directory can't open: /sys/devices/platform/ocp/ocp:P9_26_pinmux/state Pinmux: No such file or directory can't open: /sys/devices/platform/ocp/ocp:P9_24_pinmux/state Pinmux: No such file or directory can't open: /sys/devices/platform/ocp/ocp:P9_30_pinmux/state Pinmux: No such file or directory can't open: /sys/devices/platform/ocp/ocp:P9_29_pinmux/state Pinmux: No such file or directory can't open: /sys/devices/platform/ocp/ocp:P9_31_pinmux/state Pinmux: No such file or directory WARNING: missing PINMUX driver You probbaly just need a newer kernel ERROR: ti-eqep driver not loaded for eqep0 WARNING: failed to initialize eQEP0 ERROR: ti-eqep driver not loaded for eqep1 WARNING: failed to initialize eQEP1 ERROR: ti-eqep driver not loaded for eqep2 WARNING: failed to initialize eQEP2 ERROR: ti-pwm driver not loaded for pwm subsystem 1 ERROR: failed to initialize hrpwm1 WARNING: Failed to initialize motors ERROR: pru-rproc driver missing Pack: 8.42V Cell: 4.21V DC Jack: 0.00V ^C -- --------- Louis L. Whitcomb, Ph.D. Professor, Department of Mechanical Engineering 115 Hackerman Hall, 3400 N. Charles Street Johns Hopkins University, Baltimore, MD, 21218-2681 l...@jhu.edu, 410-516-6724, dscl.me.jhu.edu - -- 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/3c901bcb-ae22-a5f4-8715-7831e7c36a10%40jhu.edu. For more options, visit https://groups.google.com/d/optout.
[beagleboard] New ROS EduMIP Web Page
Hi Jason and Tom: I recently created a new web page with instructions on running ROS on the EduMIP, including Beaglebone Blue, under Ubuntu 16.04 LTS, here is the link: Can update the ROS links on the beaglebone web pages and the renaissance robotics web pages from this obsolete page https://dscl.lcsr.jhu.edu/home/courses/me530707_2017_edumip_ros to this new page https://dscl.lcsr.jhu.edu/home/courses/EduMIP_ROS This new page has a link to assembly instructions that I revised for the EduMIP with the Beaglebone Blue, and links to a Ubuntu 16.04 LTS linux image (many thanks to Robert Nelson for his help with this) for the Beaglebone Black/Blue with ROS Kinetic and robotics cape support pre-installed. Best Regards, -Louis -- - Louis L. Whitcomb, Ph.D. Professor, Department of Mechanical Engineering 115 Hackerman Hall, 3400 N. Charles Street Johns Hopkins University, Baltimore, MD, 21218-2681 l...@jhu.edu, 410-516-6724, dscl.me.jhu.edu - -- 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/4cab754c-20bf-e19d-980e-e12ca37d8405%40jhu.edu. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: ROS on beaglebone blue
Hello Jason at al: When I installed ROS on the BBB-Wireless in January 2017 I started with a recent Debian image. At that time the ROS binaries for Debian were not available, so I did a source-build of ROS. For my ROS course students I compressed 32GB Debian Jesse image that has ROS kinetic and support for the Robotics Cape pre-installed – the compressed 32GB image is about 4GB. Get it here: https://jh.box.com/v/530-707-Dropbox it is the file "BBBW-debian8_6-ROSKineticFull_2017-02-16_32gb.img.zip". Building ROS from source on the BBB is not hard. You need to create and enable a swap file. The build takes about 26 hours. Instructions are here: http://wiki.ros.org/kinetic/Installation/Source I posted some additional notes here: https://dscl.lcsr.jhu.edu/home/courses/me530707_2017_edumip_ros/#Notes_on_Installing_ROS_on_the_BBB I see from here http://wiki.ros.org/kinetic/Installation/Debian that ROS Kinetic binaries are claimed to be available for Debian/ARM64. I have not tested it, but will do so shortly as I will be giving a short course on ROS next month and will be once again using the EDUMip as a teaching robot in this short course. Best Regards, -Louis ----- Louis L. Whitcomb, Ph.D. Professor, Department of Mechanical Engineering 115 Hackerman Hall, 3400 N. Charles Street Johns Hopkins University, Baltimore, MD, 21218-2681 l...@jhu.edu, 410-516-6724, dscl.me.jhu.edu - On 10/28/2017 10:40 PM, Jason Kridner wrote: Louis, Do you have ideas about the below issue? Matza, Can we bring the list back into copy? I really, really dislike one-on-one support. This info needs to go back to the forum. Regards, Jason On Sat, Oct 28, 2017 at 6:03 PM Matza IchaÏ <ichai.ma...@gmail.com <mailto:ichai.ma...@gmail.com>> wrote: I haven't tested it on the black but I had the same issue with this tutorial (unable to locate package) Here are all my tests: 1) bbblue with debian stretch (on many version) and try to install ros-lunar: when i was trying to install ROS-Base: (Bare Bones) with this command sudo apt-get install ros-lunar-ros-base i had this error "E:Unable to locate package ros-lunar-ros-base" 2)bblue with debian jessie (on many version) and try to install ros-kinetic same error but with "E:Unable to locate package ros-kinetic-ros-base" 3)I had also try to install the package in local way without success. 4) I had also try to flash with ubuntu xenial because ros accepte armhf architecture on ubuntu but I can't connect with ssh to my bblue (I have bought wires in order to connect in a serial way, I am waiting to receive them) 5) I had also tried to run this command apt install ros-robot the same problem appear Ps: Tell me if you need any details on the errors or what I have done. Thanks a lot 2017-10-28 23:56 GMT+02:00 Jason Kridner <jkrid...@gmail.com <mailto:jkrid...@gmail.com>>: On Sat, Oct 28, 2017 at 5:54 PM Matza IchaÏ <ichai.ma...@gmail.com <mailto:ichai.ma...@gmail.com>> wrote: Thanks for your quick answer but i have already tested this tutorial, the issue is that it is designed for the beaglebone black which has a arm64 architecture (ROS can be installed on it but it's not designed for armhf architecture on beaglebone blue) They have the same armhf architecture. image.png Thank you very much. 2017-10-28 23:32 GMT+02:00 Jason Kridner <jkrid...@gmail.com <mailto:jkrid...@gmail.com>>: Could use some updates, but here is the most tested starting point I know about... https://dscl.lcsr.jhu.edu/home/courses/me530707_2017_edumip_ros/ On Oct 28, 2017, at 3:36 PM, Someone wrote: Hello, I have bought the beaglebone blue because i have seen that it was compatible with ROS. However the beaglebone blue is designed for debian and it has armhf architecture which is not proposed by ROS. Can you send me a procedure to install ROS on the beaglebone blue under any version of debian ? (I have already looked on many forum and I have found that most of people had the same problem ) Thank you very much. Kind regards. -- https://beagleboard.org/about -- https://beagleboard.org/about -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard"
