[beagleboard] Angstrom image is not booting to BBB

[chirag panchal]

 Hello, 
  I download the latest Angstrom image file for BBB 
  then by using *win32disk imager*, I write that image file into my 
microSDcard.
  then I put microSD card into microSDcard slot of Beagle Bone 
Black. and *press the boot button*, then* still holding that boot button, I 
apply power supply*. 
  But *No user LEDs are blinking*. so many times I have done this 
procedure for a long time. But nothing happend with LED.
 
*Anybody can please help me*
*Thanks in advance.*

-- 
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] not flashing the eMMC (not blinking 4 user leds) problem

[chirag panchal]

Hello, 
  I download the Android image file for BBB from link: 
http://icculus.org/~hendersa/BBB_JB_Android_3_8_13.img.bz2
  then by using *win32disk imager*, I write that image file into my 
microSDcard.
  then I put microSD card into microSDcard slot of Beagle Bone 
Black. and *press the boot button*, then* still holding that boot button, I 
apply power supply*. 
  But *No user LEDs are blinking*. so many times I have done this 
procedure for a long time. But nothing happend with LED.
 
*Anybody can please help me*
*Thanks in advance.*

-- 
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] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Satz Klauer]

On Mon, Apr 14, 2014 at 4:22 PM, Gerald Coley  wrote:
>  If anyone wants to take my place on dealing with my frustration on this
> side of the issue, I will gladly let them. Any takers?

Then let's bring up the old question: why not offering a higher priced
variant of BBB that can be manufactured in higher numbers? I'd be
willing to pay up to US$ 80 for a BBB that is REALLY available.

You of course could still offer the low-cost BBBs for the intended
market in parallel - with current availability.

-- 
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] High(er) level language for PRU programming available.

[Jason Kridner]

On Monday, April 14, 2014, William Hermans  wrote:

> Nice job John, although I have to admit I have never heard of Forth( and
> have been programming since the early 90's ). Nice to learn something new,
> and I will have to give the Language a look-see to see if I like it.
>
> Jason, if you're paying attention I would also like a copy of the C
> compiler. I am based in the US, and do have an account on TI.com.
>

A direct email with "PRU Compiler" in the subject is easiest for me to
track.


>
>
> On Mon, Apr 14, 2014 at 2:23 PM, Sungjin Chun 
> 
> > wrote:
>
>> I also am interested in C compiler for PRU.
>> Can you let me know how to contact Jason Kridner?
>>
>> Sent from my iPhone
>>
>> > On Apr 15, 2014, at 5:39 AM, Charles Steinkuehler <
>> char...@steinkuehler.net>
>> wrote:
>> >
>> >> On 4/14/2014 3:34 PM, John Silvia wrote:
>> >>
>> >> I've implemented a forth language for the PRU to facilitate one of my
>> own
>> >> projects.  It is available for others to use on github in hopes that
>> >> someone may find it useful.
>> >>
>> >> https://github.com/biocode3D/prufh
>> >
>> > You are my hero!  I love Forth and figured the PRU would be perfect for
>> > a small Forth environment!  :)
>> >
>> >> Yes, of course, a C compiler would be useful to more people; but I'm
>> not
>> >> capable of writing a C compiler in ~500 lines of perl ;-)
>> >
>> > ...and there's already a C compiler available.  You just have to e-mail
>> > Jason Kridner and ask to get the "beta" copy since it hasn't been
>> > officially released for some reason.
>> >
>> > --
>> > Charles Steinkuehler
>> > char...@steinkuehler.net
>> >
>> > --
>> > 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.
>>
>> --
>> 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.
>>
>
>  --
> 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.
>

-- 
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] High(er) level language for PRU programming available.

[Jason Kridner]

On Monday, April 14, 2014, Sungjin Chun  wrote:

> I also am interested in C compiler for PRU.
> Can you let me know how to contact Jason Kridner?


Really surprised you haven't seen my email around here? :-)


>
> Sent from my iPhone
>
> > On Apr 15, 2014, at 5:39 AM, Charles Steinkuehler <
> char...@steinkuehler.net > wrote:
> >
> >> On 4/14/2014 3:34 PM, John Silvia wrote:
> >>
> >> I've implemented a forth language for the PRU to facilitate one of my
> own
> >> projects.  It is available for others to use on github in hopes that
> >> someone may find it useful.
> >>
> >> https://github.com/biocode3D/prufh
> >
> > You are my hero!  I love Forth and figured the PRU would be perfect for
> > a small Forth environment!  :)
> >
> >> Yes, of course, a C compiler would be useful to more people; but I'm not
> >> capable of writing a C compiler in ~500 lines of perl ;-)
> >
> > ...and there's already a C compiler available.  You just have to e-mail
> > Jason Kridner and ask to get the "beta" copy since it hasn't been
> > officially released for some reason.
> >
> > --
> > Charles Steinkuehler
> > char...@steinkuehler.net 
> >
> > --
> > 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.
>
> --
> 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.
>

-- 
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] Re: Using i2c channel without recompiling the kernel

[Muhamed Noufal]

But I am using BeagleBoard. Let me see if it works for Beagle Board also.
 On Apr 14, 2014 8:34 PM, "Joshua Datko"  wrote:

>
>
>
> The bus names are a bit confusing, but the BBB's i2c-2, on pins P19/20,
> can be sometimes labeled i2c-1 in Linux.
>
> Anyway, this usually does the trick to get the third i2c bus:
>
> root@arm:~# echo BB-I2C1 > /sys/devices/bone_capemgr.8/slots
> root@arm:~# ls -l /sys/bus/i2c/devices/i2c-*
> lrwxrwxrwx 1 root root 0 Nov  3 21:49 /sys/bus/i2c/devices/i2c-0 ->
> ../../../devices/ocp.2/44e0b000.i2c/i2c-0
> lrwxrwxrwx 1 root root 0 Nov  3 21:49 /sys/bus/i2c/devices/i2c-1 ->
> ../../../devices/ocp.2/4819c000.i2c/i2c-1
> lrwxrwxrwx 1 root root 0 Nov  3 21:50 /sys/bus/i2c/devices/i2c-2 ->
> ../../../devices/ocp.2/4802a000.i2c/i2c-2
>
> I did a blog post about it here: http://datko.net/2013/11/03/bbb_i2c/
>
> Josh
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/sIKh84qfOiM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] Problems setting up Cross Compiler tool chain in Debian (perhaps Apt-Get issues)

[treedeegraphics]

Hi:

I recently installed Debian Wheezy 7.4.0  on by x86 laptop to do BeagleBone 
Black development. But I am having an impossible time to install the ARMEL 
and ARMHF compiler tool chains to cross compile for the BeagleBone Black.  
I think Aptitude got screwed up some how on the machine specifically for 
ARMEL and ARMHF... I followed the instructions on various sites and I still 
can not get it to download and install.HELP  :-)


I tried 2 methods:  1 to locate them on DVD-ROM discs (can not be found), 
2. to use the Emdebian install.   For Emdebian, If I do an apt-get update  
(with the Emdebian installed in source.list.d )  it complains it can not 
find  ARMEL / ARMHF stuff and says it will be ignored.  Also I read that 
the ARM tool chain is supposed to be right in the Debian distro DVDs, but 
no matter what I do I can not seem to get APT to find it on there.

Can someone help me to  solve my APT issues  and/or clean up my   APT   
sources.list file so it is correct so I can install these tools ?


When I installed Debian, I had to do an EXPERT install because the machine 
I am using is a multi-boot machine with various partitions. However, when 
it came time to install the software in EXPERT mode, Debian would not let 
me eject the DVD discs and scan the various other discs (#2, #3, update #1, 
and update #2).  But the install continued fine anyway and completed.  
However, now for some reason I can not get the ARM cross compilers 
installed, nor can I get APT-GET to locate them on the DVD discs.

Thanks in advance for your help.
:-)


-- 
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] Announcement: Power Cape (UPS)

[Eric Fort]

If I remember from previous discussion on this list, the issue with using
the onboard RTC was keeping it powered and running with everything else
powered down


On Mon, Apr 14, 2014 at 3:32 PM, Ron B.  wrote:

> True, I could do it with another part fairly easily.  I was trying to keep
> down the parts count (and cost) since the micro already has a 32kHz clock
> and keeps time.  My pick and place machine (me) gets grumpy if the board
> has too many parts.  ;-)
>
> I'll add a supported I2C RTC device to the wish list for the A1 boards.
>
> -Ron
>
>
> On Monday, April 14, 2014 5:10:52 PM UTC-5, Eric wrote:
>
>> Ron,
>>
>> As for adding a RTC to the board all the drivers for that are already in
>> the kernel.  Just add one of the following RTC chips: DS3232 (high
>> accuracy), DS1338C, DS1339C, or DS1374 all of which can attach to the same
>> i2c pins as your cape EEPROM.  Given the pcb cad files I'm guessing it
>> would take 5-10 minutes tops to add a RTC to your board and getting the
>> software to use it another hour tops.
>>
>> Eric
>>
>>
>> On Mon, Apr 14, 2014 at 8:54 AM, Ron B.  wrote:
>>
>>> Hi Jason,
>>>
>>> Thank you for the comments (and the order!).  The first batch of boards
>>> was very small due to parts availability.  Still waiting on a zener to come
>>> back in stock (current estimate is beginning of May).
>>>
>>> The cape firmware does currently allow for a timeout to be set that will
>>> power the BB back on.  The cape also monitors 3V3 so it knows when the BB
>>> has powered down and then will then cut 5V (and reset the timeout if you've
>>> set one).  It is my intention to add a RTC to the firmware but I really
>>> need to create a kernel driver for it to provide the proper RTC interface
>>> and so that everything else is accessible through sysfs.
>>>
>>> I have thought about moving the components to the "bottom" of the board
>>> to make the top "slick".  I'd probably have to scoot a component or two
>>> around but that should be completely doable.  These lithium battery packs
>>> get pretty small.  My final prototype now lives in a Logic Supply case
>>> which I think is a pretty nice setup.  Without the stacking connectors, the
>>> cover just needs to be raised one position.  Photo 
>>> here
>>> .
>>>
>>> The reason that I put the JST connector onto the cape is because the
>>> lithium packs from AdaFruit and SparkFun seem to all have them
>>> pre-installed.  The battery in the pic is from AdaFruit and is 1200mAh.
>>> That runs an idling BBB for nearly 3 hours!
>>>
>>> -Ron
>>>
>>> On Monday, April 14, 2014 8:49:37 AM UTC-5, Jason Kridner wrote:

 On Fri, Apr 4, 2014 at 11:09 AM, Ron B.  wrote:
 > Hello fellow enthusiasts,
 >
 > Please check out my Power Cape and let me know what you think.  Yes,
 they
 > are for sale but I would also value your feedback.

 I seem to have bought the last one in stock with stacking headers.

 Be sure to register your capes on http://beaglebonecapes.com and
 http://beagleboard.org/project.

 My "dream" power cape would include an RTC and the ability to set
 alarms to wake-up and/or power-up the board. I also dream of a power
 cape that would allow the battery and cape to still fit in an Altoids
 tin, sandwiching the battery between the boards and eliminating any
 connectors components that would extrude beyond those boundaries.
 Then, insulating the tin with a non-conductive material would allow
 for containing a running Bone and I'd just make a cut-out for the USB
 connectors.

 That said, I really like what you've created, which is why I bought
 one. :-)

 Do you have a recommended battery supplier?

 >
 > Thanks,
 > -Ron
 >
 > --
 > 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.
 > For more options, visit https://groups.google.com/d/optout.

>>>  --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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] High(er) level language for PRU programming available.

[lee]

Forth is awesome. Last time I had a paying gig in Forth was about 1985, I 
think. It was to control a big lighted display board (and garage heater!). 
So it was basically a 160 x 32 monochrome graphics editor with fonts and 
wipe effects, done on an Apple II (8-bit 6502 processor, 1 MHz, 32k of 
RAM). No other language squeezes into tight spots like that.


On Monday, April 14, 2014 3:15:37 PM UTC-7, William Hermans wrote:
>
> Nice job John, although I have to admit I have never heard of Forth( and 
> have been programming since the early 90's ). Nice to learn something new, 
> and I will have to give the Language a look-see to see if I like it. 
>
> Jason, if you're paying attention I would also like a copy of the C 
> compiler. I am based in the US, and do have an account on TI.com.
>
>
> On Mon, Apr 14, 2014 at 2:23 PM, Sungjin Chun 
> > wrote:
>
>> I also am interested in C compiler for PRU.
>> Can you let me know how to contact Jason Kridner?
>>
>> Sent from my iPhone
>>
>> > On Apr 15, 2014, at 5:39 AM, Charles Steinkuehler <
>> cha...@steinkuehler.net > wrote:
>> >
>> >> On 4/14/2014 3:34 PM, John Silvia wrote:
>> >>
>> >> I've implemented a forth language for the PRU to facilitate one of my 
>> own
>> >> projects.  It is available for others to use on github in hopes that
>> >> someone may find it useful.
>> >>
>> >> https://github.com/biocode3D/prufh
>> >
>> > You are my hero!  I love Forth and figured the PRU would be perfect for
>> > a small Forth environment!  :)
>> >
>> >> Yes, of course, a C compiler would be useful to more people; but I'm 
>> not
>> >> capable of writing a C compiler in ~500 lines of perl ;-)
>> >
>> > ...and there's already a C compiler available.  You just have to e-mail
>> > Jason Kridner and ask to get the "beta" copy since it hasn't been
>> > officially released for some reason.
>> >
>> > --
>> > Charles Steinkuehler
>> > cha...@steinkuehler.net 
>> >
>> > --
>> > 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 .
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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] HDMI to VGA, on boot the board displays its logo, but then ceases to display anything. Please Help

[Scott Force]

I don't know about the VGA adapters but ...

I am currently powering my BBB via a USB hub with a charging port. Just use
a USB to DC adapter cable. It has to be a charging port though to get the
extra juice than a regular USB port.

Here is what I am currently using;

http://www.amazon.ca/HooToo%C2%AE-HT-UH003-including-Fast-Charging-SuperSpeed/dp/B00CHH0JF0/ref=sr_1_1?ie=UTF8&qid=1385336981&sr=8-1&keywords=HT-UH003

http://www.newegg.ca/Product/Product.aspx?Item=N82E16812200699



On 13 April 2014 15:11,  wrote:

> that seems to be exactly my problem too.
> unfortunately in austria it is impossible to get a (micro)hdmi to vga
> adapter with its own power supply.
> for some strange reason ebay, amazon and other stores won't ship them to
> austria. :/
> is there any way around that?
> I'm powering my bbb with usb. i read somewhere that the bbb gets more
> power from a power supply unit than from usb.
> could that give the bbb enough power to also power the adapter? or what
> happened it i powered the bbb with a power supply unit and with usb at the
> same time? could that cause a short circuit or something or would it maybe
> work?
> I'm sure I could get a 5v power supply somewhere in austria but before i
> spend more money i'd like to know if it will make a difference.
>
> Am Samstag, 5. April 2014 18:05:45 UTC+2 schrieb bert@gmail.com:
>
>> Hay
>>
>> I think your problem is the 5Volt suply of the HDMI to VGA converter.
>> Normally it should get 5V from the HDMI plug but as I understood the
>> Beagleboard does not supply the 5 Volt at pin 18 of the plug, therefore you
>> should have a HDMI converter with his own power supply.
>>
>>  --
> 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.
>

-- 
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] Running BeagleBone without MicroSD: Need quick reply

[Scott Force]

You can run the Angstrom distribution that came with your BBB via the eMMC.
But there is no way to update it or run another OS without a microSD.

If you have a smartphone or other device with a microSD card then you could
always temporarily borrow it. Just backup you stuff first. :)



On 14 April 2014 03:22, Yiling Cao  wrote:

> maybe not.
>
>
> On Sat, Apr 12, 2014 at 7:37 PM, Anon123  wrote:
>
>> I forgot to buy a microSD
>>
>> Can and how do i run angstrom without MicroSD? I have microUSB.
>>
>> --
>> 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.
>>
>
>  --
> 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.
>

-- 
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] Announcement: Power Cape (UPS)

[Ron B.]

True, I could do it with another part fairly easily.  I was trying to keep 
down the parts count (and cost) since the micro already has a 32kHz clock 
and keeps time.  My pick and place machine (me) gets grumpy if the board 
has too many parts.  ;-)

I'll add a supported I2C RTC device to the wish list for the A1 boards.

-Ron

On Monday, April 14, 2014 5:10:52 PM UTC-5, Eric wrote:
>
> Ron,
>
> As for adding a RTC to the board all the drivers for that are already in 
> the kernel.  Just add one of the following RTC chips: DS3232 (high 
> accuracy), DS1338C, DS1339C, or DS1374 all of which can attach to the same 
> i2c pins as your cape EEPROM.  Given the pcb cad files I'm guessing it 
> would take 5-10 minutes tops to add a RTC to your board and getting the 
> software to use it another hour tops.
>
> Eric
>
>
> On Mon, Apr 14, 2014 at 8:54 AM, Ron B. 
> > wrote:
>
>> Hi Jason, 
>>
>> Thank you for the comments (and the order!).  The first batch of boards 
>> was very small due to parts availability.  Still waiting on a zener to come 
>> back in stock (current estimate is beginning of May).
>>
>> The cape firmware does currently allow for a timeout to be set that will 
>> power the BB back on.  The cape also monitors 3V3 so it knows when the BB 
>> has powered down and then will then cut 5V (and reset the timeout if you've 
>> set one).  It is my intention to add a RTC to the firmware but I really 
>> need to create a kernel driver for it to provide the proper RTC interface 
>> and so that everything else is accessible through sysfs.
>>
>> I have thought about moving the components to the "bottom" of the board 
>> to make the top "slick".  I'd probably have to scoot a component or two 
>> around but that should be completely doable.  These lithium battery packs 
>> get pretty small.  My final prototype now lives in a Logic Supply case 
>> which I think is a pretty nice setup.  Without the stacking connectors, the 
>> cover just needs to be raised one position.  Photo 
>> here
>> .
>>
>> The reason that I put the JST connector onto the cape is because the 
>> lithium packs from AdaFruit and SparkFun seem to all have them 
>> pre-installed.  The battery in the pic is from AdaFruit and is 1200mAh.  
>> That runs an idling BBB for nearly 3 hours!
>>
>> -Ron
>>
>> On Monday, April 14, 2014 8:49:37 AM UTC-5, Jason Kridner wrote:
>>>
>>> On Fri, Apr 4, 2014 at 11:09 AM, Ron B.  wrote: 
>>> > Hello fellow enthusiasts, 
>>> > 
>>> > Please check out my Power Cape and let me know what you think.  Yes, 
>>> they 
>>> > are for sale but I would also value your feedback. 
>>>
>>> I seem to have bought the last one in stock with stacking headers. 
>>>
>>> Be sure to register your capes on http://beaglebonecapes.com and 
>>> http://beagleboard.org/project. 
>>>
>>> My "dream" power cape would include an RTC and the ability to set 
>>> alarms to wake-up and/or power-up the board. I also dream of a power 
>>> cape that would allow the battery and cape to still fit in an Altoids 
>>> tin, sandwiching the battery between the boards and eliminating any 
>>> connectors components that would extrude beyond those boundaries. 
>>> Then, insulating the tin with a non-conductive material would allow 
>>> for containing a running Bone and I'd just make a cut-out for the USB 
>>> connectors. 
>>>
>>> That said, I really like what you've created, which is why I bought one. 
>>> :-) 
>>>
>>> Do you have a recommended battery supplier? 
>>>
>>> > 
>>> > Thanks, 
>>> > -Ron 
>>> > 
>>> > -- 
>>> > 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. 
>>> > For more options, visit https://groups.google.com/d/optout. 
>>>
>>  -- 
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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] BBIOConfig -> BB universal IO UI testing release

