Additionally, I presume you have a Robotics application which you're
wanting to experiment with. With that said, maybe it could be beneficial to
get one of the other variants initially. Then if you're like me, opt out of
the wireless variants, and if you need wireless get a well supported dongle
with an external antenna cable connection.

By well supported, I mean a dongle that uses a chipset that is well
supported in Linux( Debian ), and is not too short. The length could
potentially play a factor in interference with the HDMI, *if* you're using
the HDMI output at all If not it is my understanding that you can simply
disable HDMI to bypass that problem.

I did want to say that I also own an rpi 3.0, and I know there is a lot
more documentation all over the web concerning that platform. Some of the
software, and utilities seem to be pretty good too. With that said, in the
context of robotics, and general embedded Linux. I'd have to say that the
beaglebone SBC's are light years ahead, in terms of flexibility, and
connectivity. Where the beaglebone platform is also a platform that
requires more knowledge from the user or engineer using it. Basically,
aside from what you'll find googling, and what information people will
share here. There is no hand holding on this platform. Which means you need
to check everything you're working with.

For instance, if you had any IO connected to this board through any of the
GPIO, or other periphery pins while you powered the board up, or down. You
could have damaged the processor. So all the pins need to be isolated in
that case. Ethernet, USB, and the serial debug port are exceptions to this
rule. But are not what I'd exactly consider "periphery" in the context of
embedded systems.

On Fri, Mar 31, 2017 at 1:29 PM, William Hermans <[email protected]> wrote:

>
>
> On Thu, Mar 30, 2017 at 9:22 PM, Ted Carancho <[email protected]>
> wrote:
>
>> Thanks for the response William,
>> I followed the directions online to put in a formatted uSD card with
>> firmware, held the boot button down (it's a momentary push button, not an
>> on/off switch) while plugging in a 3S Lipo (12V).  No booting from uSD
>> happens . To double check I viewed the process on YouTube (for BB Black) to
>> make sure I was doing what was expected.
>>
>
> The only documentation I've seen seems to indicate that the Beaglebone
> blue has a 2 cell 6-16v charger circuit, which tells me that battery input
> voltage can also be in that range.Or more correctly 12v nominal battery
> input. However, with that said, the documentation I've seen to date is not
> what I'd consider to be complete. Which is to say, I don't have one of
> these boards, and I just have not looked all that hard.
>
>>
>> What do you think?  I realize these boards are new (says Beaglebone Blue
>> Rev A2 on back) but I hope there isn't some sort of defect with them.  I
>> used a DMM to verify that the push buttons are shorted when depressed.
>>
>> Anything obvious I'm missing?
>>
>
> I do not think so. About the only thing I can think of is that you could
> hook up a 3v3 logic USB to UART module / cable to see if uboot gives you
> any additional information as to what's happening. I'd probably contact the
> reseller you purchased this from however, and look into getting an RMA.
> Because if everything is as you say( no left out details ), it sounds like
> a potentially defective board. Which I've yet to see a defective beaglebone
> black, or green to date, and I've handled quite a few greens( 50 +).
>
> I'm considering buying one myself just so I can help others troubleshoot
> the board once in a while. But that may / may not happen.
>
>
>

-- 
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/CALHSORrdAnSYqcgoupZKGG_OcxDmAAHF2PPO1bpR0%3DY5Yg%2Bxow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to