I've just handed off my BBBlue to a student team to interface it to SparkFun robot[1].Where should I point them to get current information on the Blue? For example, what image should they be running?
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/b61572ea-1ccd-41ed-9832-7577662ddbd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi, I am one of the students who was given the BBBlue to interface with the robot, We have the latest image on an SD card in the BBBlue, on boot the leds appear to go through the normal boot routine. However we are unable to interface with it in anyway.
Initially we tried to connect with the usb network cable, however it was not recognized as even being attached by Ubuntu or windows, where as the black normally will show up as a device. So we tried to interface with UART0 which we assume is the debug serial port, and the only thing we read was nonsense, using the same serial config that we use to interface with the black.
So we are unsure if we are missing something or if there is maybe a problem with the board
On Friday, October 14, 2016 at 2:58:28 PM UTC-4, RobertCNelson wrote:On Fri, Oct 14, 2016 at 1:41 PM, Mark A. Yoder <mark.a...@gmail.com> wrote:
> I've just handed off my BBBlue to a student team to interface it to SparkFun
> robot[1].
>
> Where should I point them to get current information on the Blue? For
> example, what image should they be running?
Start with Last sunday's iot image.. (this sunday's will be better)..
then follow:
https://github.com/StrawsonDesign/Robotics_Cape_Installer
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/74094b8c-4f74-4a8c-a025-f3ead45219ad%40googlegroups.com.
Hi, I am one of the students who was given the BBBlue to interface with the robot, We have the latest image on an SD card in the BBBlue, on boot the leds appear to go through the normal boot routine. However we are unable to interface with it in anyway. Initially we tried to connect with the usb network cable, however it was not recognized as even being attached by Ubuntu or windows, where as the black normally will show up as a device.
So we tried to interface with UART0 which we assume is the debug serial port, and the only thing we read was nonsense, using the same serial config that we use to interface with the black. So we are unsure if we are missing something or if there is maybe a problem with the board
/dev/ttyACM0.
It depends on which serial to USB device you're using. Here, I use a PL2303hx based serial to USB cable, and that shows up as /dev/ttyUSB0.
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/506194fd-bc89-4f36-bcfe-3aa7448e5050%40googlegroups.com.
Id, double check and document everything when trying ot setup the serial debug port on the Beaglebone blue. Which to me going form pictures on the internet. Just seems to be *another* beaglebone, but with a blue PCB. In other words. It appears to be very similar to if not exactly the same as a beaglebone black, with a blue PCB, and a Robotics cape included with it.
However, with that said. There are typically "hooks" built into these images that check the eeprom to see which board it is. When uboot first comes up, before passing control to Linux.So, being verbose on the groups here, for this problem, would be helpful.
On Mon, Oct 24, 2016 at 12:02 PM, Samuel Lawrence <samuella...@gmail.com> wrote:
Hello,I am the other student working on the project. Thanks for the help you all have given. We were embarrassed to find out last Thursday that the USB cable we were using was off-spec and had no data wires so we were getting power but no communication.I had no idea such cables existed but it's something one should check for in the debugging process.On the issue of the terminal connection on UART 1: I can connect to the beaglebone black using uart0 on the debug header, but we have had no such luck with the blue. This is less pressing to us now that we can communicate with the board but we will post when we get to solving that problem.
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/506194fd-bc89-4f36-bcfe-3aa7448e5050%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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORqYUW3iCO3s1iCG-xZYuu790UGijPPh4uuCWcdvjY2nXw%40mail.gmail.com.