[William Hermans]

Excellent, thanks very much again.


On Mon, Apr 14, 2014 at 12:43 PM, Charles Steinkuehler <
char...@steinkuehler.net> wrote:

> On 4/14/2014 12:48 PM, William Hermans wrote:
> > Awesome Charles, and Alexander ! will definitely check it out. Charles,
> is
> > this kernel neutral ?
>
> This is mostly kernel neutral.  The basic idea works for any ARM system
> with device tree and pin multiplexing.
>
> When migrating from the BeagleBone 3.8 kernel to something newer there
> are a few changes to the device tree names and entries that will need to
> be accommodated.  For instance I think the "off-by-one" numbering for
> GPIO banks was fixed in recent kernels.  That means every pin in the
> universal overlay will need to be updated, but it's not exactly a
> complex change.  :)
>
> --
> Charles Steinkuehler
> char...@steinkuehler.net
>
> --
> 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.
>

-- 
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] Re: Bad Linux ARM zImage magic

[William Hermans]

Sorry >NFS <


On Mon, Apr 14, 2014 at 3:24 PM, William Hermans  wrote:

> macarr, just so you know I have been using Debian for a good while and it
> took me 2-3 tries to get his steps right myself. At the time the
> instructions were a bit less clear, but the fault was my own ( I was a bit
> rusty with some of the steps / commands ).
>
> I am currently rebuilding my own kernel to the latest from scratch, and so
> far they seem to work perfectly ( I am about half way through, e.g. I've
> downloaded all the tools and have compiled the kernel).
>
> @Robert, I should be able to do the same steps I took back in December to
> get a working TFTP/NSF boot/root with the latest kernel ?
>
> What about 3.13 ? I remember you saying something about it being a
> "different animal" some months ago.
>
> I would ask on your comments pages for your site, but . . . Yeah editor
> wont stop loading.
>
>
> On Mon, Apr 14, 2014 at 1:15 PM,  wrote:
>
>> Yes Robert,
>>
>> You are correct on all counts. I was unaware of the
>> http://eewiki.net/display/linuxonarm/BeagleBone+Black.
>>  I performed a google search and found the first site I mentioned.
>>
>> Being "new" can be a painful process. Not working on a staff with others
>> to learn from is even more painful.
>>
>> The biggest obstacle is that "you don't know what you don't know".
>>
>> Again, I thank you for your efforts. I will be persistent.
>>
>> Respectfully,
>>
>>  --
>> 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.
>>
>
>

-- 
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] Re: Bad Linux ARM zImage magic

[William Hermans]

macarr, just so you know I have been using Debian for a good while and it
took me 2-3 tries to get his steps right myself. At the time the
instructions were a bit less clear, but the fault was my own ( I was a bit
rusty with some of the steps / commands ).

I am currently rebuilding my own kernel to the latest from scratch, and so
far they seem to work perfectly ( I am about half way through, e.g. I've
downloaded all the tools and have compiled the kernel).

@Robert, I should be able to do the same steps I took back in December to
get a working TFTP/NSF boot/root with the latest kernel ?

What about 3.13 ? I remember you saying something about it being a
"different animal" some months ago.

I would ask on your comments pages for your site, but . . . Yeah editor
wont stop loading.


On Mon, Apr 14, 2014 at 1:15 PM,  wrote:

> Yes Robert,
>
> You are correct on all counts. I was unaware of the
> http://eewiki.net/display/linuxonarm/BeagleBone+Black.
>  I performed a google search and found the first site I mentioned.
>
> Being "new" can be a painful process. Not working on a staff with others
> to learn from is even more painful.
>
> The biggest obstacle is that "you don't know what you don't know".
>
> Again, I thank you for your efforts. I will be persistent.
>
> Respectfully,
>
>  --
> 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.
>

-- 
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] High(er) level language for PRU programming available.

[William Hermans]

Nice job John, although I have to admit I have never heard of Forth( and
have been programming since the early 90's ). Nice to learn something new,
and I will have to give the Language a look-see to see if I like it.

Jason, if you're paying attention I would also like a copy of the C
compiler. I am based in the US, and do have an account on TI.com.


On Mon, Apr 14, 2014 at 2:23 PM, Sungjin Chun  wrote:

> I also am interested in C compiler for PRU.
> Can you let me know how to contact Jason Kridner?
>
> Sent from my iPhone
>
> > On Apr 15, 2014, at 5:39 AM, Charles Steinkuehler <
> char...@steinkuehler.net> wrote:
> >
> >> On 4/14/2014 3:34 PM, John Silvia wrote:
> >>
> >> I've implemented a forth language for the PRU to facilitate one of my
> own
> >> projects.  It is available for others to use on github in hopes that
> >> someone may find it useful.
> >>
> >> https://github.com/biocode3D/prufh
> >
> > You are my hero!  I love Forth and figured the PRU would be perfect for
> > a small Forth environment!  :)
> >
> >> Yes, of course, a C compiler would be useful to more people; but I'm not
> >> capable of writing a C compiler in ~500 lines of perl ;-)
> >
> > ...and there's already a C compiler available.  You just have to e-mail
> > Jason Kridner and ask to get the "beta" copy since it hasn't been
> > officially released for some reason.
> >
> > --
> > Charles Steinkuehler
> > char...@steinkuehler.net
> >
> > --
> > 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.
>
> --
> 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.
>

-- 
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] Announcement: Power Cape (UPS)

[Eric Fort]

Ron,

As for adding a RTC to the board all the drivers for that are already in
the kernel.  Just add one of the following RTC chips: DS3232 (high
accuracy), DS1338C, DS1339C, or DS1374 all of which can attach to the same
i2c pins as your cape EEPROM.  Given the pcb cad files I'm guessing it
would take 5-10 minutes tops to add a RTC to your board and getting the
software to use it another hour tops.

Eric


On Mon, Apr 14, 2014 at 8:54 AM, Ron B.  wrote:

> Hi Jason,
>
> Thank you for the comments (and the order!).  The first batch of boards
> was very small due to parts availability.  Still waiting on a zener to come
> back in stock (current estimate is beginning of May).
>
> The cape firmware does currently allow for a timeout to be set that will
> power the BB back on.  The cape also monitors 3V3 so it knows when the BB
> has powered down and then will then cut 5V (and reset the timeout if you've
> set one).  It is my intention to add a RTC to the firmware but I really
> need to create a kernel driver for it to provide the proper RTC interface
> and so that everything else is accessible through sysfs.
>
> I have thought about moving the components to the "bottom" of the board to
> make the top "slick".  I'd probably have to scoot a component or two around
> but that should be completely doable.  These lithium battery packs get
> pretty small.  My final prototype now lives in a Logic Supply case which I
> think is a pretty nice setup.  Without the stacking connectors, the cover
> just needs to be raised one position.  Photo 
> here
> .
>
> The reason that I put the JST connector onto the cape is because the
> lithium packs from AdaFruit and SparkFun seem to all have them
> pre-installed.  The battery in the pic is from AdaFruit and is 1200mAh.
> That runs an idling BBB for nearly 3 hours!
>
> -Ron
>
> On Monday, April 14, 2014 8:49:37 AM UTC-5, Jason Kridner wrote:
>>
>> On Fri, Apr 4, 2014 at 11:09 AM, Ron B.  wrote:
>> > Hello fellow enthusiasts,
>> >
>> > Please check out my Power Cape and let me know what you think.  Yes,
>> they
>> > are for sale but I would also value your feedback.
>>
>> I seem to have bought the last one in stock with stacking headers.
>>
>> Be sure to register your capes on http://beaglebonecapes.com and
>> http://beagleboard.org/project.
>>
>> My "dream" power cape would include an RTC and the ability to set
>> alarms to wake-up and/or power-up the board. I also dream of a power
>> cape that would allow the battery and cape to still fit in an Altoids
>> tin, sandwiching the battery between the boards and eliminating any
>> connectors components that would extrude beyond those boundaries.
>> Then, insulating the tin with a non-conductive material would allow
>> for containing a running Bone and I'd just make a cut-out for the USB
>> connectors.
>>
>> That said, I really like what you've created, which is why I bought one.
>> :-)
>>
>> Do you have a recommended battery supplier?
>>
>> >
>> > Thanks,
>> > -Ron
>> >
>> > --
>> > 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.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>  --
> 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.
>

-- 
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] Mounting as drive on Windows

[William Hermans]

Device manager -> view -> show hidden devices.

Anyway, if you need to work with Windows, I suggest you find a good read,
and start learning. Its an OS, and is documented just as well as Linux,
perhaps even better. Google most of the time is sufficient.


On Mon, Apr 14, 2014 at 2:46 PM,  wrote:

> I appreciate all your help, but I'm just not seeing what you see in
> devmgmt.msc, even with your SHOW_NONPRESENT hack, and with "show hidden
> devices" checked in the app itself. Nor do I see anything in the network
> connections. I don't know if Windows7 is the difference, or 64-bit is the
> difference.
>
> Coming from the other side, when I eliminate g_multi and just run
> g_mass_storage, all is weil. No driver needed, it just comes up working
> with no problem. That will solve my needs for now, but I'm still curious
> why the drivers don't seem to work on my laptop.
>
>  --
> 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.
>

-- 
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] Mounting as drive on Windows

[lee]

I appreciate all your help, but I'm just not seeing what you see in 
devmgmt.msc, even with your SHOW_NONPRESENT hack, and with "show hidden 
devices" checked in the app itself. Nor do I see anything in the network 
connections. I don't know if Windows7 is the difference, or 64-bit is the 
difference.

Coming from the other side, when I eliminate g_multi and just run 
g_mass_storage, all is weil. No driver needed, it just comes up working 
with no problem. That will solve my needs for now, but I'm still curious 
why the drivers don't seem to work on my laptop.

-- 
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] High(er) level language for PRU programming available.

[Sungjin Chun]

I also am interested in C compiler for PRU. 
Can you let me know how to contact Jason Kridner?

Sent from my iPhone

> On Apr 15, 2014, at 5:39 AM, Charles Steinkuehler  
> wrote:
> 
>> On 4/14/2014 3:34 PM, John Silvia wrote:
>> 
>> I've implemented a forth language for the PRU to facilitate one of my own 
>> projects.  It is available for others to use on github in hopes that 
>> someone may find it useful.
>> 
>> https://github.com/biocode3D/prufh
> 
> You are my hero!  I love Forth and figured the PRU would be perfect for
> a small Forth environment!  :)
> 
>> Yes, of course, a C compiler would be useful to more people; but I'm not 
>> capable of writing a C compiler in ~500 lines of perl ;-)
> 
> ...and there's already a C compiler available.  You just have to e-mail
> Jason Kridner and ask to get the "beta" copy since it hasn't been
> officially released for some reason.
> 
> -- 
> Charles Steinkuehler
> char...@steinkuehler.net
> 
> -- 
> 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.

-- 
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] High(er) level language for PRU programming available.

[Charles Steinkuehler]

On 4/14/2014 3:34 PM, John Silvia wrote:
> 
> I've implemented a forth language for the PRU to facilitate one of my own 
> projects.  It is available for others to use on github in hopes that 
> someone may find it useful.
> 
> https://github.com/biocode3D/prufh

You are my hero!  I love Forth and figured the PRU would be perfect for
a small Forth environment!  :)

> Yes, of course, a C compiler would be useful to more people; but I'm not 
> capable of writing a C compiler in ~500 lines of perl ;-)

...and there's already a C compiler available.  You just have to e-mail
Jason Kridner and ask to get the "beta" copy since it hasn't been
officially released for some reason.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] High(er) level language for PRU programming available.

[John Silvia]

I've implemented a forth language for the PRU to facilitate one of my own 
projects.  It is available for others to use on github in hopes that 
someone may find it useful.

https://github.com/biocode3D/prufh

Prufh will allow you to write code for the PRU in 
Forth. 
 This has the advantage of easier coding and debugging.  Because of the way 
it uses data memory (and the nature of Forth) it also may allow you to 
write larger programs than would be feasible in assembly language.  The 
potential disadvantages are that code will usually be somewhat slower and 
it is more difficult to calculate execution times.

Depending on how you need to use PRU, it may well be easier learn the 
basics of the Forth language in order to use prufh than to write everything 
in assembly.  But if there is anyone out there that already knows forth and 
needs to use the PRU subsystem, I'm sure you'll like it.

Yes, of course, a C compiler would be useful to more people; but I'm not 
capable of writing a C compiler in ~500 lines of perl ;-)

-- 
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] Creating a boot sd from an img file

[Robert Nelson]

On Mon, Apr 14, 2014 at 3:18 PM, JBodine  wrote:
> Ok, I don't want to beat this to death but what about the other 10gb?

"Use gparted to expand the 2nd 3.7GB root partition."... to the full
disk size...

Regards,

-- 
Robert Nelson
http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Creating a boot sd from an img file

[JBodine]

Ok, I don't want to beat this to death but what about the other 10gb?

Thanks

On Monday, April 14, 2014 12:10:49 PM UTC-7, RobertCNelson wrote:

> On Mon, Apr 14, 2014 at 2:09 PM, JBodine > 
> wrote: 
> > Thanks for the reply.   When I boot the BBB with one of these cards I've 
> > created, Angstrom only sees a single 70mb partition, if it's just 
> windows 
> > having the problem, shouldn't my BBB show the entire 16gb partition? 
>
> It'll see a 70mb boot partition "and" a 3.7GB root partition. Use 
> gparted to expand the 2nd 3.7GB root partition. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Bad Linux ARM zImage magic

[macarr]

Yes Robert,

You are correct on all counts. I was unaware of the 
http://eewiki.net/display/linuxonarm/BeagleBone+Black.
 I performed a google search and found the first site I mentioned.

Being "new" can be a painful process. Not working on a staff with others to 
learn from is even more painful.

The biggest obstacle is that "you don't know what you don't know". 

Again, I thank you for your efforts. I will be persistent.

Respectfully,

-- 
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] Where did /sys/bus/iio/devices/iio\:device0/in_voltage[0-3]_raw go in saucy 3.13.X kernels?

[John Amidon]

Thanks.  I was able to use the device tree compiler to make the analog inputs 
available.  I started with:

ubuntu@arm:~$ ls /sys/bus/iio/devices/iio\:device0
buffer  in_voltage4_raw  in_voltage6_raw  power  subsystem
dev in_voltage5_raw  name scan_elements  uevent

The commands I used to add analog inputs 0-3 are:

$ sudo apt-get install device-tree-compiler
$ sudo dtc -I dtb -O dts /boot/uboot/dtbs/am335x-boneblack.dtb > 
am335x-boneblack.dts

Change the section:

 adc {
  #io-channel-cells = <0x1>;
  compatible = "ti,am3359-adc";
  ti,adc-channels = <0x4 0x5 0x6>;
 };

to

 adc {
  #io-channel-cells = <0x1>;
  compatible = "ti,am3359-adc";
  ti,adc-channels = <0x0 0x1 0x2 0x3 0x4 0x5 0x6>;
 };

then recompile, install and reboot:

$ dtc -O dtb -o am335x-boneblack.dtb am335x-boneblack.dts
$ sudo cp am335x-boneblack.dtb /boot/uboot/dtbs

Once rebooted, the devices show up:

ubuntu@arm:~$ ls /sys/bus/iio/devices/iio\:device0
buffer  in_voltage0_raw  in_voltage2_raw  in_voltage4_raw  in_voltage6_raw  
power  subsystem
dev in_voltage1_raw  in_voltage3_raw  in_voltage5_raw  name 
scan_elements  uevent
ubuntu@arm:~$ 

-- jda

-- 
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] BBIOConfig -> BB universal IO UI testing release

[Charles Steinkuehler]

On 4/14/2014 12:48 PM, William Hermans wrote:
> Awesome Charles, and Alexander ! will definitely check it out. Charles, is
> this kernel neutral ?

This is mostly kernel neutral.  The basic idea works for any ARM system
with device tree and pin multiplexing.

When migrating from the BeagleBone 3.8 kernel to something newer there
are a few changes to the device tree names and entries that will need to
be accommodated.  For instance I think the "off-by-one" numbering for
GPIO banks was fixed in recent kernels.  That means every pin in the
universal overlay will need to be updated, but it's not exactly a
complex change.  :)

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] Setting I/O's

[Guy Grotke]

Of course I would not assume that every I/O pins starts in tristate, but he 
said earlier:
>On the PCB I designed I use the BBB for setting some pumps and valves.
>When the system starts up the first seconds the IO pins are not logic 1 or 0.
That sounds to me like the particular pins he used do start in tristate.  

Reading the datasheet is always the first thing to do, but once you confirm 
that an I/O pin is tristated then what would be wrong about using a weak pullup 
or pulldown resistor to keep those pumps and valves from doing some damage 
before you get the I/Os programmed?


From: Gerald Coley 
Sent: Monday, April 14, 2014 11:11 AM
To: beagleboard@googlegroups.com 
Subject: Re: [beagleboard] Setting I/O's

That is not correct. Please. Read the datasheet. 

Gerald



On Mon, Apr 14, 2014 at 1:04 PM, Guy Grotke  wrote:

  All your programmable I/O pins are going to startup in tristate mode.  That 
means you can just add a weak pullup or pulldown resistor (EG. 10K) to each 
pin’s circuit to make your external devices behave properly until your software 
programs the pins.

  From: maartenrik...@gmail.com 
  Sent: Monday, April 14, 2014 8:09 AM
  To: beagleboard@googlegroups.com 
  Subject: Re: [beagleboard] Setting I/O's

  Dear Gerald,

  Isn't it possible to set the IO's in the U-boot? 
  before the kernel is started.
  This would be fast enough.

  Regards,


  Maarten

  Op maandag 14 april 2014 16:40:16 UTC+2 schreef Gerald: 
Read the datasheet for the default state of each pin on power up. 

http://www.ti.com/product/am3358


These cannot be changed. Once the SW is loaded, it can set the pins to 
whatever function it supports.

Gerald




On Mon, Apr 14, 2014 at 9:37 AM,  wrote:

  Dear Reader,

  I have a question about the following problem.
  On the PCB I designed I use the BBB for setting some pumps and valves.
  When the system starts up the first seconds the IO pins are not logic 1 
or 0.
  Is it possible to set the GPIO's in U-boot before starting up the kernel 
and how can I do this?

  Thanks,

  Maarten


  -- 
  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.
  For more options, visit https://groups.google.com/d/optout.


  -- 
  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.

  -- 
  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.


-- 
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.

-- 
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] Flshing nanad of begle bone black am335x

[charudatta ingale]

board is successfully booting from sd card but board not booting from nand
i want to flash nand  want guidance




*// successfully boot from sd *

arch=arm
baudrate=115200
board=am335x
board_name=A335BNLT
board_rev=0A6A
bootargs_defaults=setenv bootargs console=${console} ${optargs}
bootcmd=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device 
${mmcdev};if run loadbootenv; then echo Loaded environment from ${bo;
bootdelay=1
bootenv=uEnv.txt
bootfile=uImage
console=ttyO0,115200n8
cpu=armv7
dfu_alt_info_emmc=rawemmc mmc 0 3751936
dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw mmc 100 
100;u-boot.img.raw mmc 300 3C0;u-boot.img fat 0 1;uEnv.txt fat 0 1
dfu_alt_info_nand=SPL part 0 1;SPL.backup1 part 0 2;SPL.backup2 part 0 
3;SPL.backup3 part 0 4;u-boot part 0 5;kernel part 0 7;rootfs part 0 8
ethact=cpsw
ethaddr=90:59:af:82:3d:9f
fdt_high=0x
fdtaddr=0x80F8
findfdt=if test $board_name = A335BONE; then setenv fdtfile 
am335x-bone.dtb; fi; if test $board_name = A33515BB; then setenv fdtfile 
am335x-evmi
importbootenv=echo Importing environment from mmc ...; env import -t 
$loadaddr $filesize
ip_method=none
kloadaddr=0x80007fc0
loadaddr=0x8020
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
loadramdisk=fatload mmc ${mmcdev} ${rdaddr} ramdisk.gz
loaduimage=ext2load mmc ${mmcdev}:2 ${kloadaddr} /boot/${bootfile}
loaduimagefat=fatload mmc ${mmcdev} ${kloadaddr} ${bootfile}
mmcargs=run bootargs_defaults;setenv bootargs ${bootargs} root=${mmcroot} 
rootfstype=${mmcrootfstype} ip=${ip_method}
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${kloadaddr}
mmcdev=0
mmcroot=/dev/mmcblk0p2 ro
mmcrootfstype=ext3 rootwait
mtdids=nand0=omap2-nand.0
mtdparts=mtdparts=omap2-nand.0:128k(SPL),128k(SPL.backup1),128k(SPL.backup2),128k(SPL.backup3),1920k(u-boot),128k(u-boot-env),5m(kernel),-(root)
nandargs=setenv bootargs console=${console} ${optargs} root=${nandroot} 
rootfstype=${nandrootfstype}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 
${nandsrcaddr} ${nandimgsize}; bootm ${loadaddr}
nandimgsize=0x50
nandroot=ubi0:rootfs rw ubi.mtd=7,2048
nandrootfstype=ubifs rootwait=1
nandsrcaddr=0x28
netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs 
nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp
netboot=echo Booting from network ...; setenv autoload no; dhcp; tftp 
${loadaddr} ${bootfile}; run netargs; bootm ${loadaddr}
nfsopts=nolock
ramargs=setenv bootargs console=${console} ${optargs} root=${ramroot} 
rootfstype=${ramrootfstype}
ramboot=echo Booting from ramdisk ...; run ramargs; bootm ${loadaddr}
ramroot=/dev/ram0 rw ramdisk_size=65536 initrd=${rdaddr},64M
ramrootfstype=ext2
rdaddr=0x8100
rootpath=/export/rootfs
soc=am33xx
spiargs=setenv bootargs console=${console} ${optargs} root=${spiroot} 
rootfstype=${spirootfstype}
spiboot=echo Booting from spi ...; run spiargs; sf probe ${spibusno}:0; sf 
read ${loadaddr} ${spisrcaddr} ${spiimgsize}; bootm ${loadaddr}
spibusno=0
spiimgsize=0x362000
spiroot=/dev/mtdblock4 rw
spirootfstype=jffs2
spisrcaddr=0xe
static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
stderr=serial
stdin=serial
stdout=serial
usbnet_devaddr=90:59:af:82:3d:9f
vendor=ti
ver=U-Boot 2013.01.01 (Jun 25 2013 - 16:42:52)


*// after booting from nand*


Welcome to minicom 2.5

OPTIONS: I18n 
Compiled on May  2 2011, 00:39:27.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys  
 
 
U-Boot# AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0 
syntax error 
U-Boot# 
U-Boot SPL 2013.10 (Nov 28 2013 - 06:36:11)
reading args
spl: error reading image args, err - -1
reading u-boot.img
reading u-boot.img


U-Boot 2013.10 (Nov 28 2013 - 06:36:11)

I2C:   ready
DRAM:  512 
MiB  
WARNING: Caches not 
enabled 
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 
1   
Net:   cpsw, 
usb_ether  
Hit any key to stop autoboot:  
0
mmc - MMC sub 
system


Usage:  

mmc read addr blk# 
cnt  
mmc write addr blk# 
cnt 
mmc erase blk# 
cnt  
mmc 
rescan  
mmc part - lists available partition on current mmc 
device  
mmc dev [dev] [part] - show

Re: [beagleboard] Creating a boot sd from an img file

[Robert Nelson]

On Mon, Apr 14, 2014 at 2:09 PM, JBodine  wrote:
> Thanks for the reply.   When I boot the BBB with one of these cards I've
> created, Angstrom only sees a single 70mb partition, if it's just windows
> having the problem, shouldn't my BBB show the entire 16gb partition?

It'll see a 70mb boot partition "and" a 3.7GB root partition. Use
gparted to expand the 2nd 3.7GB root partition.

Regards,

-- 
Robert Nelson
http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Creating a boot sd from an img file

[JBodine]

Thanks for the reply.   When I boot the BBB with one of these cards I've 
created, Angstrom only sees a single 70mb partition, if it's just windows 
having the problem, shouldn't my BBB show the entire 16gb partition?

Thanks

On Monday, April 14, 2014 11:59:22 AM UTC-7, RobertCNelson wrote:

> On Mon, Apr 14, 2014 at 1:54 PM, JBodine > 
> wrote: 
> > Using a BBB revision B, I've followed standard instructions for copying 
> the 
> > Angstrom distro to a micro SD card from a Windows 7 machine.  It works 
> and I 
> > can boot from the SD card, I've done this with both 16gb & 32gb micro sd 
> > cards.  First, I format the sd card so I have an empty card with a 
> single 
> > partition of 16gb free.   The problem is that after Win32DiskImager 
> copies 
> > the img file to the card, I'm always left with an sd card that has only 
> 70mb 
> > total space and only a few meg of available space.  If I look at the sd 
> card 
> > in Windows Computer Management, it shows the active partition of 71mb, 
> > another empty partition of 3.33gb and 12gb of unallocated space.   Is 
> there 
> > another tool besides Win32DiskImager or something else I can look at? 
>
> in "linux" you can use a tool called "gparted" to expand the 2nd 
> "ext4" partition.  Your windows machine doesn't understand what it's 
> seeing. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Creating a boot sd from an img file

[Robert Nelson]

On Mon, Apr 14, 2014 at 1:54 PM, JBodine  wrote:
> Using a BBB revision B, I've followed standard instructions for copying the
> Angstrom distro to a micro SD card from a Windows 7 machine.  It works and I
> can boot from the SD card, I've done this with both 16gb & 32gb micro sd
> cards.  First, I format the sd card so I have an empty card with a single
> partition of 16gb free.   The problem is that after Win32DiskImager copies
> the img file to the card, I'm always left with an sd card that has only 70mb
> total space and only a few meg of available space.  If I look at the sd card
> in Windows Computer Management, it shows the active partition of 71mb,
> another empty partition of 3.33gb and 12gb of unallocated space.   Is there
> another tool besides Win32DiskImager or something else I can look at?

in "linux" you can use a tool called "gparted" to expand the 2nd
"ext4" partition.  Your windows machine doesn't understand what it's
seeing.

Regards,

-- 
Robert Nelson
http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Creating a boot sd from an img file

[JBodine]

Using a BBB revision B, I've followed standard instructions for copying the 
Angstrom distro to a micro SD card from a Windows 7 machine.  It works and 
I can boot from the SD card, I've done this with both 16gb & 32gb micro sd 
cards.  First, I format the sd card so I have an empty card with a single 
partition of 16gb free.   The problem is that after Win32DiskImager copies 
the img file to the card, I'm always left with an sd card that has only 
70mb total space and only a few meg of available space.  If I look at the 
sd card in Windows Computer Management, it shows the active partition of 
71mb, another empty partition of 3.33gb and 12gb of unallocated space.   Is 
there another tool besides Win32DiskImager or something else I can look at?

Thanks

-- 
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] Setting I/O's

[Gerald Coley]

That is not correct. Please. Read the datasheet.

Gerald


On Mon, Apr 14, 2014 at 1:04 PM, Guy Grotke wrote:

>   All your programmable I/O pins are going to startup in tristate mode.
> That means you can just add a weak pullup or pulldown resistor (EG. 10K) to
> each pin’s circuit to make your external devices behave properly until your
> software programs the pins.
>
>  *From:* maartenrik...@gmail.com
> *Sent:* Monday, April 14, 2014 8:09 AM
> *To:* beagleboard@googlegroups.com
> *Subject:* Re: [beagleboard] Setting I/O's
>
>  Dear Gerald,
>
> Isn't it possible to set the IO's in the U-boot?
> before the kernel is started.
> This would be fast enough.
>
> Regards,
>
>
> Maarten
>
> Op maandag 14 april 2014 16:40:16 UTC+2 schreef Gerald:
>>
>> Read the datasheet for the default state of each pin on power up.
>>
>> http://www.ti.com/product/am3358
>>
>> These cannot be changed. Once the SW is loaded, it can set the pins to
>> whatever function it supports.
>>
>> Gerald
>>
>>
>>
>> On Mon, Apr 14, 2014 at 9:37 AM,  wrote:
>>
>>> Dear Reader,
>>>
>>> I have a question about the following problem.
>>> On the PCB I designed I use the BBB for setting some pumps and valves.
>>> When the system starts up the first seconds the IO pins are not logic 1
>>> or 0.
>>> Is it possible to set the GPIO's in U-boot before starting up the kernel
>>> and how can I do this?
>>>
>>> Thanks,
>>>
>>> Maarten
>>>
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
> --
> 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.
>
> --
> 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.
>

-- 
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] Re: Dude, where's my BeagleBone Black?

[Gerald Coley]

The AM335x has only 16bits of data. SO-DIMM would be a big waste.

Gerald



On Mon, Apr 14, 2014 at 1:07 PM, Jacek Radzikowski <
jacek.radzikow...@gmail.com> wrote:

> Would SO-DIMM socketed memory be a viable option? This would free some
> space on the board, but might complicate signal routing?
>
> j.
>
>
> On Mon, Apr 14, 2014 at 1:50 PM, Gerald Coley 
> wrote:
> > Not until the memory device is made that can get it to 1GB for sure. The
> > best we can do then is 1GB. The small form factor does not allow us to
> add
> > memory devices  Even then I am not sure we have the power supply to run
> it.
> > If it means a redesign of the power section, it won't happen.
> >
> > Gerald
> >
> >
> > On Mon, Apr 14, 2014 at 12:47 PM, Don deJuan 
> wrote:
> >>
> >> On 04/14/2014 04:01 AM, Jason Kridner wrote:
> >> > On Mon, Apr 14, 2014 at 3:25 AM, rh_ 
> >> > wrote:
> >> >> On Sun, 13 Apr 2014 19:07:00 -0400
> >> >> Jason Kridner  wrote:
> >> >>
> >> >> --8<--
> >> >>
> >> >>> To provide the best experience of using Debian on BeagleBone Black,
> we
> >> >>> are connecting the switch-over to an increase in the on-board eMMC
> >> >>> flash storage from 2GB to 4GB, leaving more free room in which you
> can
> >> >>> work. The eMMC is faster and more reliable than micro-SD cards, so
> >> >>> this is adding a lot of value---and a little bit of cost.
> >> >>>
> >> >>> These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev
> C
> >> >>> and they will likely cost a bit more at most distributors. This
> extra
> >> >>> money is helping CircuitCo pay for the additional expense of the
> eMMC,
> >> >>> but also to cover costs for ramping production to higher-than-ever
> >> >>> rates.
> >> >>>
> >> >>> With the additional capacity CircuitCo is bringing on, we expect to
> be
> >> >>> able to fill all end-user back-orders for the Rev B boards by early
> >> >>> May and shift all production to Rev C. With around 150,000 boards on
> >> >>> *distributor* back-orders, we'll be working with distributors to
> >> >>> quickly accept board shipments such that CircuitCo isn't sitting on
> >> >>> any units.
> >> >>>
> >> >> So no more 2GB eMMC models ever?  What about one with no eMMC
> >> >> at all? I know there are more than a few people here that boot from
> >> >> network, sdcard or usb.
> >> > Never say never, but we are unlikely to make any more 2GB eMMC models.
> >> > I've been kicking around the idea of doing a kickstarter for a no-eMMC
> >> > model, but I'd like to wait a month or two to see how the Rev C and
> >> > Element14 boards are doing out there.
> >> >
> >> >> Another thought occurred, has beagle or circuitco done any long
> >> >> duration
> >> >> eMMC testing? How graceful will the BBB handle a failed eMMC part?
> >> >> Failed as-in worn out from use not a defect. I think some people are
> >> >> concerned with eMMC failures and so they don't use it or don't rely
> >> >> on it.
> >> > The only data we have is from the manufacturer and the community.
> >> > After a year, we aren't seeing wear-out issues. The ext4 file system
> >> > if fairly robust, but if writes start failing, end-user failures can
> >> > occur in odd ways. If you are creating a mission-critical app that
> >> > must stay deployed for many years without the ability to perform
> >> > replacements, I'd encourage you to alter the eMMC contents to
> >> > read-only, except for your critical data acquisition.
> >> >
> >> >> --
> >> >> 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.
> >> any chance we will get a bump in RAM any time soon? Would love to see
> >> 1GB or catching up to some of the other boards with 2GB. I realize it
> >> would be a cost increase, but I think that would be a better option than
> >> no eMMC.
> >>
> >> --
> >> 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.
> >
> >
> > --
> > 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.
>
>
>
> --
> Given a choice between two theories, take the one which is funnier
>
> --
> For more options, visit http://beagleboard.org/discuss
> -

Re: [beagleboard] Re: Dude, where's my BeagleBone Black?

[Jacek Radzikowski]

Would SO-DIMM socketed memory be a viable option? This would free some
space on the board, but might complicate signal routing?

j.


On Mon, Apr 14, 2014 at 1:50 PM, Gerald Coley  wrote:
> Not until the memory device is made that can get it to 1GB for sure. The
> best we can do then is 1GB. The small form factor does not allow us to add
> memory devices  Even then I am not sure we have the power supply to run it.
> If it means a redesign of the power section, it won't happen.
>
> Gerald
>
>
> On Mon, Apr 14, 2014 at 12:47 PM, Don deJuan  wrote:
>>
>> On 04/14/2014 04:01 AM, Jason Kridner wrote:
>> > On Mon, Apr 14, 2014 at 3:25 AM, rh_ 
>> > wrote:
>> >> On Sun, 13 Apr 2014 19:07:00 -0400
>> >> Jason Kridner  wrote:
>> >>
>> >> --8<--
>> >>
>> >>> To provide the best experience of using Debian on BeagleBone Black, we
>> >>> are connecting the switch-over to an increase in the on-board eMMC
>> >>> flash storage from 2GB to 4GB, leaving more free room in which you can
>> >>> work. The eMMC is faster and more reliable than micro-SD cards, so
>> >>> this is adding a lot of value---and a little bit of cost.
>> >>>
>> >>> These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev C
>> >>> and they will likely cost a bit more at most distributors. This extra
>> >>> money is helping CircuitCo pay for the additional expense of the eMMC,
>> >>> but also to cover costs for ramping production to higher-than-ever
>> >>> rates.
>> >>>
>> >>> With the additional capacity CircuitCo is bringing on, we expect to be
>> >>> able to fill all end-user back-orders for the Rev B boards by early
>> >>> May and shift all production to Rev C. With around 150,000 boards on
>> >>> *distributor* back-orders, we'll be working with distributors to
>> >>> quickly accept board shipments such that CircuitCo isn't sitting on
>> >>> any units.
>> >>>
>> >> So no more 2GB eMMC models ever?  What about one with no eMMC
>> >> at all? I know there are more than a few people here that boot from
>> >> network, sdcard or usb.
>> > Never say never, but we are unlikely to make any more 2GB eMMC models.
>> > I've been kicking around the idea of doing a kickstarter for a no-eMMC
>> > model, but I'd like to wait a month or two to see how the Rev C and
>> > Element14 boards are doing out there.
>> >
>> >> Another thought occurred, has beagle or circuitco done any long
>> >> duration
>> >> eMMC testing? How graceful will the BBB handle a failed eMMC part?
>> >> Failed as-in worn out from use not a defect. I think some people are
>> >> concerned with eMMC failures and so they don't use it or don't rely
>> >> on it.
>> > The only data we have is from the manufacturer and the community.
>> > After a year, we aren't seeing wear-out issues. The ext4 file system
>> > if fairly robust, but if writes start failing, end-user failures can
>> > occur in odd ways. If you are creating a mission-critical app that
>> > must stay deployed for many years without the ability to perform
>> > replacements, I'd encourage you to alter the eMMC contents to
>> > read-only, except for your critical data acquisition.
>> >
>> >> --
>> >> 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.
>> any chance we will get a bump in RAM any time soon? Would love to see
>> 1GB or catching up to some of the other boards with 2GB. I realize it
>> would be a cost increase, but I think that would be a better option than
>> no eMMC.
>>
>> --
>> 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.
>
>
> --
> 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.



-- 
Given a choice between two theories, take the one which is funnier

-- 
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] Re: Dude, where's my BeagleBone Black?

[Gerald Coley]

Sorry. Jason says it has to fit in the Altoids box. Originally the form
factor was planned to be bigger, but that was a long time ago and before we
shrunk it.

Yes, the next gen version will have a little bit more RAM and a little
faster processor for you as well. And it will be bigger.

Gerald


On Mon, Apr 14, 2014 at 12:54 PM, William Hermans  wrote:

> Gerald, I for one would be willing to go with a larger form factor to gain
> more memory, and GbE.
>
> Anyhow, yes I am not trying to push you or anything like that, just making
> my thoughts known. Sounds like I will have to keep my eyes out for the next
> Generation :)
>
> IN the meantime, the minnowboard MAX *could* fit the bill, but I think I
> will wait and see whats going on with ARM for a while.
>
>
> On Mon, Apr 14, 2014 at 10:50 AM, Gerald Coley wrote:
>
>> Not until the memory device is made that can get it to 1GB for sure. The
>> best we can do then is 1GB. The small form factor does not allow us to add
>> memory devices  Even then I am not sure we have the power supply to run it.
>> If it means a redesign of the power section, it won't happen.
>>
>> Gerald
>>
>>
>> On Mon, Apr 14, 2014 at 12:47 PM, Don deJuan wrote:
>>
>>> On 04/14/2014 04:01 AM, Jason Kridner wrote:
>>> > On Mon, Apr 14, 2014 at 3:25 AM, rh_ 
>>> wrote:
>>> >> On Sun, 13 Apr 2014 19:07:00 -0400
>>> >> Jason Kridner  wrote:
>>> >>
>>> >> --8<--
>>> >>
>>> >>> To provide the best experience of using Debian on BeagleBone Black,
>>> we
>>> >>> are connecting the switch-over to an increase in the on-board eMMC
>>> >>> flash storage from 2GB to 4GB, leaving more free room in which you
>>> can
>>> >>> work. The eMMC is faster and more reliable than micro-SD cards, so
>>> >>> this is adding a lot of value---and a little bit of cost.
>>> >>>
>>> >>> These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev C
>>> >>> and they will likely cost a bit more at most distributors. This extra
>>> >>> money is helping CircuitCo pay for the additional expense of the
>>> eMMC,
>>> >>> but also to cover costs for ramping production to higher-than-ever
>>> >>> rates.
>>> >>>
>>> >>> With the additional capacity CircuitCo is bringing on, we expect to
>>> be
>>> >>> able to fill all end-user back-orders for the Rev B boards by early
>>> >>> May and shift all production to Rev C. With around 150,000 boards on
>>> >>> *distributor* back-orders, we'll be working with distributors to
>>> >>> quickly accept board shipments such that CircuitCo isn't sitting on
>>> >>> any units.
>>> >>>
>>> >> So no more 2GB eMMC models ever?  What about one with no eMMC
>>> >> at all? I know there are more than a few people here that boot from
>>> >> network, sdcard or usb.
>>> > Never say never, but we are unlikely to make any more 2GB eMMC models.
>>> > I've been kicking around the idea of doing a kickstarter for a no-eMMC
>>> > model, but I'd like to wait a month or two to see how the Rev C and
>>> > Element14 boards are doing out there.
>>> >
>>> >> Another thought occurred, has beagle or circuitco done any long
>>> duration
>>> >> eMMC testing? How graceful will the BBB handle a failed eMMC part?
>>> >> Failed as-in worn out from use not a defect. I think some people are
>>> >> concerned with eMMC failures and so they don't use it or don't rely
>>> >> on it.
>>> > The only data we have is from the manufacturer and the community.
>>> > After a year, we aren't seeing wear-out issues. The ext4 file system
>>> > if fairly robust, but if writes start failing, end-user failures can
>>> > occur in odd ways. If you are creating a mission-critical app that
>>> > must stay deployed for many years without the ability to perform
>>> > replacements, I'd encourage you to alter the eMMC contents to
>>> > read-only, except for your critical data acquisition.
>>> >
>>> >> --
>>> >> 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.
>>> any chance we will get a bump in RAM any time soon? Would love to see
>>> 1GB or catching up to some of the other boards with 2GB. I realize it
>>> would be a cost increase, but I think that would be a better option than
>>> no eMMC.
>>>
>>> --
>>> 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.
>>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard

Re: [beagleboard] Setting I/O's

[Guy Grotke]

All your programmable I/O pins are going to startup in tristate mode.  That 
means you can just add a weak pullup or pulldown resistor (EG. 10K) to each 
pin’s circuit to make your external devices behave properly until your software 
programs the pins.

From: maartenrik...@gmail.com 
Sent: Monday, April 14, 2014 8:09 AM
To: beagleboard@googlegroups.com 
Subject: Re: [beagleboard] Setting I/O's

Dear Gerald,

Isn't it possible to set the IO's in the U-boot? 
before the kernel is started.
This would be fast enough.

Regards,


Maarten

Op maandag 14 april 2014 16:40:16 UTC+2 schreef Gerald: 
  Read the datasheet for the default state of each pin on power up. 

  http://www.ti.com/product/am3358


  These cannot be changed. Once the SW is loaded, it can set the pins to 
whatever function it supports.

  Gerald




  On Mon, Apr 14, 2014 at 9:37 AM,  wrote:

Dear Reader,

I have a question about the following problem.
On the PCB I designed I use the BBB for setting some pumps and valves.
When the system starts up the first seconds the IO pins are not logic 1 or 
0.
Is it possible to set the GPIO's in U-boot before starting up the kernel 
and how can I do this?

Thanks,

Maarten


-- 
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.
For more options, visit https://groups.google.com/d/optout.


-- 
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.

-- 
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: U-Boot PHY Configuration/Demo Source Availability

[wolcott]

Has there been any resolution to this yet? I too have a board that is using 
the TLK105 PHY chip. Does anyone know if TI has support for this chip in 
u-boot and their SitraLinux distro yet?

Thanks!

On Saturday, March 1, 2014 1:33:50 PM UTC-8, kip...@ualberta.ca wrote:
>
>
> I'm working with a board based around the Beaglebone Black, and I'm having 
> some issues surrounding U-Boot. One difference between my board and the 
> shipped BBB is the Ethernet PHY used; the BBB's PHY has a default address 
> of '0', whereas the PHY I'm replacing it with (TI TLK105) has an address of 
> '1'. I've been working off the demo images for Angstrom up until now, but 
> this means that my PHY isn't being detected. I haven't looked into the 
> board file enough to know what's really going on, but I'm guessing that the 
> PHY address is hard-coded into U-Boot, and if U-Boot can't find the PHY 
> then you're out of luck.
>
> I tried to correct this by compiling U-Boot myself. I did a bit of 
> research into PHY configuration in U-Boot and I made a few modifications. I 
> added *#define CONFIG_CMD_MII *to the include/configs/am335x_evm.h file. 
> Once I built and deployed my compiled U-Boot, *mii *was a listed command 
> and *mii info 1 *confirmed that there was a PHY at that address. 
>
> I also added *#define CONFIG_PHY_ADDR   1 *and hoped that this would 
> change the default PHY address and everything else would take care of 
> itself, but this didn't really happen. When I was using the pre-compiled 
> U-Boot binaries, it reported:
>
> *Net:  not set. Validating first E-fuse MAC*
>> *Phy not found*
>> *PHY reset timed out*
>>
>
> After my modifications, I got the following:
>
>
>>
>>
>>
>> *Net:  not set. Validating first E-fuse MACCould not read the 
>> EEPROM; something fundamentally wrong on the I2C bus.Could not get Board 
>> ID, assuming BeagleBone Black.Could not get PHY for cpsw: addr 0*
>
>
> I don't really understand why the nature of the PHY error would change so 
> much. Any help with getting my PHY up and running would be appreciated, or 
> at least some confirmation that I'm going about this the right way. 
>
> I built U-Boot using this 
> guidewith the addition 
> of this 
> patchto
>  deal with some EEPROM issues I'm having. There is an EEPROM on the 
> board, but right now it doesn't have the correct BBB data written to it. 
> The weird thing is, the demo U-Boot images are able to read the EEPROM 
> (reporting 0xFF as its contents) while my modified U-Boot image cannot 
> even use the I2C bus. The hardware is identical, and if I jump back and 
> forth between the two U-Boot images, only the pre-compiled one is able to 
> read my EEPROM. It seems like there is some difference between the 
> configuration of the demo U-Boot images and the ones I've built from 
> source, but I can't find any documentation regarding the demo images so I 
> have no idea what they might be. Are the sources for the images available? 
> Since my uEnv.txt file is blank, once U-Boot loads it just hangs and waits 
> for me to tell it what to do. The uEnv.txt file in the demo image is also 
> blank, but U-Boot does some configuration and loads the kernel. I'm 
> guessing that this is hard-coded into the compiled U-Boot that's used, but 
> it would be nice to have it as a reference so I could eventually implement 
> the same behavior myself. I know that the demo image boots near-perfectly 
> on my board, so being able to add PHY support to that source would be much 
> easier than adding PHY support to the original U-Boot source and then guess 
> every modification made for the demo images. Implementing this stuff myself 
> is a useful learning experience and everything, but I feel like I'm 
> reinventing the wheel since I already had a working image to begin with. 
>
> Thanks
>

-- 
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] Reading over SPI with Beaglebone Black as Slave

[Guy Grotke]

I am running BBB SPI as slave but using the opposite direction for the data 
pins:

0x150 0x30  /* spi0_sclk.spi0_sclk, INPUT_PULLUP  | MODE0 */
0x154 0x10  /* spi0_d0.spi0_d0, OUTPUT_PULLUP | MODE0 */
0x158 0x30  /* spi0_d1.spi0_d1, INPUT_PULLUP  | MODE0 */
0x15c 0x30  /* spi0_cs0.spi0_cs0,   INPUT_PULLUP  | MODE0 */

I think your way can work fine too, it just requires setting up the right 
values in the SPI control registers.

But to make mine work as slave, I had to use mmap to directly access the SPI 
hardware registers.  I can do that from user-space because the protocol I 
designed for my SPI hardware has no realtime requirements that would require 
interrupts.  (The packets in both directions always fit in the FIFOs, and run 
in a half-duplex command/response mode.)

I don’t think any Linux SPI drivers support slave mode, and there is even an 
explanation available from Linus Torvalds if you search the web.  If you need 
interrupts for more demanding performance, you will have to write your own 
driver.



From: babakre...@gmail.com 
Sent: Saturday, April 12, 2014 1:39 AM
To: beagleboard@googlegroups.com 
Subject: [beagleboard] Reading over SPI with Beaglebone Black as Slave

Im trying to use the Beaglebone Black as a slave device and read from the 
arduino over SPI. 

Im confused as to why I am just getting 255 repeated over and over on the 
terminal as an output.
My thought is that there is some kind of a memory leak or buffer overflow. I 
just can not figure out what
I'm doing wrong. Is one supposed to set cs as input? even with it set to output 
I have the same issue.


I have my dts file set as:

/dts-v1/;
/plugin/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";

/* identification */
part-number = "spi0pinmux";

fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
spi0_pins_s0: spi0_pins_s0 {
pinctrl-single,pins = <
  0x150 0x30  /* spi0_sclk, INPUT_PULLUP | MODE0 */
  0x154 0x30  /* spi0_d0, INPUT_PULLUP | MODE0 */
  0x158 0x10  /* spi0_d1, OUTPUT_PULLUP | MODE0 */
  0x15c 0x30  /* spi0_cs0, INPUT_PULLUP | MODE0 */
>;
};
};
};

fragment@1 {
target = <&spi0>;
__overlay__ {
 #address-cells = <1>;
 #size-cells = <0>;

 status = "okay";
 pinctrl-names = "default";
 pinctrl-0 = <&spi0_pins_s0>;

 spidev@0 {
 spi-max-frequency = <2400>;
 reg = <0>;
 compatible = "linux,spidev";
};
};
};
};

My Arduino is wired up like so:
P9.22 SPI0_CLK - Orange - 0x150 0x30 --> Arduino Due 110 SCLK
P9.21 SPI0_D0 - Green - 0x154 0x30 --> Arduino Due 109 MOSI
P9.18 SPI0_D1 - White - 0x158 0x10 --> 108 MISO
P9.17 SP0_CS0 - Black - 0x15C 0x30 ---> Pin 10 Set as Slave Select

Python File:
import spidev
import time
spi = spidev.SpiDev()
spi.open(1,0)
while True:
   resp = spi.readbytes(1)
   print resp[0]



-- 
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.

-- 
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] Re: Dude, where's my BeagleBone Black?

[William Hermans]

Gerald, I for one would be willing to go with a larger form factor to gain
more memory, and GbE.

Anyhow, yes I am not trying to push you or anything like that, just making
my thoughts known. Sounds like I will have to keep my eyes out for the next
Generation :)

IN the meantime, the minnowboard MAX *could* fit the bill, but I think I
will wait and see whats going on with ARM for a while.


On Mon, Apr 14, 2014 at 10:50 AM, Gerald Coley wrote:

> Not until the memory device is made that can get it to 1GB for sure. The
> best we can do then is 1GB. The small form factor does not allow us to add
> memory devices  Even then I am not sure we have the power supply to run it.
> If it means a redesign of the power section, it won't happen.
>
> Gerald
>
>
> On Mon, Apr 14, 2014 at 12:47 PM, Don deJuan wrote:
>
>> On 04/14/2014 04:01 AM, Jason Kridner wrote:
>> > On Mon, Apr 14, 2014 at 3:25 AM, rh_ 
>> wrote:
>> >> On Sun, 13 Apr 2014 19:07:00 -0400
>> >> Jason Kridner  wrote:
>> >>
>> >> --8<--
>> >>
>> >>> To provide the best experience of using Debian on BeagleBone Black, we
>> >>> are connecting the switch-over to an increase in the on-board eMMC
>> >>> flash storage from 2GB to 4GB, leaving more free room in which you can
>> >>> work. The eMMC is faster and more reliable than micro-SD cards, so
>> >>> this is adding a lot of value---and a little bit of cost.
>> >>>
>> >>> These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev C
>> >>> and they will likely cost a bit more at most distributors. This extra
>> >>> money is helping CircuitCo pay for the additional expense of the eMMC,
>> >>> but also to cover costs for ramping production to higher-than-ever
>> >>> rates.
>> >>>
>> >>> With the additional capacity CircuitCo is bringing on, we expect to be
>> >>> able to fill all end-user back-orders for the Rev B boards by early
>> >>> May and shift all production to Rev C. With around 150,000 boards on
>> >>> *distributor* back-orders, we'll be working with distributors to
>> >>> quickly accept board shipments such that CircuitCo isn't sitting on
>> >>> any units.
>> >>>
>> >> So no more 2GB eMMC models ever?  What about one with no eMMC
>> >> at all? I know there are more than a few people here that boot from
>> >> network, sdcard or usb.
>> > Never say never, but we are unlikely to make any more 2GB eMMC models.
>> > I've been kicking around the idea of doing a kickstarter for a no-eMMC
>> > model, but I'd like to wait a month or two to see how the Rev C and
>> > Element14 boards are doing out there.
>> >
>> >> Another thought occurred, has beagle or circuitco done any long
>> duration
>> >> eMMC testing? How graceful will the BBB handle a failed eMMC part?
>> >> Failed as-in worn out from use not a defect. I think some people are
>> >> concerned with eMMC failures and so they don't use it or don't rely
>> >> on it.
>> > The only data we have is from the manufacturer and the community.
>> > After a year, we aren't seeing wear-out issues. The ext4 file system
>> > if fairly robust, but if writes start failing, end-user failures can
>> > occur in odd ways. If you are creating a mission-critical app that
>> > must stay deployed for many years without the ability to perform
>> > replacements, I'd encourage you to alter the eMMC contents to
>> > read-only, except for your critical data acquisition.
>> >
>> >> --
>> >> 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.
>> any chance we will get a bump in RAM any time soon? Would love to see
>> 1GB or catching up to some of the other boards with 2GB. I realize it
>> would be a cost increase, but I think that would be a better option than
>> no eMMC.
>>
>> --
>> 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.
>>
>
>  --
> 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.
>

-- 
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...@googlegrou

Re: [beagleboard] Re: Dude, where's my BeagleBone Black?

[Gerald Coley]

Not until the memory device is made that can get it to 1GB for sure. The
best we can do then is 1GB. The small form factor does not allow us to add
memory devices  Even then I am not sure we have the power supply to run it.
If it means a redesign of the power section, it won't happen.

Gerald


On Mon, Apr 14, 2014 at 12:47 PM, Don deJuan  wrote:

> On 04/14/2014 04:01 AM, Jason Kridner wrote:
> > On Mon, Apr 14, 2014 at 3:25 AM, rh_ 
> wrote:
> >> On Sun, 13 Apr 2014 19:07:00 -0400
> >> Jason Kridner  wrote:
> >>
> >> --8<--
> >>
> >>> To provide the best experience of using Debian on BeagleBone Black, we
> >>> are connecting the switch-over to an increase in the on-board eMMC
> >>> flash storage from 2GB to 4GB, leaving more free room in which you can
> >>> work. The eMMC is faster and more reliable than micro-SD cards, so
> >>> this is adding a lot of value---and a little bit of cost.
> >>>
> >>> These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev C
> >>> and they will likely cost a bit more at most distributors. This extra
> >>> money is helping CircuitCo pay for the additional expense of the eMMC,
> >>> but also to cover costs for ramping production to higher-than-ever
> >>> rates.
> >>>
> >>> With the additional capacity CircuitCo is bringing on, we expect to be
> >>> able to fill all end-user back-orders for the Rev B boards by early
> >>> May and shift all production to Rev C. With around 150,000 boards on
> >>> *distributor* back-orders, we'll be working with distributors to
> >>> quickly accept board shipments such that CircuitCo isn't sitting on
> >>> any units.
> >>>
> >> So no more 2GB eMMC models ever?  What about one with no eMMC
> >> at all? I know there are more than a few people here that boot from
> >> network, sdcard or usb.
> > Never say never, but we are unlikely to make any more 2GB eMMC models.
> > I've been kicking around the idea of doing a kickstarter for a no-eMMC
> > model, but I'd like to wait a month or two to see how the Rev C and
> > Element14 boards are doing out there.
> >
> >> Another thought occurred, has beagle or circuitco done any long duration
> >> eMMC testing? How graceful will the BBB handle a failed eMMC part?
> >> Failed as-in worn out from use not a defect. I think some people are
> >> concerned with eMMC failures and so they don't use it or don't rely
> >> on it.
> > The only data we have is from the manufacturer and the community.
> > After a year, we aren't seeing wear-out issues. The ext4 file system
> > if fairly robust, but if writes start failing, end-user failures can
> > occur in odd ways. If you are creating a mission-critical app that
> > must stay deployed for many years without the ability to perform
> > replacements, I'd encourage you to alter the eMMC contents to
> > read-only, except for your critical data acquisition.
> >
> >> --
> >> 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.
> any chance we will get a bump in RAM any time soon? Would love to see
> 1GB or catching up to some of the other boards with 2GB. I realize it
> would be a cost increase, but I think that would be a better option than
> no eMMC.
>
> --
> 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.
>

-- 
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] BBIOConfig -> BB universal IO UI testing release

[William Hermans]

Awesome Charles, and Alexander ! will definitely check it out. Charles, is
this kernel neutral ?


On Mon, Apr 14, 2014 at 6:29 AM, Jason Kridner wrote:

> On Mon, Apr 14, 2014 at 8:19 AM,  wrote:
>
>> Hello BeagleBone community,
>>
>> I have created a UI for Charles BB universal IO tool that will be part of
>> the upcoming Debian image release. Please test and provide feedback. You
>> can find binaries for Linux, Mac and Windows here:
>> https://github.com/strahlex/BBIOConfig/releases
>>
>
> Thanks for this great contribution. Glad to have you as part of the
> community!
>
>
>>
>>
>> For a short introduction take a look at the wiki:
>> https://github.com/strahlex/BBIOConfig/wiki/User-Manual
>>
>>
>> 
>>
>>
>>
>> Regards
>> Strahlex
>>
>> --
>> 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.
>>
>
>  --
> 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.
>

-- 
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] Re: Dude, where's my BeagleBone Black?

[Don deJuan]

On 04/14/2014 04:01 AM, Jason Kridner wrote:
> On Mon, Apr 14, 2014 at 3:25 AM, rh_  wrote:
>> On Sun, 13 Apr 2014 19:07:00 -0400
>> Jason Kridner  wrote:
>>
>> --8<--
>>
>>> To provide the best experience of using Debian on BeagleBone Black, we
>>> are connecting the switch-over to an increase in the on-board eMMC
>>> flash storage from 2GB to 4GB, leaving more free room in which you can
>>> work. The eMMC is faster and more reliable than micro-SD cards, so
>>> this is adding a lot of value---and a little bit of cost.
>>>
>>> These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev C
>>> and they will likely cost a bit more at most distributors. This extra
>>> money is helping CircuitCo pay for the additional expense of the eMMC,
>>> but also to cover costs for ramping production to higher-than-ever
>>> rates.
>>>
>>> With the additional capacity CircuitCo is bringing on, we expect to be
>>> able to fill all end-user back-orders for the Rev B boards by early
>>> May and shift all production to Rev C. With around 150,000 boards on
>>> *distributor* back-orders, we'll be working with distributors to
>>> quickly accept board shipments such that CircuitCo isn't sitting on
>>> any units.
>>>
>> So no more 2GB eMMC models ever?  What about one with no eMMC
>> at all? I know there are more than a few people here that boot from
>> network, sdcard or usb.
> Never say never, but we are unlikely to make any more 2GB eMMC models.
> I've been kicking around the idea of doing a kickstarter for a no-eMMC
> model, but I'd like to wait a month or two to see how the Rev C and
> Element14 boards are doing out there.
>
>> Another thought occurred, has beagle or circuitco done any long duration
>> eMMC testing? How graceful will the BBB handle a failed eMMC part?
>> Failed as-in worn out from use not a defect. I think some people are
>> concerned with eMMC failures and so they don't use it or don't rely
>> on it.
> The only data we have is from the manufacturer and the community.
> After a year, we aren't seeing wear-out issues. The ext4 file system
> if fairly robust, but if writes start failing, end-user failures can
> occur in odd ways. If you are creating a mission-critical app that
> must stay deployed for many years without the ability to perform
> replacements, I'd encourage you to alter the eMMC contents to
> read-only, except for your critical data acquisition.
>
>> --
>> 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.
any chance we will get a bump in RAM any time soon? Would love to see
1GB or catching up to some of the other boards with 2GB. I realize it
would be a cost increase, but I think that would be a better option than
no eMMC.

-- 
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] Re: Dude, where's my BeagleBone Black?

[Gerald Coley]

Drop the expansion headers and a lot of things could be done. Keep them,
and you won't get Dual GbE. You might be better waiting on the
next generation offering.

Gerald



On Mon, Apr 14, 2014 at 12:36 PM, William Hermans  wrote:

> Charles, yes thats it thanks.
>
> Jason,  Just on a rough guess, how much would a 4GB model with GbE, and
> 1GB memory cost ? Since you mention KickStarter, I figure if the price
> point could be low enough, it also might be worth it. Dual GbE would even
> be better( I bet you all can see where I am going with this ).
>
>
> On Mon, Apr 14, 2014 at 4:44 AM, Robert Berger <
> robert.karl.ber...@gmail.com> wrote:
>
>> Hi,
>> >>
>> >> I mean can I take an SD card which runs on a  Circuitco BBB and expect
>> this
>> >> to work on an Embest BB Black?
>> >
>> > Yes.
>>
>>
>> OK thanks!
>>
>> >
>> >>
>> >> BTW I will do a webinar "From Arduino Uno to BeagleBone Black (and
>> back)![1]
>> >> on 17th and such a question might arise.
>> >
>> > Sounds interesting. Will you talk about stuff like Userspace Arduino
>> > and using the PRUs?
>>
>> Not really. It's just 30 min ;)
>>
>> For the average Embedded software person it's quite painful to create
>> (or let others create) prototyping hardware in order to write software
>> which talks to sensors and actuators. On the one hand it's quite
>> straightforward to build up some hardware and write test software with
>> libraries available for the Arduino UNO, on the other hand it's not that
>> easy to do the same thing "right" in Embedded Linux. Wouldn't it be nice
>> to reuse this tested hardware prototype and write code for Embedded
>> Linux to talk to it? I intentionally don't want to use Arduino wrapping
>> libraries on Linux since those are typically not industrial strength,
>> but targeted towards hobbyists. This is what's going to be presented
>> here. BTW the prototyping hardware is not only able to convert signal
>> levels from an Arduino UNO (shield) to a Beagle Bone, but also to
>> convert signal levels from a Beagle Bone (cape) to an Arduino UNO if
>> that's needed.
>>
>> >
>> >>
>> >> Regards,
>> >>
>> >> Robert
>> >>
>> >> [1] http://www.element14.com/community/events/4021
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> 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.
>> >
>>
>> --
>> 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.
>>
>
>  --
> 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.
>

-- 
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] Re: Bad Linux ARM zImage magic

[William Hermans]

Robert, They are still useful I think to someone, maybe make an archive ?
Just suggestion.


On Mon, Apr 14, 2014 at 10:30 AM, Robert Nelson wrote:

> On Mon, Apr 14, 2014 at 12:24 PM, William Hermans 
> wrote:
> > One thing I am finding unclear in your latest instructions Robert.
> >
> > Under the root file system heading .  .
> >
> > "optargs=quiet init=/lib/systemd/systemd"
>
> Yeah, i haven't documented the systemd stuff very well on those pages.
>
> >
> > Now I suspect I know what this is for and how to use it, but someone else
> > may not. By the way your comments section of that site is completely
> > terrible now days. Neither firefox, nor chrome on my system here could
> load
> > your text editor. Just sat there loading indefinitely.
>
> Yeap, and every new comment, just makes those pages worse.  That's why
> I moved the comments into their own pages about a year ago. The mysql
> server really struggles with them.  I'm tempted to start purging
> old-outdated comments.
>
> Regards,
>
> --
> Robert Nelson
> http://www.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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] Re: Dude, where's my BeagleBone Black?

[William Hermans]

Charles, yes thats it thanks.

Jason,  Just on a rough guess, how much would a 4GB model with GbE, and 1GB
memory cost ? Since you mention KickStarter, I figure if the price point
could be low enough, it also might be worth it. Dual GbE would even be
better( I bet you all can see where I am going with this ).


On Mon, Apr 14, 2014 at 4:44 AM, Robert Berger  wrote:

> Hi,
> >>
> >> I mean can I take an SD card which runs on a  Circuitco BBB and expect
> this
> >> to work on an Embest BB Black?
> >
> > Yes.
>
>
> OK thanks!
>
> >
> >>
> >> BTW I will do a webinar "From Arduino Uno to BeagleBone Black (and
> back)![1]
> >> on 17th and such a question might arise.
> >
> > Sounds interesting. Will you talk about stuff like Userspace Arduino
> > and using the PRUs?
>
> Not really. It's just 30 min ;)
>
> For the average Embedded software person it's quite painful to create
> (or let others create) prototyping hardware in order to write software
> which talks to sensors and actuators. On the one hand it's quite
> straightforward to build up some hardware and write test software with
> libraries available for the Arduino UNO, on the other hand it's not that
> easy to do the same thing "right" in Embedded Linux. Wouldn't it be nice
> to reuse this tested hardware prototype and write code for Embedded
> Linux to talk to it? I intentionally don't want to use Arduino wrapping
> libraries on Linux since those are typically not industrial strength,
> but targeted towards hobbyists. This is what's going to be presented
> here. BTW the prototyping hardware is not only able to convert signal
> levels from an Arduino UNO (shield) to a Beagle Bone, but also to
> convert signal levels from a Beagle Bone (cape) to an Arduino UNO if
> that's needed.
>
> >
> >>
> >> Regards,
> >>
> >> Robert
> >>
> >> [1] http://www.element14.com/community/events/4021
> >>
> >>
> >>
> >>
> >> --
> >> 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.
> >
>
> --
> 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.
>

-- 
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] Re: Bad Linux ARM zImage magic

[Robert Nelson]

On Mon, Apr 14, 2014 at 12:24 PM, William Hermans  wrote:
> One thing I am finding unclear in your latest instructions Robert.
>
> Under the root file system heading .  .
>
> "optargs=quiet init=/lib/systemd/systemd"

Yeah, i haven't documented the systemd stuff very well on those pages.

>
> Now I suspect I know what this is for and how to use it, but someone else
> may not. By the way your comments section of that site is completely
> terrible now days. Neither firefox, nor chrome on my system here could load
> your text editor. Just sat there loading indefinitely.

Yeap, and every new comment, just makes those pages worse.  That's why
I moved the comments into their own pages about a year ago. The mysql
server really struggles with them.  I'm tempted to start purging
old-outdated comments.

Regards,

-- 
Robert Nelson
http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Bad Linux ARM zImage magic

[William Hermans]

One thing I am finding unclear in your latest instructions Robert.

Under the root file system heading .  .

"optargs=quiet init=/lib/systemd/systemd"

Now I suspect I know what this is for and how to use it, but someone else
may not. By the way your comments section of that site is completely
terrible now days. Neither firefox, nor chrome on my system here could load
your text editor. Just sat there loading indefinitely.


On Mon, Apr 14, 2014 at 9:36 AM, Robert Nelson wrote:

> On Fri, Apr 11, 2014 at 7:07 PM,   wrote:
> > I went back and started from scratch with u-boot. It looks like it had
> build
> > errors.
> >
> > git clone git://git.denx.de/u-boot.git
> > Cloning into 'u-boot'...
> > remote: Counting objects: 253022, done.
> > remote: Compressing objects: 100% (49006/49006), done.
> > remote: Total 253022 (delta 202954), reused 249594 (delta 199777)
> > Receiving objects: 100% (253022/253022), 60.92 MiB | 5.80 MiB/s, done.
> > Resolving deltas: 100% (202954/202954), done.
> > victoryred@WorkStation:~$ cd u-boot
> > victoryred@WorkStation:~/u-boot$ git checkout v2014.04-rc3 -b tmp
> > Switched to a new branch 'tmp'
> > victoryred@WorkStation:~/u-boot$ wget -c
> >
> https://raw.github.com/eewiki/u-boot-patches/master/v2014.04-rc3/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
> > --2014-04-11 16:41:52--
> >
> https://raw.github.com/eewiki/u-boot-patches/master/v2014.04-rc3/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
> > Resolving raw.github.com (raw.github.com)... 199.27.79.133
> > Connecting to raw.github.com (raw.github.com)|199.27.79.133|:443...
> > connected.
> > HTTP request sent, awaiting response... 200 OK
> > Length: 4886 (4.8K) [text/plain]
> > Saving to: `0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch'
> >
> >
> 100%[>]
> > 4,886   --.-K/s   in 0.001s
> >
> > 2014-04-11 16:41:52 (7.62 MB/s) -
> > `0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch' saved [4886/4886]
> >
> >
> > patch -p1 < 0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
> > patching file include/configs/am335x_evm.h
> > patching file include/configs/ti_armv7_common.h
> > victoryred@WorkStation:~/u-boot$ make ARCH=arm CROSS_COMPILE=${CC}
> distclean
> > victoryred@WorkStation:~/u-boot$ make ARCH=arm CROSS_COMPILE=${CC}
> > am335x_evm_config
> > Configuring for am335x_evm - Board: am335x_evm, Options:
> > SERIAL1,CONS_INDEX=1,NAND
> > victoryred@WorkStation:~/u-boot$ make ARCH=arm CROSS_COMPILE=${CC}
> >   GEN include/autoconf.mk.dep
> > cc1: error: bad value (armv5) for -march= switch
> >   GEN include/autoconf.mk
> > cc1: error: bad value (armv5) for -march= switch
> >   CHK include/config/uboot.release
> >   UPD include/config/uboot.release
> >   CHK include/generated/version_autogenerated.h
> >   UPD include/generated/version_autogenerated.h
> >   CHK include/generated/timestamp_autogenerated.h
> >   UPD include/generated/timestamp_autogenerated.h
> >   HOSTCC  scripts/basic/fixdep
> >   CC  lib/asm-offsets.s
> > lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
> > make[1]: *** [lib/asm-offsets.s] Error 1
> > make: *** [prepare0] Error 2
>
> Thus you never set "CC" to the cross compiler referenced..
>
> Regards,
>
> --
> Robert Nelson
> http://www.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+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Drew Fustini]

Thanks very much for all your hard work, Gerald, and everyone else involved
in my favorite Open Source Hardware Linux computer.

For those that haven't seen, Jason wrote a great post yesterday about the
state of BBB supply and recent developments:
http://beagleboard.org/blog/2014-04-13-dude-wheres-my-beaglebone-black/


On Mon, Apr 14, 2014 at 9:22 AM, Gerald Coley wrote:

>  If anyone wants to take my place on dealing with my frustration on this
> side of the issue, I will gladly let them. Any takers?
>
> Gerald
>
>
>
> On Mon, Apr 14, 2014 at 12:53 AM, Anil Gupta wrote:
>
>> The comments by Hannes are reflective of his frustration with
>> availability, so I would take them in that spirit.
>>
>> A lot of people are working hard to address BBB supply.  So I am sure at
>> some point, we will hear of increased supply which will reduce frustration.
>>
>> Hannes: I don't know of the entire landscape of Linux boards but we have
>> extensively tested boards by Olimex.  www.olimex.com  Although we prefer
>> BBB, we felt that Olimex has reasonably priced, industrial quality
>> products.   Maybe they have something that is a fit for you.
>>
>>
>> On Mon, Apr 14, 2014 at 10:37 AM, William Hermans wrote:
>>
>>> You come onto the beagleboard forums, make rude remarks to as how you
>>> think it should be available, and expect someone to help you ?
>>>
>>> That takes brass. Good luck.
>>>
>>>
>>> On Sat, Apr 12, 2014 at 7:03 AM,  wrote:
>>>
  I checked every store in EU and US I could find to get a BBB, there
 is no single one available worldwide.
 That's such a joke ..
 Oh well I can get them on ebay, for 999 EUR (1400 USD) per piece.

 The whole release management of that product is a big fail, listing 20
 stores and all of them have no availablility ..

 --

 I don't want to bet on a product which is not available fo rmonths when
 I need it.
 Is there a good replacement to BBB ? Should have about the same
 performance and many pinouts.

  --
 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.

>>>
>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/Z3JfUIkxOl8/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard+unsubscr...@googlegroups.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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.
>>
>
>  --
> 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.
>

-- 
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: BBB Bare Metal with HDMI

[dean . wedel]

Travis:

I know that you have alot going on there with other projects, but just 
checking if you have any progress on bare-metal HDMI code at this point? 
I'm looking forward to what you have to show. Especially the pin-muxing 
part :-)

Sincerely,
Dean


On Wednesday, March 26, 2014 10:07:41 AM UTC-7, dean@gmail.com wrote:
>
> Thanks alot for all your efforts! I'll keep an eye on this group for your 
> developments.
>
> On Tuesday, March 25, 2014 9:51:57 AM UTC-7, Travis Estep wrote:
>>
>> Yes, I do have this somewhat working now. It has taken a lot of time and 
>> many different resources to get to where I am now, but progress is coming 
>> along slowly. I have a few other projects going on in parallel, so I don't 
>> have all the time if like to devote to it. I should have the code in a 
>> stable and mostly functional state pretty soon. But I wouldn't expect ago 
>> of the bells and whistles to be working. I'll post back here with the Git 
>> repo once I've uploaded it.
>>
>> Also, I plan to post any and all docs and information along with the code 
>> so that the community can get involved and help make this driver fully 
>> functional. Just keep an eye on this post for the next couple of weeks.
>>
>

-- 
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] Re: Debian, Bluez and a Sony PS3 Sixaxis Controller

[Don deJuan]

On 04/14/2014 09:41 AM, mac...@msn.com wrote:
> I upgraded my Debian v3.8 to v3.13.9 so that I could plug a powered
> USB hub into the BBB USB host so that I could plug a Rocketfish BT
> dongle and my Sony sixaxis concurrently for pairing. Otherwise you can
> only plug one device into the USB host at a time. I think there is
> more to do to support USB. Long story short in Debian v3.8 my
> Rocketfish dongle was correctly identified. In Debian v3.13.9 I get
> the following-
>
> root@arm:/# dmesg |tail
> [ 1223.364177] usb 2-1: new full-speed USB device number 4 using musb-hdrc
> [ 1276.911353] Bluetooth: Core ver 2.17
> [ 1276.911471] NET: Registered protocol family 31
> [ 1276.911482] Bluetooth: HCI device and connection manager initialized
> [ 1276.911532] Bluetooth: HCI socket layer initialized
> [ 1276.911549] Bluetooth: L2CAP socket layer initialized
> [ 1276.911578] Bluetooth: SCO socket layer initialized
> [ 1276.944459] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 1276.944480] Bluetooth: BNEP filters: protocol multicast
> [ 1276.944530] Bluetooth: BNEP socket layer initialized
> root@arm:/# hcitool dev
> Devices:
> root@arm:/# [ 1349.186393] usb 2-1.1: device v0a5c p4502 is not supported
> [ 1349.396415] usb 2-1.2: device v0a5c p4503 is not supported
> [ 1349.606618] usb 2-1.3: device v0461 p4d75 is not supported
>
> ...Back to the drawing board.
>
>
>
> On Tuesday, April 8, 2014 9:33:56 PM UTC-7, mac...@msn.com wrote:
>
> Hi All,
>
> First I want to thank Robert, Jason and everyone that coded/tested
> to bring Debian to our projects. My life became considerably
> easier because of those efforts. Magnificent!
>
> The next hurdle for me has been trying to get a Sony PS3 sixaxis
> controller and the Sony wireless keyboard working with Bluetooth
> (Bluez). The problem seems to be that when I plug the controller
> into the USB port, UDEV creates input/js0 and event0
>
> but Dmesg reports-
>
> [15105.669932] input: Sony PLAYSTATION(R)3 Controller as
> /devices/ocp.3/4740.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input2
> [15105.671447] usbhid 1-1:1.0: looking for a minor, starting at 96
> [15105.672694] sony 0003:054C:0268.0002: input,hiddev0,hidraw0:
> USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on
> usb-musb-hdrc.1.auto-1/input0
> [15105.675678] hub 1-0:1.0: state 7 ports 1 chg  evt 0002
> [15105.675776] hub 1-0:1.0: port 1 enable change, status 0103
>
> but lacks reporting the following
>
> sony :::: Calling sixaxis_set_operational_usb
> sony :::: Sony PS3 Controller bdaddr: xx:xx:xx:xx:xx:xx
>
>
> From what I understand there is a patch that went into Linux
> kernel since 2.6.37 but I could never find it in the changelogs.
> Does anyone know if this patch carried through to 3.8.13-bone41?
>
> Also the Bluez version we have for Debian seems to be 4.99 and the
> latest version on www.bluez.org  is up to
> 5.17. Sixaxis looks to be fully supported in that version. Any
> chance we will be going to a newer version of Bluez in the near
> future?
>
> Thanks!
>   
>
>
> -- 
> 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.

It should build could be a few different reasons its failing for you. If
I get time I will setup a deb install and see about compiling it. But it
for sure builds on Arch.

-- 
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] Re: Debian, Bluez and a Sony PS3 Sixaxis Controller

[Robert Nelson]

On Mon, Apr 14, 2014 at 11:41 AM,   wrote:
> I upgraded my Debian v3.8 to v3.13.9 so that I could plug a powered USB hub
> into the BBB USB host so that I could plug a Rocketfish BT dongle and my
> Sony sixaxis concurrently for pairing. Otherwise you can only plug one
> device into the USB host at a time. I think there is more to do to support
> USB. Long story short in Debian v3.8 my Rocketfish dongle was correctly
> identified. In Debian v3.13.9 I get the following-
>
> root@arm:/# dmesg |tail
> [ 1223.364177] usb 2-1: new full-speed USB device number 4 using musb-hdrc
> [ 1276.911353] Bluetooth: Core ver 2.17
> [ 1276.911471] NET: Registered protocol family 31
> [ 1276.911482] Bluetooth: HCI device and connection manager initialized
> [ 1276.911532] Bluetooth: HCI socket layer initialized
> [ 1276.911549] Bluetooth: L2CAP socket layer initialized
> [ 1276.911578] Bluetooth: SCO socket layer initialized
> [ 1276.944459] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 1276.944480] Bluetooth: BNEP filters: protocol multicast
> [ 1276.944530] Bluetooth: BNEP socket layer initialized
> root@arm:/# hcitool dev
> Devices:
> root@arm:/# [ 1349.186393] usb 2-1.1: device v0a5c p4502 is not supported
> [ 1349.396415] usb 2-1.2: device v0a5c p4503 is not supported
> [ 1349.606618] usb 2-1.3: device v0461 p4d75 is not supported

That looks like you didn't copy the modules to the rootfs..

Regards,

-- 
Robert Nelson
http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Debian, Bluez and a Sony PS3 Sixaxis Controller

[macarr]

I upgraded my Debian v3.8 to v3.13.9 so that I could plug a powered USB hub 
into the BBB USB host so that I could plug a Rocketfish BT dongle and my 
Sony sixaxis concurrently for pairing. Otherwise you can only plug one 
device into the USB host at a time. I think there is more to do to support 
USB. Long story short in Debian v3.8 my Rocketfish dongle was correctly 
identified. In Debian v3.13.9 I get the following-

root@arm:/# dmesg |tail
[ 1223.364177] usb 2-1: new full-speed USB device number 4 using musb-hdrc
[ 1276.911353] Bluetooth: Core ver 2.17
[ 1276.911471] NET: Registered protocol family 31
[ 1276.911482] Bluetooth: HCI device and connection manager initialized
[ 1276.911532] Bluetooth: HCI socket layer initialized
[ 1276.911549] Bluetooth: L2CAP socket layer initialized
[ 1276.911578] Bluetooth: SCO socket layer initialized
[ 1276.944459] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1276.944480] Bluetooth: BNEP filters: protocol multicast
[ 1276.944530] Bluetooth: BNEP socket layer initialized
root@arm:/# hcitool dev
Devices:
root@arm:/# [ 1349.186393] usb 2-1.1: device v0a5c p4502 is not supported
[ 1349.396415] usb 2-1.2: device v0a5c p4503 is not supported
[ 1349.606618] usb 2-1.3: device v0461 p4d75 is not supported

...Back to the drawing board.



On Tuesday, April 8, 2014 9:33:56 PM UTC-7, mac...@msn.com wrote:
>
> Hi All,
>
> First I want to thank Robert, Jason and everyone that coded/tested to 
> bring Debian to our projects. My life became considerably easier because of 
> those efforts. Magnificent!
>
> The next hurdle for me has been trying to get a Sony PS3 sixaxis 
> controller and the Sony wireless keyboard working with Bluetooth (Bluez). 
> The problem seems to be that when I plug the controller into the USB port, 
> UDEV creates input/js0 and event0 
>
> but Dmesg reports- 
>
> [15105.669932] input: Sony PLAYSTATION(R)3 Controller as 
> /devices/ocp.3/4740.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input2
> [15105.671447] usbhid 1-1:1.0: looking for a minor, starting at 96
> [15105.672694] sony 0003:054C:0268.0002: input,hiddev0,hidraw0: USB HID 
> v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on 
> usb-musb-hdrc.1.auto-1/input0
> [15105.675678] hub 1-0:1.0: state 7 ports 1 chg  evt 0002
> [15105.675776] hub 1-0:1.0: port 1 enable change, status 0103
>
> but lacks reporting the following
>
> sony :::: Calling sixaxis_set_operational_usb
> sony :::: Sony PS3 Controller bdaddr: xx:xx:xx:xx:xx:xx
>
>
> From what I understand there is a patch that went into Linux kernel since 
> 2.6.37 but I could never find it in the changelogs. Does anyone know if 
> this patch carried through to 3.8.13-bone41?
>
> Also the Bluez version we have for Debian seems to be 4.99 and the latest 
> version on www.bluez.org is up to 5.17. Sixaxis looks to be fully 
> supported in that version. Any chance we will be going to a newer version 
> of Bluez in the near future?
>
> Thanks!
>   
>
>
>

-- 
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] Re: Bad Linux ARM zImage magic

[Robert Nelson]

On Fri, Apr 11, 2014 at 7:07 PM,   wrote:
> I went back and started from scratch with u-boot. It looks like it had build
> errors.
>
> git clone git://git.denx.de/u-boot.git
> Cloning into 'u-boot'...
> remote: Counting objects: 253022, done.
> remote: Compressing objects: 100% (49006/49006), done.
> remote: Total 253022 (delta 202954), reused 249594 (delta 199777)
> Receiving objects: 100% (253022/253022), 60.92 MiB | 5.80 MiB/s, done.
> Resolving deltas: 100% (202954/202954), done.
> victoryred@WorkStation:~$ cd u-boot
> victoryred@WorkStation:~/u-boot$ git checkout v2014.04-rc3 -b tmp
> Switched to a new branch 'tmp'
> victoryred@WorkStation:~/u-boot$ wget -c
> https://raw.github.com/eewiki/u-boot-patches/master/v2014.04-rc3/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
> --2014-04-11 16:41:52--
> https://raw.github.com/eewiki/u-boot-patches/master/v2014.04-rc3/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
> Resolving raw.github.com (raw.github.com)... 199.27.79.133
> Connecting to raw.github.com (raw.github.com)|199.27.79.133|:443...
> connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 4886 (4.8K) [text/plain]
> Saving to: `0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch'
>
> 100%[>]
> 4,886   --.-K/s   in 0.001s
>
> 2014-04-11 16:41:52 (7.62 MB/s) -
> `0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch' saved [4886/4886]
>
>
> patch -p1 < 0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
> patching file include/configs/am335x_evm.h
> patching file include/configs/ti_armv7_common.h
> victoryred@WorkStation:~/u-boot$ make ARCH=arm CROSS_COMPILE=${CC} distclean
> victoryred@WorkStation:~/u-boot$ make ARCH=arm CROSS_COMPILE=${CC}
> am335x_evm_config
> Configuring for am335x_evm - Board: am335x_evm, Options:
> SERIAL1,CONS_INDEX=1,NAND
> victoryred@WorkStation:~/u-boot$ make ARCH=arm CROSS_COMPILE=${CC}
>   GEN include/autoconf.mk.dep
> cc1: error: bad value (armv5) for -march= switch
>   GEN include/autoconf.mk
> cc1: error: bad value (armv5) for -march= switch
>   CHK include/config/uboot.release
>   UPD include/config/uboot.release
>   CHK include/generated/version_autogenerated.h
>   UPD include/generated/version_autogenerated.h
>   CHK include/generated/timestamp_autogenerated.h
>   UPD include/generated/timestamp_autogenerated.h
>   HOSTCC  scripts/basic/fixdep
>   CC  lib/asm-offsets.s
> lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
> make[1]: *** [lib/asm-offsets.s] Error 1
> make: *** [prepare0] Error 2

Thus you never set "CC" to the cross compiler referenced..

Regards,

-- 
Robert Nelson
http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Bad Linux ARM zImage magic

[Robert Nelson]

On Mon, Apr 14, 2014 at 11:22 AM,   wrote:
> Hi All,
>
> Here's my latest update regarding building a 3.13.9-bone9 bootable image.
> Again, I want to thank Robert Nelson, Jason Kridner and everyone that has
> contributed to the BBB/Debian effort. This was a big improvement for me.
>
> I did get Debian 3.13.9 running last night. I am trying to integrate devices
> with the BBB and it was recommended that in order to complete the
> integration I should perform the build and upgrade. But first I needed to
> put together the cross compiler development platform. I didn't didn't have
> one other than Windows 7, Eclipse, GNU toolchain and Putty. I went the dual
> boot route by adding Ubuntu to may second SSD.
>
> As mentioned above I tried to perform the steps outlined in this link
> http://eewiki.net/display/linuxonarm/BeagleBone . The difficulties I had are
> documented earlier in this thread. Those issues were part of my learning
> curve and having the correct packages loaded in the correct directory
> structure. I own those issues.

Well hat's the wrong page for the BBB and hence why the uEnv.txt did not work..

For the BeagleBone black use:
http://eewiki.net/display/linuxonarm/BeagleBone+Black

Not sure how much clearer i can make it..:
http://eewiki.net/display/linuxonarm/BeagleBone#BeagleBone-uEnv.txtbasedbootscript

Quote: "This will not work on the BeagleBone Black with the default
firmware in eMMC: for that device use: BeagleBone Black"

> However, in those instructions there are patches applied to u-boot. After
> the patch, many environmental variables are set in AM335x_evm.h. Some of
> those variables are load addresses for zImage. Other variables are
> defined/set in uEnv.txt. This was important all day yesterday because u-boot
> wouldn't load the zImage or fdtload. It can become confusing trying to
> understand the uImage/zImage concept when you go back and forth between the
> code and running uboot. BTW, none of this troubleshooting would have been
> possible without at least a serial -> USB converter and Putty running a
> serial connection. Need to learn u-boot as part of the process as well.
> Using printenv and comparing the environmental variables to the values
> defined/set in the u-boot patch (AM335x_evm.h) was insightful.
>
> So, to finish the build discussion, I ended up using ./build_kernel.sh and
> ./install_kernel.sh. I think ./install_kernel.sh is still a work in progress
> as can be determined by looking at the conditional code surrounding zImage.

That's called making the script generic and supporting legacy
platforms.  PS the directions on the wiki never state to use the
"./tools/install_kernel.sh" script, that's cheating.. ;)

> But it works and the pesky edits and cp -v of fstab, inittab et. al. found
> in the '//eewiki.net/' are now included in the shell (build/install). Life
> is simpler for that. Butlet's go back to the patches referenced in
> the '//eewiki.net/' link that are applied to u-boot and also to uEnv.txt.
>
> In a nutshell, variables such as loadaddr are set in AM335x_emv.h if you
> apply the patch. Yet they appear to be changed in uboot when you compare the
> contents of the dump when you perform printenv. It was interesting because
> according to uboot quit with the unable to load zImage running from the
> uEnv.txt command file. Interesting because some of those variables aren't
> defined or set in uEnv.txt and are different than what was defined in the
> u-boot patch. What was more curious was the skeletal uEnv.txt command file
> from the wiki link. At the end of the day, here's how I got things to work.
> I booted my Win7 machine and copied the latest Debian build (v3.8) to one of
> my SD cards. I ran my BBB to check that it worked. Shutdown my BBB and
> removed the card. I rebooted my development platform out of Win7 and into
> Ubuntu. Placed the sdcard into a reader and compared the uEnv.txt file in
> the ~/linux-dev/deploy path against what was on the sdcard. Well, I almost
> fell out of my chair.
>
> I had a "I wonder if" moment and copied the uEnv.txt file from the sdcard
> (w/Debian v3.8) to my desktop and then swapped sdcards (w/Debian v3.13.9)
> and copied the much different  uEnv.txt file from my desktop to the sdcard.
> After placing the sdcard into the BBB I started the BBB. Now everything
> booted correctly (Debian v3.13.9).
>
> I hope that someone benefits from my mistakes and my discoveries.

Regards,

-- 
Robert Nelson
http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Bad Linux ARM zImage magic

[macarr]

Hi All,

Here's my latest update regarding building a 3.13.9-bone9 bootable image.
Again, I want to thank Robert Nelson, Jason Kridner and everyone that has 
contributed to the BBB/Debian effort. This was a big improvement for me.

I did get Debian 3.13.9 running last night. I am trying to integrate 
devices with the BBB and it was recommended that in order to complete the 
integration I should perform the build and upgrade. But first I needed to 
put together the cross compiler development platform. I didn't didn't have 
one other than Windows 7, Eclipse, GNU toolchain and Putty. I went the dual 
boot route by adding Ubuntu to may second SSD.

As mentioned above I tried to perform the steps outlined in this link  
http://eewiki.net/display/linuxonarm/BeagleBone
 . 
The difficulties I had are documented earlier in this thread. Those issues 
were part of my learning curve and having the correct packages loaded in 
the correct directory structure. I own those issues.

However, in those instructions there are patches applied to u-boot. After 
the patch, many environmental variables are set in AM335x_evm.h. Some of 
those variables are load addresses for zImage. Other variables are 
defined/set in uEnv.txt. This was important all day yesterday because 
u-boot wouldn't load the zImage or fdtload. It can become confusing trying 
to understand the uImage/zImage concept when you go back and forth between 
the code and running uboot. BTW, none of this troubleshooting would have 
been possible without at least a serial -> USB converter and Putty running 
a serial connection. Need to learn u-boot as part of the process as well. 
Using printenv and comparing the environmental variables to the values 
defined/set in the u-boot patch (AM335x_evm.h) was insightful.

So, to finish the build discussion, I ended up using ./build_kernel.sh and 
./install_kernel.sh. I think ./install_kernel.sh is still a work in 
progress as can be determined by looking at the conditional code 
surrounding zImage. But it works and the pesky edits and cp -v of fstab, 
inittab et. al. found in the '//eewiki.net/' are now included in the shell 
(build/install). Life is simpler for that. Butlet's go back to the 
patches referenced in the '//eewiki.net/' link that are applied to u-boot 
and also to uEnv.txt.

In a nutshell, variables such as loadaddr are set in AM335x_emv.h if you 
apply the patch. Yet they appear to be changed in uboot when you compare 
the contents of the dump when you perform printenv. It was interesting 
because according to uboot quit with the unable to load zImage running from 
the uEnv.txt command file. Interesting because some of those variables 
aren't defined or set in uEnv.txt and are different than what was defined 
in the u-boot patch. What was more curious was the skeletal uEnv.txt 
command file from the wiki link. At the end of the day, here's how I got 
things to work. I booted my Win7 machine and copied the latest Debian build 
(v3.8) to one of my SD cards. I ran my BBB to check that it worked. 
Shutdown my BBB and removed the card. I rebooted my development platform 
out of Win7 and into Ubuntu. Placed the sdcard into a reader and compared 
the uEnv.txt file in the ~/linux-dev/deploy path against what was on the 
sdcard. Well, I almost fell out of my chair.

I had a "I wonder if" moment and copied the uEnv.txt file from the sdcard 
(w/Debian v3.8) to my desktop and then swapped sdcards (w/Debian v3.13.9) 
and copied the much different  uEnv.txt file from my desktop to the sdcard. 
After placing the sdcard into the BBB I started the BBB. Now everything 
booted correctly (Debian v3.13.9). 

I hope that someone benefits from my mistakes and my discoveries.

-- 
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] Announcement: Power Cape (UPS)

[Ron B.]

Hi Jason, 

Thank you for the comments (and the order!).  The first batch of boards was 
very small due to parts availability.  Still waiting on a zener to come 
back in stock (current estimate is beginning of May).

The cape firmware does currently allow for a timeout to be set that will 
power the BB back on.  The cape also monitors 3V3 so it knows when the BB 
has powered down and then will then cut 5V (and reset the timeout if you've 
set one).  It is my intention to add a RTC to the firmware but I really 
need to create a kernel driver for it to provide the proper RTC interface 
and so that everything else is accessible through sysfs.

I have thought about moving the components to the "bottom" of the board to 
make the top "slick".  I'd probably have to scoot a component or two around 
but that should be completely doable.  These lithium battery packs get 
pretty small.  My final prototype now lives in a Logic Supply case which I 
think is a pretty nice setup.  Without the stacking connectors, the cover 
just needs to be raised one position.  Photo 
here
.

The reason that I put the JST connector onto the cape is because the 
lithium packs from AdaFruit and SparkFun seem to all have them 
pre-installed.  The battery in the pic is from AdaFruit and is 1200mAh.  
That runs an idling BBB for nearly 3 hours!

-Ron

On Monday, April 14, 2014 8:49:37 AM UTC-5, Jason Kridner wrote:
>
> On Fri, Apr 4, 2014 at 11:09 AM, Ron B. > 
> wrote: 
> > Hello fellow enthusiasts, 
> > 
> > Please check out my Power Cape and let me know what you think.  Yes, 
> they 
> > are for sale but I would also value your feedback. 
>
> I seem to have bought the last one in stock with stacking headers. 
>
> Be sure to register your capes on http://beaglebonecapes.com and 
> http://beagleboard.org/project. 
>
> My "dream" power cape would include an RTC and the ability to set 
> alarms to wake-up and/or power-up the board. I also dream of a power 
> cape that would allow the battery and cape to still fit in an Altoids 
> tin, sandwiching the battery between the boards and eliminating any 
> connectors components that would extrude beyond those boundaries. 
> Then, insulating the tin with a non-conductive material would allow 
> for containing a running Bone and I'd just make a cut-out for the USB 
> connectors. 
>
> That said, I really like what you've created, which is why I bought one. 
> :-) 
>
> Do you have a recommended battery supplier? 
>
> > 
> > Thanks, 
> > -Ron 
> > 
> > -- 
> > 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 . 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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] Setting I/O's

[Charles Steinkuehler]

>From the top google hit on "uboot set gpio":

http://e2e.ti.com/support/arm/sitara_arm/f/791/t/248181.aspx

...it's even for a TI Sitara processor.

Executive summary:
Use u-boot commands to directly access memory to turn on the GPIO clock
and setup pinmux and gpio values as desired.

And here's the u-boot documentation page on memory commands:
http://www.denx.de/wiki/view/DULG/UBootCmdGroupMemory#Section_5.9.2.6.

On 4/14/2014 10:09 AM, maartenrik...@gmail.com wrote:
> Dear Gerald,
> 
> Isn't it possible to set the IO's in the U-boot? 
> before the kernel is started.
> This would be fast enough.
> 
> Regards,
> 
> 
> Maarten
> 
> Op maandag 14 april 2014 16:40:16 UTC+2 schreef Gerald:
>>
>> Read the datasheet for the default state of each pin on power up.
>>
>> http://www.ti.com/product/am3358
>>
>> These cannot be changed. Once the SW is loaded, it can set the pins to 
>> whatever function it supports.
>>
>> Gerald
>>
>>
>>
>> On Mon, Apr 14, 2014 at 9:37 AM, >wrote:
>>
>>> Dear Reader,
>>>
>>> I have a question about the following problem.
>>> On the PCB I designed I use the BBB for setting some pumps and valves.
>>> When the system starts up the first seconds the IO pins are not logic 1 
>>> or 0.
>>> Is it possible to set the GPIO's in U-boot before starting up the kernel 
>>> and how can I do this?
>>>
>>> Thanks,
>>>
>>> Maarten
>>>
>>>  -- 
>>> 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 .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
> 


-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] Setting I/O's

[Gerald Coley]

Possibly. Not sure if Linux would like that or not. I would think it would
have to be a custom UBoot just for your use in that case.

Gerald



On Mon, Apr 14, 2014 at 10:09 AM,  wrote:

> Dear Gerald,
>
> Isn't it possible to set the IO's in the U-boot?
> before the kernel is started.
> This would be fast enough.
>
> Regards,
>
>
> Maarten
>
> Op maandag 14 april 2014 16:40:16 UTC+2 schreef Gerald:
>>
>> Read the datasheet for the default state of each pin on power up.
>>
>> http://www.ti.com/product/am3358
>>
>> These cannot be changed. Once the SW is loaded, it can set the pins to
>> whatever function it supports.
>>
>> Gerald
>>
>>
>>
>> On Mon, Apr 14, 2014 at 9:37 AM,  wrote:
>>
>>> Dear Reader,
>>>
>>> I have a question about the following problem.
>>> On the PCB I designed I use the BBB for setting some pumps and valves.
>>> When the system starts up the first seconds the IO pins are not logic 1
>>> or 0.
>>> Is it possible to set the GPIO's in U-boot before starting up the kernel
>>> and how can I do this?
>>>
>>> Thanks,
>>>
>>> Maarten
>>>
>>>  --
>>> 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.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> 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.
>

-- 
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] Setting I/O's

[maartenrikhof]

Dear Gerald,

Isn't it possible to set the IO's in the U-boot? 
before the kernel is started.
This would be fast enough.

Regards,


Maarten

Op maandag 14 april 2014 16:40:16 UTC+2 schreef Gerald:
>
> Read the datasheet for the default state of each pin on power up.
>
> http://www.ti.com/product/am3358
>
> These cannot be changed. Once the SW is loaded, it can set the pins to 
> whatever function it supports.
>
> Gerald
>
>
>
> On Mon, Apr 14, 2014 at 9:37 AM, >wrote:
>
>> Dear Reader,
>>
>> I have a question about the following problem.
>> On the PCB I designed I use the BBB for setting some pumps and valves.
>> When the system starts up the first seconds the IO pins are not logic 1 
>> or 0.
>> Is it possible to set the GPIO's in U-boot before starting up the kernel 
>> and how can I do this?
>>
>> Thanks,
>>
>> Maarten
>>
>>  -- 
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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] spi-omap2-mcspi hangs when DMA and PIO are used simultaneously

[Jack Mitchell]

On 14/04/14 14:50, jorge.araujo.vent...@gmail.com wrote:
> I am using spi-omap2-mcspi to drive a network card based on enc28j60 and
> everything works perfect if I define
> DMA_MIN_BYTES = 0 (force to use DMA only) or DMA_MIN_BYTES = 9
> (force to use PIO only).
> But if I use the original value of 160, the board can send out 10 to 20
> pings approximately
> and if any time the drive switch from PIO to DMA what will be decided by
> the size of data,
> some workqueue tasks hung and the card stops.
> 
> I am using the kernel 3.13.6 patched to beaglebone and did test also
> with the mainline 3.14.0 and the problem is exactly the same.
> 
> I am running with "lockdep" and "detect hung tasks" and I can see that
> four tasks are stopped,
> three from enc28j60 and one from spi-omap2-mcspi.
> 
> The mcspi is stopped in spi-omap2.mcspi.c:480 to wait the completion of
> omap2_mcspi_rx_callback
> that it never happens.
> 
> |468 ||if| |(tx) { |
> |469 tx->callback = omap2_mcspi_rx_callback; |
> |470 tx->callback_param = spi; |
> |471 dmaengine_submit(tx); |
> |472 } ||else| |{ |
> |473 ||/* FIXME: fall back to PIO? */|||
> |474 } |
> |475 } |
> |476 |
> |477 dma_async_issue_pending(mcspi_dma->dma_rx); |
> |478 omap2_mcspi_set_dma_req(spi, 1, 1); |
> |479 |
> |480 wait_for_completion(&mcspi_dma->dma_rx_completion); |
> |481 dma_unmap_single(mcspi->dev, xfer->rx_dma, count, |
> |482  DMA_FROM_DEVICE);|
> 
> 
> Any help/suggestion is welcome. Need more information, please let me
> know, I have more details.
> 
> Thank you.
> 

You might want to also try sending this to the linux-omap list as it's a
bug in mainline too. I know TI are shouting from the rooftops about
using the mainline kernel at the moment so you might be able to leverage
that to get some help.

Good luck!

Cheers,


-- 
  Jack Mitchell (j...@embed.me.uk)
  Embedded Systems Engineer
  Cambridgeshire, UK
  http://www.embed.me.uk
-- 

-- 
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: Using i2c channel without recompiling the kernel

[Joshua Datko]

The bus names are a bit confusing, but the BBB's i2c-2, on pins P19/20,
can be sometimes labeled i2c-1 in Linux.

Anyway, this usually does the trick to get the third i2c bus:

root@arm:~# echo BB-I2C1 > /sys/devices/bone_capemgr.8/slots
root@arm:~# ls -l /sys/bus/i2c/devices/i2c-*
lrwxrwxrwx 1 root root 0 Nov  3 21:49 /sys/bus/i2c/devices/i2c-0 -> 
../../../devices/ocp.2/44e0b000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Nov  3 21:49 /sys/bus/i2c/devices/i2c-1 -> 
../../../devices/ocp.2/4819c000.i2c/i2c-1
lrwxrwxrwx 1 root root 0 Nov  3 21:50 /sys/bus/i2c/devices/i2c-2 -> 
../../../devices/ocp.2/4802a000.i2c/i2c-2

I did a blog post about it here: http://datko.net/2013/11/03/bbb_i2c/

Josh


-- 
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] Setting I/O's

[Gerald Coley]

Read the datasheet for the default state of each pin on power up.

http://www.ti.com/product/am3358

These cannot be changed. Once the SW is loaded, it can set the pins to
whatever function it supports.

Gerald



On Mon, Apr 14, 2014 at 9:37 AM,  wrote:

> Dear Reader,
>
> I have a question about the following problem.
> On the PCB I designed I use the BBB for setting some pumps and valves.
> When the system starts up the first seconds the IO pins are not logic 1 or
> 0.
> Is it possible to set the GPIO's in U-boot before starting up the kernel
> and how can I do this?
>
> Thanks,
>
> Maarten
>
>  --
> 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.
>

-- 
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] Setting I/O's

[maartenrikhof]

Dear Reader,

I have a question about the following problem.
On the PCB I designed I use the BBB for setting some pumps and valves.
When the system starts up the first seconds the IO pins are not logic 1 or 
0.
Is it possible to set the GPIO's in U-boot before starting up the kernel 
and how can I do this?

Thanks,

Maarten

-- 
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] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Gerald Coley]

 If anyone wants to take my place on dealing with my frustration on this
side of the issue, I will gladly let them. Any takers?

Gerald



On Mon, Apr 14, 2014 at 12:53 AM, Anil Gupta wrote:

> The comments by Hannes are reflective of his frustration with
> availability, so I would take them in that spirit.
>
> A lot of people are working hard to address BBB supply.  So I am sure at
> some point, we will hear of increased supply which will reduce frustration.
>
> Hannes: I don't know of the entire landscape of Linux boards but we have
> extensively tested boards by Olimex.  www.olimex.com  Although we prefer
> BBB, we felt that Olimex has reasonably priced, industrial quality
> products.   Maybe they have something that is a fit for you.
>
>
> On Mon, Apr 14, 2014 at 10:37 AM, William Hermans wrote:
>
>> You come onto the beagleboard forums, make rude remarks to as how you
>> think it should be available, and expect someone to help you ?
>>
>> That takes brass. Good luck.
>>
>>
>> On Sat, Apr 12, 2014 at 7:03 AM,  wrote:
>>
>>>  I checked every store in EU and US I could find to get a BBB, there is
>>> no single one available worldwide.
>>> That's such a joke ..
>>> Oh well I can get them on ebay, for 999 EUR (1400 USD) per piece.
>>>
>>> The whole release management of that product is a big fail, listing 20
>>> stores and all of them have no availablility ..
>>>
>>> --
>>>
>>> I don't want to bet on a product which is not available fo rmonths when
>>> I need it.
>>> Is there a good replacement to BBB ? Should have about the same
>>> performance and many pinouts.
>>>
>>>  --
>>> 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.
>>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/Z3JfUIkxOl8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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.
>

-- 
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] what might happened to my BBB?

[Gerald Coley]

I would suggest an RMA to see what happened.

http://www.elinux.org/Beagleboard:BeagleBoneBlack


Gerald



On Mon, Apr 14, 2014 at 8:47 AM, zhiyong zhan  wrote:

> When I tried my HDMI cable, plugged it in. and also with a 5V2A power
> supply, it works.
> But when I plugged in a apple keyboard through the USB host, the power
> just turned off.
> And now it just gives a response of a blink of power led when I plug in
> the power.
> What can I do? only RMA?
>
> --
> 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.
>

-- 
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 ADC

[andreu . blasco]

Hello,

I'm using beaglebone black to acquire data from a radar sensor. I have  
angstrom distribution (3.8.13). I want to use the ADC for the  
conversion and a dmtimer (timer7) to control it.


In the technical reference manual I found that there is a register to  
select the source for the conversion (adc_evt_capt) in the control  
module. The problem is that only in privileged mode it is possible to  
write the registers of the control module.


How can I change this register to select timer7 as the input of the  
ext_hw_event?


Thanks,

Andreu Blasco

--
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] LCD capacitive driver for FT5x06

[dario . cogliati79]

Hi,

I'm trying to interface my BBB with a 4,3'' capacitive LCD 
(NHD-4.4-480272EF-ATXL-CTP) using LCD4 cape that is hardaware prapared to 
connect capacitive LCD with the I2C interface. 

When boot my BBB, it detects LCD4 cape through the EEprom memory and it 
load coorectly BB-BONE-LCD4-A001.dtbo overlay binariy file that contains the 
configuration for the resistive Touch LCD. Now i have to modify that file 
to describe  the interface of my capacitive LCD that differs only for the 
i2c interface to communicate touch points. 

I have found the kernel driver that communicate with the i2c controller 
(FT5x06) of the LCD, it is place in 
/lib/modules/3.8.13/kernel/drive/input/touchscreen/edt-ft5x06.ko but before 
I have to load a correct DTS fbut i can't find it.

Can someone help me to resolve this problem?

Thanks 

Dario 

-- 
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] spi-omap2-mcspi hangs when DMA and PIO are used simultaneously

[jorge.araujo.vent...@gmail.com]

I am using spi-omap2-mcspi to drive a network card based on enc28j60 and 
everything works perfect if I define
DMA_MIN_BYTES = 0 (force to use DMA only) or DMA_MIN_BYTES = 9 (force 
to use PIO only).
But if I use the original value of 160, the board can send out 10 to 20 
pings approximately
and if any time the drive switch from PIO to DMA what will be decided by 
the size of data,
some workqueue tasks hung and the card stops.
I am using the kernel 3.13.6 patched to beaglebone and did test also with 
the mainline 3.14.0 and the problem is exactly the same.

I am running with "lockdep" and "detect hung tasks" and I can see that four 
tasks are stopped,
three from enc28j60 and one from spi-omap2-mcspi.

The mcspi is stopped in spi-omap2.mcspi.c:480 to wait the completion of 
omap2_mcspi_rx_callback
that it never happens.

468 if (tx) { 
469 tx->callback = omap2_mcspi_rx_callback; 
470 tx->callback_param = spi; 
471 dmaengine_submit(tx); 
472 } else { 
473 /* FIXME: fall back to PIO? */ 
474 } 
475 } 
476 
477 dma_async_issue_pending(mcspi_dma->dma_rx); 
478 omap2_mcspi_set_dma_req(spi, 1, 1); 
479 
480 wait_for_completion(&mcspi_dma->dma_rx_completion); 
481 dma_unmap_single(mcspi->dev, xfer->rx_dma, count, 
482  DMA_FROM_DEVICE);


















Any help/suggestion is welcome. Need more information, please let me know, 
I have more details.

Thank you.

-- 
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] Re: Availability - how come nobody has any BeagleBone Black to sell?

[Anil Gupta]

The comments by Hannes are reflective of his frustration with availability,
so I would take them in that spirit.

A lot of people are working hard to address BBB supply.  So I am sure at
some point, we will hear of increased supply which will reduce frustration.

Hannes: I don't know of the entire landscape of Linux boards but we have
extensively tested boards by Olimex.  www.olimex.com  Although we prefer
BBB, we felt that Olimex has reasonably priced, industrial quality
products.   Maybe they have something that is a fit for you.


On Mon, Apr 14, 2014 at 10:37 AM, William Hermans  wrote:

> You come onto the beagleboard forums, make rude remarks to as how you
> think it should be available, and expect someone to help you ?
>
> That takes brass. Good luck.
>
>
> On Sat, Apr 12, 2014 at 7:03 AM,  wrote:
>
>> I checked every store in EU and US I could find to get a BBB, there is no
>> single one available worldwide.
>> That's such a joke ..
>> Oh well I can get them on ebay, for 999 EUR (1400 USD) per piece.
>>
>> The whole release management of that product is a big fail, listing 20
>> stores and all of them have no availablility ..
>>
>> --
>>
>> I don't want to bet on a product which is not available fo rmonths when I
>> need it.
>> Is there a good replacement to BBB ? Should have about the same
>> performance and many pinouts.
>>
>>  --
>> 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.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/Z3JfUIkxOl8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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] Announcement: Power Cape (UPS)

[Jason Kridner]

On Fri, Apr 4, 2014 at 11:09 AM, Ron B.  wrote:
> Hello fellow enthusiasts,
>
> Please check out my Power Cape and let me know what you think.  Yes, they
> are for sale but I would also value your feedback.

I seem to have bought the last one in stock with stacking headers.

Be sure to register your capes on http://beaglebonecapes.com and
http://beagleboard.org/project.

My "dream" power cape would include an RTC and the ability to set
alarms to wake-up and/or power-up the board. I also dream of a power
cape that would allow the battery and cape to still fit in an Altoids
tin, sandwiching the battery between the boards and eliminating any
connectors components that would extrude beyond those boundaries.
Then, insulating the tin with a non-conductive material would allow
for containing a running Bone and I'd just make a cut-out for the USB
connectors.

That said, I really like what you've created, which is why I bought one. :-)

Do you have a recommended battery supplier?

>
> Thanks,
> -Ron
>
> --
> 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.

-- 
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] what might happened to my BBB?

[zhiyong zhan]

When I tried my HDMI cable, plugged it in. and also with a 5V2A power 
supply, it works.
But when I plugged in a apple keyboard through the USB host, the power just 
turned off.
And now it just gives a response of a blink of power led when I plug in the 
power.
What can I do? only RMA? 

-- 
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] BBIOConfig -> BB universal IO UI testing release

[Jason Kridner]

On Mon, Apr 14, 2014 at 8:19 AM,  wrote:

> Hello BeagleBone community,
>
> I have created a UI for Charles BB universal IO tool that will be part of
> the upcoming Debian image release. Please test and provide feedback. You
> can find binaries for Linux, Mac and Windows here:
> https://github.com/strahlex/BBIOConfig/releases
>

Thanks for this great contribution. Glad to have you as part of the
community!


>
>
> For a short introduction take a look at the wiki:
> https://github.com/strahlex/BBIOConfig/wiki/User-Manual
>
>
> 
>
>
>
> Regards
> Strahlex
>
> --
> 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.
>

-- 
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] Suggestion for change to Beaglebone PCB: USB header

[CEinTX]

Even though this might violate the spirit of the specification, it is highly
likely this will work. Most PCBs that use differential signals are very 
loosely
coupled by the nature of the traces having to be side by side. The traces 
can
wander quite a bit and still maintain a reasonably close differential 
impedance.
The more important aspect is to maintain a matched distance. Depending on
which speed of USB that you want support for, this can easily be achieved 
even
going through a header - as even this doesn't have to be that precise.
Consider this, just about every motherboard in existence has USB port 
headers
to go to a ISA/PCI/PICe slot connector. All of these go to a ribbon cable 
with two
insulation displacement connectors - one at each end. These surprisingly 
work
well for most PC users - go figure - even with all the changes in impedance.
I suspect a 1/2" or so header won't be as much of a challenge.
Doesn't sound like Gerald has any intention to make this change anyway, but
if someone wanted to try this as an option for their own board, with 
planning, it
should be workable.

On Monday, April 14, 2014 4:06:46 AM UTC-5, john3909 wrote:
>
>
> On 4/13/14, 8:52 AM, "brem...@gmail.com " 
> > 
> wrote: 
>
> >I have to say that USB connection accesible from the side headers would 
> >be really nice feature. I aggre that you can loop a regular usb cable, 
> >but this way makes ot more robust and that just doesnt look good. Imagine 
> >someone buildibg a device basing on bbb. Everything could be connected to 
> >the cape and all a worker has to do is place the bbb on the cape. 
> USB uses differential signaling with controlled impedance. The connectors 
> used for the capes would violate this specification and cannot support USB 
> signaling. 
>
> Regards, 
> John 
> > 
> > 
> >I vote for this as well ;) 
> > 
> >-- 
> >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 . 
> >For more options, visit https://groups.google.com/d/optout. 
>
>
>

-- 
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 not booting if connected to buffer IC 74AVC16T245

[Kishor Dhanawade]

Hello Eric and Gerald,
 Thank you very much for your guidance. I solved the problem.
Eric you are absolutely correct. I followed your instructions and I am very
glad that my hardware is working properly with 7" lcd display. Thanks a
lot.. :)

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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Announcement: Power Cape (UPS)

[mail . aroessler]

Looks interesting for building a robot.

Am Freitag, 4. April 2014 17:09:17 UTC+2 schrieb Ron B.:
>
> Hello fellow enthusiasts,
>
> Please check out my Power 
> Capeand let me know what you 
> think.  Yes, they are for sale but I would also 
> value your feedback.
>
> Thanks,
> -Ron
>
>

-- 
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] BBIOConfig -> BB universal IO UI testing release

[Charles Steinkuehler]

On 4/14/2014 7:19 AM, mail.aroess...@gmail.com wrote:
> Hello BeagleBone community,
> 
> I have created a UI for Charles BB universal IO tool that will be part of 
> the upcoming Debian image release. Please test and provide feedback. You 
> can find binaries for Linux, Mac and Windows here:
> https://github.com/strahlex/BBIOConfig/releases
> 
> For a short introduction take a look at the wiki: 
> https://github.com/strahlex/BBIOConfig/wiki/User-Manual
> 
> 

If you have ever had problems with pin multiplexing on the BeagleBone,
check out this application!

My universal cape overlay and pin configuration utility make it possible
to set most every BBB pin to do what you want.  Alexander's GUI
application gives you a visual and easy to edit method of creating a pin
configuration.  Just click on the pins to set them up like you want,
then take the generated text file and feed it into my config-pin utility.

Thanks for the great work Alexander!

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] BBIOConfig -> BB universal IO UI testing release

[mail . aroessler]

Hello BeagleBone community,

I have created a UI for Charles BB universal IO tool that will be part of 
the upcoming Debian image release. Please test and provide feedback. You 
can find binaries for Linux, Mac and Windows here:
https://github.com/strahlex/BBIOConfig/releases

For a short introduction take a look at the wiki: 
https://github.com/strahlex/BBIOConfig/wiki/User-Manual





Regards
Strahlex

-- 
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] Re: Dude, where's my BeagleBone Black?

[Robert Berger]

Hi,
>>
>> I mean can I take an SD card which runs on a  Circuitco BBB and expect this
>> to work on an Embest BB Black?
> 
> Yes.


OK thanks!

> 
>>
>> BTW I will do a webinar "From Arduino Uno to BeagleBone Black (and back)![1]
>> on 17th and such a question might arise.
> 
> Sounds interesting. Will you talk about stuff like Userspace Arduino
> and using the PRUs?

Not really. It's just 30 min ;)

For the average Embedded software person it's quite painful to create
(or let others create) prototyping hardware in order to write software
which talks to sensors and actuators. On the one hand it's quite
straightforward to build up some hardware and write test software with
libraries available for the Arduino UNO, on the other hand it's not that
easy to do the same thing "right" in Embedded Linux. Wouldn't it be nice
to reuse this tested hardware prototype and write code for Embedded
Linux to talk to it? I intentionally don't want to use Arduino wrapping
libraries on Linux since those are typically not industrial strength,
but targeted towards hobbyists. This is what's going to be presented
here. BTW the prototyping hardware is not only able to convert signal
levels from an Arduino UNO (shield) to a Beagle Bone, but also to
convert signal levels from a Beagle Bone (cape) to an Arduino UNO if
that's needed.

> 
>>
>> Regards,
>>
>> Robert
>>
>> [1] http://www.element14.com/community/events/4021
>>
>>
>>
>>
>> --
>> 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.
> 

-- 
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] Re: Dude, where's my BeagleBone Black?

[Jason Kridner]

On Mon, Apr 14, 2014 at 3:41 AM, Micka  wrote:
> Well I can't agree more with you ... I'm not using the eMMC because I need
> the pins that the eMMC use  .
>
> Why not only using sdcard ? it's much more easy to programm the BBB with
> sdcard than with eMMC ... .


There certainly is a value to going back to no eMMC, but the
reliability, performance and cost advantages make it more practical
for the standard BeagleBone Black.


>
>
> On Mon, Apr 14, 2014 at 9:25 AM, rh_  wrote:
>>
>> On Sun, 13 Apr 2014 19:07:00 -0400
>> Jason Kridner  wrote:
>>
>> --8<--
>>
>> > To provide the best experience of using Debian on BeagleBone Black, we
>> > are connecting the switch-over to an increase in the on-board eMMC
>> > flash storage from 2GB to 4GB, leaving more free room in which you can
>> > work. The eMMC is faster and more reliable than micro-SD cards, so
>> > this is adding a lot of value---and a little bit of cost.
>> >
>> > These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev C
>> > and they will likely cost a bit more at most distributors. This extra
>> > money is helping CircuitCo pay for the additional expense of the eMMC,
>> > but also to cover costs for ramping production to higher-than-ever
>> > rates.
>> >
>> > With the additional capacity CircuitCo is bringing on, we expect to be
>> > able to fill all end-user back-orders for the Rev B boards by early
>> > May and shift all production to Rev C. With around 150,000 boards on
>> > *distributor* back-orders, we'll be working with distributors to
>> > quickly accept board shipments such that CircuitCo isn't sitting on
>> > any units.
>> >
>>
>> So no more 2GB eMMC models ever?  What about one with no eMMC
>> at all? I know there are more than a few people here that boot from
>> network, sdcard or usb.
>>
>> Another thought occurred, has beagle or circuitco done any long duration
>> eMMC testing? How graceful will the BBB handle a failed eMMC part?
>> Failed as-in worn out from use not a defect. I think some people are
>> concerned with eMMC failures and so they don't use it or don't rely
>> on it.
>>
>> --
>> 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.
>
>
> --
> 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.

-- 
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] Dude, where's my BeagleBone Black?

[Jason Kridner]

On Mon, Apr 14, 2014 at 5:01 AM, Charles Steinkuehler
 wrote:
> On 4/14/2014 12:11 AM, Jason Kridner wrote:
>> On Sunday, April 13, 2014 8:03:56 PM UTC-4, William Hermans wrote:
>>>
>>> Good information and thank you Jason for sharing. I see there is also
>>> someone else producing miniature versions of the BBB, but . . . not my own
>>> thing.
>>
>> Who and what?
>
> SoM version of BeagleBone:
> http://www.mentorel.com/product/usomiq-am335x/

Looks pretty cool, thanks. Another win for open hardware!

>
> From this post:
> https://groups.google.com/d/msg/beagleboard/KCr_Sm8tP_o/6YVEfI8Dc-4J

Sorry I missed it.

>
> --
> Charles Steinkuehler
> char...@steinkuehler.net
>
> --
> 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.

-- 
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] Re: Dude, where's my BeagleBone Black?

[Jason Kridner]

On Mon, Apr 14, 2014 at 3:25 AM, rh_  wrote:
> On Sun, 13 Apr 2014 19:07:00 -0400
> Jason Kridner  wrote:
>
> --8<--
>
>> To provide the best experience of using Debian on BeagleBone Black, we
>> are connecting the switch-over to an increase in the on-board eMMC
>> flash storage from 2GB to 4GB, leaving more free room in which you can
>> work. The eMMC is faster and more reliable than micro-SD cards, so
>> this is adding a lot of value---and a little bit of cost.
>>
>> These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev C
>> and they will likely cost a bit more at most distributors. This extra
>> money is helping CircuitCo pay for the additional expense of the eMMC,
>> but also to cover costs for ramping production to higher-than-ever
>> rates.
>>
>> With the additional capacity CircuitCo is bringing on, we expect to be
>> able to fill all end-user back-orders for the Rev B boards by early
>> May and shift all production to Rev C. With around 150,000 boards on
>> *distributor* back-orders, we'll be working with distributors to
>> quickly accept board shipments such that CircuitCo isn't sitting on
>> any units.
>>
>
> So no more 2GB eMMC models ever?  What about one with no eMMC
> at all? I know there are more than a few people here that boot from
> network, sdcard or usb.

Never say never, but we are unlikely to make any more 2GB eMMC models.
I've been kicking around the idea of doing a kickstarter for a no-eMMC
model, but I'd like to wait a month or two to see how the Rev C and
Element14 boards are doing out there.

>
> Another thought occurred, has beagle or circuitco done any long duration
> eMMC testing? How graceful will the BBB handle a failed eMMC part?
> Failed as-in worn out from use not a defect. I think some people are
> concerned with eMMC failures and so they don't use it or don't rely
> on it.

The only data we have is from the manufacturer and the community.
After a year, we aren't seeing wear-out issues. The ext4 file system
if fairly robust, but if writes start failing, end-user failures can
occur in odd ways. If you are creating a mission-critical app that
must stay deployed for many years without the ability to perform
replacements, I'd encourage you to alter the eMMC contents to
read-only, except for your critical data acquisition.

>
> --
> 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.

-- 
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] Re: Dude, where's my BeagleBone Black?

[Jason Kridner]

On Mon, Apr 14, 2014 at 2:59 AM, robert.berger
 wrote:
> Hi Jason,
>
>
> On Monday, April 14, 2014 2:07:00 AM UTC+3, Jason Kridner wrote:
>>
>> Just about to post this to http://beagleboard.org/blog, but it
>> wouldn't hurt to get a bit of community feedback before pushing this
>> out there
>
>
> What I would be interested is software (binary) compatibility between the
> Circuitco BBB and the Embest BB Black.
> I can't find it right now, but Rob Nelson mentioned something like "only
> supports the Circuitco Version".

Before switching to the "Element14 BeagleBone Black" branded boards,
they sold off some of their older stock which had some really old
firmware on it. It was determined that the really old firmware was to
blame for Robert's code not booting. Reflashing the board solved the
issue.

>
> Can you please enlighten me a bit on possible differences which require
> software adjustments?

There are none. Future boards should line up with the same software
version we deliver to CircuitCo.

>
> I mean can I take an SD card which runs on a  Circuitco BBB and expect this
> to work on an Embest BB Black?

Yes.

>
> BTW I will do a webinar "From Arduino Uno to BeagleBone Black (and back)![1]
> on 17th and such a question might arise.

Sounds interesting. Will you talk about stuff like Userspace Arduino
and using the PRUs?

>
> Regards,
>
> Robert
>
> [1] http://www.element14.com/community/events/4021
>
>
>
>
> --
> 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.

-- 
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] Suggestion for change to Beaglebone PCB: USB header

[John Syn]

On 4/13/14, 8:52 AM, "breme...@gmail.com"  wrote:

>I have to say that USB connection accesible from the side headers would
>be really nice feature. I aggre that you can loop a regular usb cable,
>but this way makes ot more robust and that just doesnt look good. Imagine
>someone buildibg a device basing on bbb. Everything could be connected to
>the cape and all a worker has to do is place the bbb on the cape.
USB uses differential signaling with controlled impedance. The connectors
used for the capes would violate this specification and cannot support USB
signaling. 

Regards,
John
> 
>
>I vote for this as well ;)
>
>-- 
>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.


-- 
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] Dude, where's my BeagleBone Black?

[Charles Steinkuehler]

On 4/14/2014 12:11 AM, Jason Kridner wrote:
> On Sunday, April 13, 2014 8:03:56 PM UTC-4, William Hermans wrote:
>>
>> Good information and thank you Jason for sharing. I see there is also 
>> someone else producing miniature versions of the BBB, but . . . not my own 
>> thing.
> 
> Who and what?

SoM version of BeagleBone:
http://www.mentorel.com/product/usomiq-am335x/

>From this post:
https://groups.google.com/d/msg/beagleboard/KCr_Sm8tP_o/6YVEfI8Dc-4J

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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] [BBB] TI SDK7 and linux 3.12 on github, any difference?

[Grissiom]

Hi all,

TI has released the AM335XSDK7
http://software-dl.ti.com/sitara_linux/esd/AM335xSDK/latest/index_FDS.htmlrecently,
which ships the Linux 3.12 kernel. Can someone sum up the
difference between the "offical" version of Linux 3.12 and the github
version (https://github.com/beagleboard/kernel/tree/3.12) of Linux 3.12?

-- 
Cheers,
Grissiom

-- 
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] Re: Dude, where's my BeagleBone Black?

[Bas Laarhoven]

Robert,

The Embest board I received from Farnell last week ago has been used in 
my BeBoPr++ production test system and I have not experienced any 
incompatibilities.


As I posted earlier, the Angstrom software on the board was identical to 
that on a original rev B BBB. The only differences discovered thus far 
are mechanical and quality related. I replaced Angstrom with the Debian 
trial image and have had no problems (other than those that were present 
on the original BBB too).


The on-board EEPROM contents differ and can be used to identify the 
boards if needed:


Embest:

000 aa 55 33 ee 41 33 33 35 42 4e 4c 54 30 30 41 35
020 33 30 30 31 42 42 42 4b 39 36 30 30 58 41 58 58
040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
060 30 31 32 33 34 35 36 37 38 39 41 42 43 44 45 46
100 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

strings: "A335BNLT00A53001BBBK9600XAXX" "0123456789ABCDEF"

BBB:
000 aa 55 33 ee 41 33 33 35 42 4e 4c 54 30 30 30 42
020 31 30 31 34 42 42 42 4b 31 30 39 33 ff ff ff ff
040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
100 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

strings: "A335BNLT000B1014BBBK1093"

Except from that, both boards seem identical from a software point of view.

-- Bas


On 14-4-2014 8:59, robert.berger wrote:

Hi Jason,

On Monday, April 14, 2014 2:07:00 AM UTC+3, Jason Kridner wrote:

Just about to post this to http://beagleboard.org/blog, but it
wouldn't hurt to get a bit of community feedback before pushing this
out there


What I would be interested is software (binary) compatibility between 
the Circuitco BBB and the Embest BB Black.
I can't find it right now, but Rob Nelson mentioned something like 
"only supports the Circuitco Version".


Can you please enlighten me a bit on possible differences which 
require software adjustments?


I mean can I take an SD card which runs on a  Circuitco BBB and expect 
this to work on an Embest BB Black?


BTW I will do a webinar "From Arduino Uno to BeagleBone Black (and 
back)![1] on 17th and such a question might arise.


Regards,

Robert

[1] http://www.element14.com/community/events/4021





--
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.


--
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] Re: Dude, where's my BeagleBone Black?

[Micka]

Well I can't agree more with you ... I'm not using the eMMC because I need
the pins that the eMMC use  .

Why not only using sdcard ? it's much more easy to programm the BBB with
sdcard than with eMMC ... .


On Mon, Apr 14, 2014 at 9:25 AM, rh_  wrote:

> On Sun, 13 Apr 2014 19:07:00 -0400
> Jason Kridner  wrote:
>
> --8<--
>
> > To provide the best experience of using Debian on BeagleBone Black, we
> > are connecting the switch-over to an increase in the on-board eMMC
> > flash storage from 2GB to 4GB, leaving more free room in which you can
> > work. The eMMC is faster and more reliable than micro-SD cards, so
> > this is adding a lot of value---and a little bit of cost.
> >
> > These BeagleBone Blacks with Debian and 4GB eMMC will be called Rev C
> > and they will likely cost a bit more at most distributors. This extra
> > money is helping CircuitCo pay for the additional expense of the eMMC,
> > but also to cover costs for ramping production to higher-than-ever
> > rates.
> >
> > With the additional capacity CircuitCo is bringing on, we expect to be
> > able to fill all end-user back-orders for the Rev B boards by early
> > May and shift all production to Rev C. With around 150,000 boards on
> > *distributor* back-orders, we'll be working with distributors to
> > quickly accept board shipments such that CircuitCo isn't sitting on
> > any units.
> >
>
> So no more 2GB eMMC models ever?  What about one with no eMMC
> at all? I know there are more than a few people here that boot from
> network, sdcard or usb.
>
> Another thought occurred, has beagle or circuitco done any long duration
> eMMC testing? How graceful will the BBB handle a failed eMMC part?
> Failed as-in worn out from use not a defect. I think some people are
> concerned with eMMC failures and so they don't use it or don't rely
> on it.
>
> --
> 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.
>

-- 
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] Running BeagleBone without MicroSD: Need quick reply

[Yiling Cao]

maybe not.


On Sat, Apr 12, 2014 at 7:37 PM, Anon123  wrote:

> I forgot to buy a microSD
>
> Can and how do i run angstrom without MicroSD? I have microUSB.
>
> --
> 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.
>

-- 
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: Dude, where's my BeagleBone Black?

[robert.berger]

Hi Jason,

On Monday, April 14, 2014 2:07:00 AM UTC+3, Jason Kridner wrote:
>
> Just about to post this to http://beagleboard.org/blog, but it 
> wouldn't hurt to get a bit of community feedback before pushing this 
> out there 
>
 
What I would be interested is software (binary) compatibility between the 
Circuitco BBB and the Embest BB Black.
I can't find it right now, but Rob Nelson mentioned something like "only 
supports the Circuitco Version".

Can you please enlighten me a bit on possible differences which require 
software adjustments?

I mean can I take an SD card which runs on a  Circuitco BBB and expect this 
to work on an Embest BB Black?

BTW I will do a webinar "From Arduino Uno to BeagleBone Black (and 
back)![1] on 17th and such a question might arise.

Regards,

Robert

[1] http://www.element14.com/community/events/4021



-- 
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.