[beagleboard] Power supply for BBB

[magu_]

 

Hey

I would like to design the power supply for my BBB. The primary power 
source is a battery and therefore not constant - depending on 
load/remaining charge/hooked up to power supply etc...

 

The task is to measure the primary voltage and to supply the board from it. 
The support will be achieved by a constant output 5V piece. 

The Voltage supervision must only work between 8-15V - therefore I 
introduce a voltage splitter to bring it down to 1.8 V (or let's say 1.5 to 
be on the safe side). Since there can voltage ripple up to 20 V I want to 
protect the ADC and put a Z-Diode in scheme.




Now the questions come:

- Would you design it accordingly or do I miss something important?
- I couldn't find any values on the current drain of the AIN - I kind of 
need that value to scale the resistors.
- Is the Z-Diode fast enough or do I need to introduce some "inertia" by 
butting a coil in front of AIN?

Thank you already in advance for some inside

yours
magu_

-- 
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/groups/opt_out.

[beagleboard] Re: Modbus

[Riccardo Fracassi]

> Thanks Garyamort for the indications.  
> I owe first to verify the typology of the EtherCat and the libmodbus to 
> have explanations on the use.  
> Indeed the use of the modbus consists in the encapsulation as you have 
> specified  
> The other instructions will be me useful to try with the new versions 
> hoping to succeed in getting anything.  
> To the moment I again thank you for the attention  
> Hi  
> Riccardo  
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] device tree support

[Saransh Jain]

Hello RobertCNelson,

I may be wrong here, but I thought that u-boot was responsible for the 
loadaddress of the zimage.In the u-boot patches. there is a loadzimage 
command which has the loadaddress as one of its arguments.So how does the 
soc know the address?
Also if this is the case the only problem I see with uImage is one extra 
step of making it.
Kindly clarify thisI am really confused

-- 
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/groups/opt_out.

Re: [beagleboard] Beaglebone Black ... What a Bull Shit !!!

[Seppo Nikkilä]

One lazy, immature and arrogant personality.
Worth ignoring, siñ


On Fri, Sep 27, 2013 at 7:35 AM, evilwulfie  wrote:

> I would say this person is a poor hardware designer and integrator
>
> nothing wrong with the BBB i can see at this stage in its short life
>
>
> On 9/26/2013 2:09 AM, gilles.nol...@gmail.com wrote:
> > We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
> > Nothing does work as expected!!!
> > Use of Touchscreen is hawfully slow and use of ADC with this screen
> > hangs up the system!
> >
> > How to get a such bad system. It is the same with angstrom distrib!!!
> >
> > We had developp a specific cape and we can put it in garbage!!!
> >
> > Forget this board and chose other one.
> >
> > Regards to all!
> > --
> > 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/groups/opt_out.
>
> --
> 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/groups/opt_out.
>



-- 
Developing next generation wireless audio

-- 
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/groups/opt_out.

Re: [beagleboard] Beaglebone Black ... What a Bull Shit !!!

[evilwulfie]

I would say this person is a poor hardware designer and integrator

nothing wrong with the BBB i can see at this stage in its short life


On 9/26/2013 2:09 AM, gilles.nol...@gmail.com wrote:
> We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
> Nothing does work as expected!!!
> Use of Touchscreen is hawfully slow and use of ADC with this screen
> hangs up the system!
>
> How to get a such bad system. It is the same with angstrom distrib!!!
>
> We had developp a specific cape and we can put it in garbage!!!
>
> Forget this board and chose other one.
>
> Regards to all!
> -- 
> 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/groups/opt_out.

-- 
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/groups/opt_out.

[beagleboard] Connecting to WPA(2) using wpa_supplicant and atheros chipset -- ubuntu

[Alvin Mites]

Been hacking at this all day, it's also the 3rd card so I got a few more 
already invested but not giving up this time

I have a TP LINK TL-WN722N with atheros chipset AR9271
I have a beaglebone black running ubuntu 13.04 arm

I've followed upwards of a dozen different tutorials with a number of links 
below to different references

I can connect to a wireless router with security disabled using iwconfig

I cannot connect to anything with WPA 1 or 2

wpa_supplicant.conf looks like

network={
proto=WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
ssid="MYSSID"
#psk="supersecretpassword"
psk=f2b34bb6b0e3ec1747325fac94ce0476a30911e08cf582df472d5df76e51dcad
}


so when I run

# wpa_supplicant -P /var/run/wpa_supplicant.wlan0.pid -i wlan0 -Dwext -c 
/etc/wpa_supplicant/wpa_supplicant.conf

I get


ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWSCAN]: Device or resource busy
wlan0: Failed to initiate AP scan
wlan0: Trying to associate with 00:00:00:00:00:00 (SSID='MYSSID' freq=2437 
MHz)
ioctl[SIOCSIWFREQ]: Device or resource busy
ioctl[SIOCSIWESSID]: Device or resource busy
wlan0: Association request to the driver failed
wlan0: Associated with 00:00:00:00:00:00
wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlan0: Authentication with 00:00:00:00:00:00 timed out.

any ideas?

tried a number of variations of the above, can copy & paste from history if 
it will be useful



---
|  reference  |
---

 tutorials
  good reference for long term setup
   
http://kerneldriver.wordpress.com/2012/10/21/configuring-wpa2-using-wpa_supplicant-on-the-raspberry-pi/
  general reference for wireless command line in ubuntu
  
 
http://askubuntu.com/questions/16584/how-to-connect-and-disconnect-to-a-network-manually-in-terminal
   http://ubuntuforums.org/showthread.php?t=318539
   http://ubuntuforums.org/showthread.php?t=571188
   http://ubuntuforums.org/showthread.php?t=263136

  

 forum posts
  worked through wpa_supplicant issues
   http://forums.gentoo.org/viewtopic-t-928818-start-0.html
  suggestions for auto-setup
   
http://askubuntu.com/questions/191836/wpa-supplicants-connection-issues
  

wifi hotspot

 http://thenewbieblog.wordpress.com/2012/05/01/wifi-hotspot-setup-on-ubuntu/

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[liyaoshi]

About 1， Fsl timesys will have the HardFloat driver for UBUNTU ,but no
wayland driver support

check from this

http://download.ossystems.com.br/bsp/freescale/source

BTW , do you someone know will SGX support wayland in some time ?where can
I get some information ?


2013/9/27 liyaoshi 

> So funny,
> This is my style !
> BUT ,
>
> What I can tell you something ,
>
> 1 ,Fsl will not have the vivante code to build for their release , you
> will not have a HardFloat enviroment
>
> 2,Fsl dont have the DMA support for UART ,i2c ,SPI support on their
> current bsp code and no plan to support
>
> 3,Fsl have ADMA bug on their SDHC host controller ,
>
> 4,Fsl dont support 16bit NAND boot on iMX6
>
> 5 TBD
>
> Ok, now , let's talk about your bull shit board ?
>
>
>
> 2013/9/27 Nuno Sucena Almeida 
>
>> On 09/26/2013 10:46 AM, Robert Nelson wrote:
>> > Humm, strange, as the defacto ubuntu maintainer, for some reason I do
>> > not see any email/bug messages from you regarding this issue.. SO
>> > whatever, if you don't try, it's not my problem...
>> >
>> > Regards,
>> >
>> > -- Robert Nelson http://www.rcn-ee.com/
>>
>> Hi Robert,
>>
>> I've been using 13.04 on a BBB without any issues, thank you for the
>> good work,
>>
>> regards,
>> Nuno
>>
>> --
>> http://aeminium.org/nuno/
>>
>> --
>> 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/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] elapsed time microseconds c++

[Nuno Sucena Almeida]

On 09/26/2013 09:31 PM, Nuno Sucena Almeida wrote:
> 
> Hi,
>   use a search engine and look for "linux measure time nanoseconds".
> Also: man clock_gettime
> 
> regards,
> Nuno
> 

If you have C++11 , look for chrono, it might be easier
http://en.cppreference.com/w/cpp/chrono

regards,
Nuno

-- 
http://aeminium.org/nuno/

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[liyaoshi]

About SD card
Fsl will have the 200M clk support for SDHC ,this will same speed as eMMC
4.4 8bit DDR mode
Only depend how much of your SD card

On my board , imx6 SOLO , ARM@800M  16bit DDR3 @400M ,ONFI 2.0 8bit nand
@100M clock

In wayland + QT 5.1.1

8 seconds can login to wayland-terminal console
almost 8s can run Qt HelloWindow with wayland egl

SD CARD will not be bottle neck ,


2013/9/26 Maxim Podbereznyy 

> I don't know which Freescale platform you have chosen but based on my
> experience with both Wandboard and Sabre Lite - imx6 running from a SD card
> is extremely slow. By slow I mean that even such stupid command like "ls"
> can complete up to 1 minute. Impressed?
> 26.09.2013 18:25 пользователь "Diogene"  написал:
>
> It just a beginning for TI ARM testing.
>> We will go to Freescale products.
>> Much more efficient.
>>
>> For your information, Win Ce has same problems ...
>> This project is not a company project but a community project.
>> In fact, Angstrom distrib is OK. Ubuntu ported on it is Hawfull!!!
>>
>> Regards.
>>
>> Le jeudi 26 septembre 2013 15:25:32 UTC+2, Mickae1 a écrit :
>>>
>>> well, you shouldn't blame the company behind the BBB, neither the
>>> community.
>>>
>>> *It's entirely your fault*, you decided for your product to use open
>>> source solution !
>>>
>>>  Yes it's attractive, you don't need to buy a license for windows CE,
>>> but you should have made some research and discovered since we moved to the
>>> new kernel, not all of the functions are available.
>>>
>>> *It's unacceptable for a company to bet that the BBB will work in few
>>> months *
>>>
>>> In my case, i was at the same position as you 6 months ago, I wanted to
>>> use the RS485 Cap ... and you know what ? I decided to spend 2 months to
>>> find out how to modify the drivers. And now It's working ! ( Thx  again
>>> everyone for your help again)
>>>
>>>
>>> So, you should instead blame yourself or spend some time to help us, and
>>> find out what's wrong with the LCD.. .
>>>
>>> IF you don't have TIME, give some money to this community and I'm sure
>>> that a developer will put this bug in priority.
>>>
>>>
>>> Michael Musset,
>>>
>>>
>>> On Thu, Sep 26, 2013 at 2:59 PM, garyamort  wrote:
>>>


 On Thursday, September 26, 2013 5:09:30 AM UTC-4, Diogene wrote:
>
> We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
> Nothing does work as expected!!!
> Use of Touchscreen is hawfully slow and use of ADC with this screen
> hangs up the system!
>
> How to get a such bad system. It is the same with angstrom distrib!!!
>
> We had developp a specific cape and we can put it in garbage!!!
>
>
 I'll happily pay for shipping if you want to send me the cape and
 board. :-)



 --
 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/**groups/opt_out
 .

>>>
>>>  --
>> 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/groups/opt_out.
>>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] elapsed time microseconds c++

[Nuno Sucena Almeida]

On 09/26/2013 03:36 PM, ignacio.mata...@gmail.com wrote:
> hello,
> 
> I tried several ways ( clock(), gettimeofday()..) but I can get the proper 
> way to measure the elapsed time in microseconds.
> 
> I am using eclipse to program in ansi c. Could anybody help me about how to 
> measure the elapsed time in microsecond? Could it be possible to enclosed 
> the code that I should use? 
> 
> thank you so much and sorry for the inconveniences
> 
> Regards
> 

Hi,
use a search engine and look for "linux measure time nanoseconds".
Also: man clock_gettime

regards,
Nuno

-- 
http://aeminium.org/nuno/

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[liyaoshi]

So funny,
This is my style !
BUT ,

What I can tell you something ,

1 ,Fsl will not have the vivante code to build for their release , you will
not have a HardFloat enviroment

2,Fsl dont have the DMA support for UART ,i2c ,SPI support on their current
bsp code and no plan to support

3,Fsl have ADMA bug on their SDHC host controller ,

4,Fsl dont support 16bit NAND boot on iMX6

5 TBD

Ok, now , let's talk about your bull shit board ?



2013/9/27 Nuno Sucena Almeida 

> On 09/26/2013 10:46 AM, Robert Nelson wrote:
> > Humm, strange, as the defacto ubuntu maintainer, for some reason I do
> > not see any email/bug messages from you regarding this issue.. SO
> > whatever, if you don't try, it's not my problem...
> >
> > Regards,
> >
> > -- Robert Nelson http://www.rcn-ee.com/
>
> Hi Robert,
>
> I've been using 13.04 on a BBB without any issues, thank you for the
> good work,
>
> regards,
> Nuno
>
> --
> http://aeminium.org/nuno/
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] SSH keypair authentifcation

[Nuno Sucena Almeida]

On 09/26/2013 05:26 AM, leo mayer wrote:
> ubuntu@BBB:~$ ssh-copy-id -i ubuntu@192.168.7.1 

You have to run the ssh-copy-id in the machine you are connecting *from*
(client machine), not what you are connecting *to* (server machine) ,
this case the BBB.

Alternatively, you can generate the keypair in the client machine and
copy the .pub manually and put it into the authorized_keys in the
server, usually ~/.ssh/authorized_keys

http://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter8.html

regards,
Nuno

-- 
http://aeminium.org/nuno/

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[Nuno Sucena Almeida]

On 09/26/2013 10:46 AM, Robert Nelson wrote:
> Humm, strange, as the defacto ubuntu maintainer, for some reason I do
> not see any email/bug messages from you regarding this issue.. SO
> whatever, if you don't try, it's not my problem...
> 
> Regards,
> 
> -- Robert Nelson http://www.rcn-ee.com/

Hi Robert,

I've been using 13.04 on a BBB without any issues, thank you for the
good work,

regards,
Nuno

-- 
http://aeminium.org/nuno/

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Initializing memory on the BBW using Starterware examples

[Warren Scheinin]

Hi, Louis

 Wow, thanks for heeding my call.

 1) Yes, I am using the latest Starterware for the AM335x family.  The
older version actually worked better because I could compile in debug mode
while the latest version only lets me run in release mode for the time
being.  As my TI Applications support adviser noted before turning me over
to the forum, the latest version inserts a debug or release folder in the
source code location file chain.

 2) Yes, I tested it first without any of my own code added to the
demo.   The print statements were only added later to see where it stopped.

   3) I have no problem running the Angstrom Distribution or the Demo using
a freshly formatted memory card.   Although I am not sure what to expect
when I run usb_dev_serial.  Perhaps a second com port window?  Surprisingly
(to me), after Starterware hangs at MMUinit, the MLO/Demo binaries still
work after I press the reset button on the board (but not the reset in
Starterware).

Thanks for giving me hope,
Warren




On Thu, Sep 26, 2013 at 1:58 PM, Louis McCarthy  wrote:

> This is a pretty specific issue, and since I don't have this exact setup,
> I am shooting in the dark.
>
> 1) Are you using the latest Starterware for the AM335x family?
> 2) Have you tested it without any of your code added to the demo?
> 3) Have you freshly formatted and partitioned the memory card and then
> copied MLO first, then other files?
>
> It's been a few months since I played around in Starterware
> Louis
>
> On Wednesday, September 18, 2013 12:49:33 PM UTC-5, Warren S wrote:
>>
>> Hi:
>>
>>  My BeagleBone White hangs at the function call MMUInit((unsigned
>> int*)pageTable) while running the Demo and the usb_dev_serial examples in
>> TI's Starterware 01.01 in the TI Code Composer Studio v5.  I have
>> corresponded with the TI Applications support team and the TI Starterware
>> community at TI Home  » TI E2E 
>> Community» Support
>> Forums  » Embedded 
>> Software»
>> StarterWare » 
>> StarterWare
>> forum  » the
>> demo in StarterWare_02_00_00_07 is not working for 
>> AM3352BZCZ80to
>>  no avail.  It runs the C instructions and my added print to console
>> statements just fine until I get to this function call halfway through the
>> MMUConfigAndEnable function call define earlier in the example programs.
>>
>> Thanks,
>>
>> Warren S.
>>
>  --
> 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/xVEoeppurpI/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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] Re: g_ether usb0 static IP

[Brandon I]

Looking at my beaglebone with the 7-31 production image, there's a systemd 
service called storage-gadget-init. Check out what it's doing with 
"systemctl status storage-gadget-init":

  Loaded: loaded (/lib/systemd/system/storage-gadget-init.service; 
enabled)
  Active: active (running) since Tue 2000-01-04 00:57:51 UTC; 13 
years 8 months ago
Main PID: 122 (g-ether-load.sh)
  CGroup: name=systemd:/system/storage-gadget-init.service
  |-122 */bin/sh /usr/bin/g-ether-load.sh*
  `-353 */usr/sbin/udhcpd -f -S /etc/udhcpd.conf*

I'ts running a script g-ether-load.sh with a line at the end:

/sbin/ifconfig usb0 192.168.7.2 netmask 255.255.255.252

then fires up the dhcp server with the configuration from /etc/udhcpd.conf 
that sets the ip range for the dhcp server for the usb host, acting as a 
dhcp client, the usb cable is connected to:

start  192.168.7.1
end192.168.7.1
interface  usb0
max_leases 1
option subnet 255.255.255.252


So, you'll have to change both files with the subnet in mind.

I don't know if the udev rule comes into play at all. I deleted the file, 
rebooted with usb plugged in, I get an ip. Rebooted with usb disconnected, 
connect usb, get an ip. Probably some old thing that someone forgot about.

"Can't Linux without a little wtf." - Bob Dole, 1978

On Saturday, August 31, 2013 3:12:32 AM UTC-7, Víctor MV wrote:
>
> Hi Steve,
>
> I followed your exact instructions but my usb0 interface is still getting 
> the 192.168.7.2 address. No clue how to modify this. I even tried to remove 
> this udhcpd.rules but nothing.
>
> Actually i'd like to remove this interface totally because i think the 
> usb-over-ethernet is causing the kernel to crash
>
> root@beaglebone:/var/lib/connman# [  600.197574] INFO: task 
> systemd-udevd:346 blocked for more than 60 seconds. 
>  
> [  600.204837] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
> this message.   
>   
> [  600.213115] Kernel panic - not syncing: hung_task: blocked tasks   
> 
>
> [  600.219439] [] (unwind_backtrace+0x1/0x8c) from [] 
> (panic+0x55/0x14c) 
> 
> [  600.228011] [] (panic+0x55/0x14c) from [] 
> (watchdog+0x153/0x1a0) 
>  
> [  600.236129] [] (watchdog+0x153/0x1a0) from [] 
> (kthread+0x61/0x72) 
> 
> [  600.244336] [] (kthread+0x61/0x72) from [] 
> (ret_from_fork+0x11/0x34)   
>
> [  631.278836]  gadget: rndis req21.00 v i l12 
> 
>   
> [  631.283984] rndis_msg_parser: RNDIS_MSG_HALT   
> 
>
> [  631.295282] CAUTION: musb: Babble Interrupt Occurred   
> 
>
> [  631.300482]  gadget: reset config   
> 
>   
> [  631.303947]  gadget: rndis deactivated 
> 
>
> [  631.307869] usb0: gether_disconnect 
> 
>   
> [  631.311542]  gadget: acm ttyGS0 deactivated 
> 
>   
> [  631.367452] CAUTION: musb: Babble Interrupt Occurred   
> 
>
> [  631.455212]  gadget: high-speed config #1: Multifunction with RNDIS 
> 
>   
> [  631.461773]  gadget: init rndis 
> 
>   
> [  631.465058]  gadget: RNDIS RX/TX early activation ...   
> 
>   
> [  631.470441] usb0: qlen 10   
> 
>   
> [  631.473180]  gadget: rndis_close

[beagleboard] Re: How do I find the U-Boot source and build options exactly as it is in the prod version of BBB?

[Clark]

Best answer is located here:
   
http://www.crashcourse.ca/wiki/index.php/U-Boot_on_the_BBB#BBB-specific_U-Boot_from_current_Git_tree

-- 
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/groups/opt_out.

Re: [beagleboard] Unable to get IP with DHCP, Static IP doesn't work, TFTP times out

[Clark]

Are you building your own U-boot?

On this website:
http://www.crashcourse.ca/wiki/index.php/U-Boot_on_the_BBB#BBB-specific_U-Boot_from_current_Git_tree

I did notice this note:
It appears that if you want to download the kernel via TFTP, you have to 
apply the "kloadaddr" patch from above.

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Initializing memory on the BBW using Starterware examples

[Mark Lazarewicz]

Never calling print before the processor and MMU is initialized is that 
something you added?





 From: Louis McCarthy 
To: beagleboard@googlegroups.com 
Sent: Thursday, September 26, 2013 4:58 PM
Subject: [beagleboard] Re: Initializing memory on the BBW using Starterware 
examples
 


This is a pretty specific issue, and since I don't have this exact setup, I am 
shooting in the dark.

1) Are you using the latest Starterware for the AM335x family?

2) Have you tested it without any of your code added to the demo?
3) Have you freshly formatted and partitioned the memory card and then copied 
MLO first, then other files?

It's been a few months since I played around in Starterware 
Louis

On Wednesday, September 18, 2013 12:49:33 PM UTC-5, Warren S wrote:
Hi:
>
> My BeagleBone White hangs at the
function call MMUInit((unsigned int*)pageTable) while running the
Demo and the usb_dev_serial examples in TI's Starterware 01.01 in the
TI Code Composer Studio v5.  I have corresponded with the TI
Applications support team and the TI Starterware community at TI
Home » TI E2E Community » Support Forums » Embedded
Software » StarterWare » StarterWare
forum » the
demo in StarterWare_02_00_00_07 is not working for AM3352BZCZ80 to no avail.  
It runs the C instructions and my added print to
console statements just fine until I get to this function call
halfway through the MMUConfigAndEnable function call define earlier
in the example programs. 
>
>Thanks, 
>
>Warren S.
>
-- 
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/groups/opt_out.

-- 
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/groups/opt_out.

Re: [beagleboard] BBB Video Drivers

[Robert Nelson]

On Thu, Sep 26, 2013 at 4:42 PM, garyamort  wrote:
>
>
> On Thursday, September 26, 2013 4:02:34 PM UTC-4, RobertCNelson wrote:
>>
>> On Thu, Sep 26, 2013 at 2:54 PM, garyamort  wrote:
>> >
>> > There is the tilcdc Driver:  Released by Ron Clark at the beginning of
>> > 2013.
>> > http://lwn.net/Articles/533731/  This driver, if installed, is
>> > configured
>> > via the Device Tree.  For example, see the BB-BONE-LCD7-*.dts files.
>> > These
>> > files contain the pin connection info and the LCD display configuration
>> > information and will be used by the tilcdc driver to configure the
>> > display.
>> > Note: I do not know what configuration options are supported for
>> > userland
>> > configuration[ie setting rotation on bootup, or configuring rotation in
>> > the
>> > Xorg.conf file]  This drivers sourcecode is located at
>> > drivers/gpu/tilcdc
>
>
> Extra note: There is Device Tree Documentation for tilcd, see
> https://github.com/torvalds/linux/tree/master/Documentation/devicetree/bindings/drm/tilcdc
>
>
>
>>
>> >
>> > There is the omap  frame buffer driver: Located at drivers/video/omap
>> > This
>>
>> No... different IP block... tilcdc != video/omap
>>
>> > There is the omap2 frame buffer driver: Located at
>>
>> No... different IP block... tilcdc != omapfb
>>
>
> Great!  Thanks for the correction.  So it seems like the most basic choice
> is between the fallback driver, fbdev, and tilcdc.

and the "modesetting" ddx... which is a generic ddx driver for most
kms drivers...

> I'm guessing that I am incorrect there and that tilcdc is a more low level
> driver which is loaded regardless, and fbdev just provides some higher level
> Xorg config options.

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/groups/opt_out.

Re: [beagleboard] BBB Video Drivers

[garyamort]

On Thursday, September 26, 2013 4:02:34 PM UTC-4, RobertCNelson wrote:
>
> On Thu, Sep 26, 2013 at 2:54 PM, garyamort > 
> wrote: 
> > 
> > There is the tilcdc Driver:  Released by Ron Clark at the beginning of 
> 2013. 
> > http://lwn.net/Articles/533731/  This driver, if installed, is 
> configured 
> > via the Device Tree.  For example, see the BB-BONE-LCD7-*.dts files.   
> These 
> > files contain the pin connection info and the LCD display configuration 
> > information and will be used by the tilcdc driver to configure the 
> display. 
> > Note: I do not know what configuration options are supported for 
> userland 
> > configuration[ie setting rotation on bootup, or configuring rotation in 
> the 
> > Xorg.conf file]  This drivers sourcecode is located at 
> drivers/gpu/tilcdc 
>

Extra note: There is Device Tree Documentation for tilcd, see
https://github.com/torvalds/linux/tree/master/Documentation/devicetree/bindings/drm/tilcdc


 

> > 
> > There is the omap  frame buffer driver: Located at drivers/video/omap   
> This 
>
> No... different IP block... tilcdc != video/omap 
>
> > There is the omap2 frame buffer driver: Located at 
>
> No... different IP block... tilcdc != omapfb 
>
>
Great!  Thanks for the correction.  So it seems like the most basic choice 
is between the fallback driver, fbdev, and tilcdc.

I'm guessing that I am incorrect there and that tilcdc is a more low level 
driver which is loaded regardless, and fbdev just provides some higher 
level Xorg config options.


-- 
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/groups/opt_out.

Re: [beagleboard] Slidshow no longer works and cannot debug with Cloud9

[Louis McCarthy]

>From the serial console, have you tried looking at the dmesg log for any 
clues? I've included my BBW dmesg as reference. At around 6.7 seconds, you 
can see the init of 'gadget' in my dmesg log. Is yours starting? How about 
rndis?

You can also see if services are running by typing the following in the 
console:
systemctl
look for cloud9, connman, gateone. Are they active and running?

Another option is to get a more detailed dmesg log by running this:
journalctl
look for any errors

Louis

On Friday, September 20, 2013 2:31:34 PM UTC-5, Raphael Titsworth-Morin 
wrote:

> Hi Gerald,
>
> I don't know which one I was using last night when I posted, but I 
> re-imaged and am now using:
> Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img
>
> Just to clarify (in case it matters), I am using a BeagleBone and not a 
> BeagleBone Black.
>
> Since I re-imaged, all I can do is connect with Putty over serial.  I 
> cannot even load Cloud9 anymore.
>
> I feel like the virtual ethernet over usb is no longer working.  Here is 
> what I get from ifconfig:
>
> root@beaglebone:~# ifconfig
> eth0  Link encap:Ethernet  HWaddr 00:18:31:8F:47:B8
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>   Interrupt:56
>
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
>
> Thanks for the help!
>
> On Friday, September 20, 2013 9:10:30 AM UTC-4, Gerald wrote:
>>
>> What version of the BeagleBone Black image are you using?
>>
>> Gerald
>>
>>
>>
>> On Fri, Sep 20, 2013 at 1:55 AM,  wrote:
>>
>>> Hi there!
>>>
>>> I just started playing with a BeagleBone I've had lying around for a 
>>> little while.  
>>>
>>> I have some (not much) experience with linux, but mainly Ubuntu, and 
>>> have never played with anything quite like this.
>>>
>>> I got everything installed as needed.  I plugged in the Beaglebone, 
>>> ejected it from within Windows Explorer and navigated to 192.168.7.2, as 
>>> per the instructions found 
>>> here. 
>>>  I start going through the little slideshow, which I find quite 
>>> informative.  I get to the slide which has links to blink the LEDs in it. 
>>>  They work. Awesome.  I get to the slide with link to Cloud9 and something 
>>> else.  I click the Cloud9 link, expecting it to open in a new tab. It 
>>> doesn't. Whatever. I go through the tour and then try to go back to the 
>>> slideshow.  It doesn't work anymore and tells me that "index.html" doesn't 
>>> exist.  I try in firefox (I was in chrome). Still doesn't work. Cloud9 
>>> does, though.  
>>>
>>> I reboot.  The slideshow still doesn't doesn't work, but this time I 
>>> don't even get a message about "index.html" not existing.  I wonder what 
>>> does/doesn't work, so I open up Cloud9.  Everything seems ok.  I try to 
>>> plug in the sample code from the link I mentioned previously and run it as 
>>> described. Doesn't work.  I use Putty and log in.  I can turn the LEDs on 
>>> and off by echo-ing 0 or 1 to the appropriate files, but nothing from 
>>> within Cloud9.
>>>
>>> Then I tell myself that perhaps the slideshow was being served up using 
>>> Node. The led blinking example was in JS, so perhaps there is a problem 
>>> with node and that's why I'm not getting anything.  I have a bit of 
>>> background in web development (Apache/PHP/MySQL, specifically) but do not 
>>> know how Node works.  It seems to run correctly when I run "node" from the 
>>> shell, but I assume there needs to be a particular instance of it running 
>>> to serve up/run the stuff from Cloud9 and the slideshow?
>>>
>>> Anyway, I just want to start fiddling.
>>>
>>> Is there something I'm missing? Is this normal? Or should I re-image?
>>>
>>> Also, is there a good, detailed reference somewhere on using BoneScript? 
>>> And a good reference on getting stuff done outside of BoneScript? Can I 
>>> write applications in other languages from within Cloud9? Or is that 
>>> something I'll have to do differently?
>>>
>>> I'm really excited about playing with the BeagleBone, especially since 
>>> it seems I'll be able to read/run a lot more stuff more easily than with my 
>>> arduino, but at the moment I'm feeling incredibly lost and confused.
>>>
>>> Thanks in advance for any help!
>>>
>>> Raph
>>>
>>> -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed 

Re: [beagleboard] LCD4 Backlight brightness

[Terry Storm]

No takers?

Any help would be really appreciated.

Terry

On Thursday, 26 September 2013 11:21:50 UTC+12, Terry Storm wrote:
>
> I have been doing some reading.
>
> In the DTS file for the BB-BONE-LCD4-01-00A1.dts, there is the PWM 
> settings which is currently set to 50 which is in nanoseconds, which is 
> 2Khz. Which is good.
> Changing this value to 100 which is 1Khz, and then running this 
> command:
> dtc -O dtb -o BB-BONE-LCD4-01-00A1.dtbo -b 0 -@ BB-BONE-LCD4-01-00A1.dts
> to compile it
> I then restarted, and the frequency was still 2Khz.
>
> Can anyone suggest what I am not doing or something else I need to do?
>
> Thanks
> Terry
>

-- 
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/groups/opt_out.

[beagleboard] Re: opkg upgrade=WARNING: could not open /lib/modules/3.8.13/modules.order: No such file or directory

[Brandon I]

http://imgur.com/6W5zcb0.jpg

On Wednesday, September 25, 2013 12:20:49 PM UTC-7, Steve French wrote:
>
> Hello!  New to BBB, but lovin it so far...got two of them working on the 
> same network...more to come...
>
> 1) So, I used this image "BBB-eMMC-flasher-2013.09.04.img"
> 2) In order for me to do a opkg update & opkg upgrade without hundreds of 
> "opkg_download: Failed to download" errors , I had to do the hack that 
> Paul Tan referenced 
> here
> .
> 3) After a seemingly successful completion of "opkg upgrade", I noticed 
> these warnings on both BBBs that I was upgrading at the same time. 
>  (Interestingly one of them had 4 warnings and the other had 6 warnings)
>
> QUESTION:  Ignore it or fix it somehow?  Thx!
>
> Final lines of  "opkg upgrade" for root@VoltVision-BBB1:
> WARNING: could not open /lib/modules/3.8.13/modules.order: No such file or 
> directory
> WARNING: could not open /lib/modules/3.8.13/modules.builtin: No such file 
> or directory
> WARNING: could not open /lib/modules/3.8.13/modules.order: No such file or 
> directory
> WARNING: could not open /lib/modules/3.8.13/modules.builtin: No such file 
> or directory
> WARNING: could not open /lib/modules/3.8.13/modules.order: No such file or 
> directory
> WARNING: could not open /lib/modules/3.8.13/modules.builtin: No such file 
> or directory
>
> Final lines of  "opkg upgrade" for root@VoltVision-BBB2:
> WARNING: could not open /lib/modules/3.8.13/modules.order: No such file or 
> directory
> WARNING: could not open /lib/modules/3.8.13/modules.builtin: No such file 
> or directory
> WARNING: could not open /lib/modules/3.8.13/modules.order: No such file or 
> directory
> WARNING: could not open /lib/modules/3.8.13/modules.builtin: No such file 
> or directory
>

-- 
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/groups/opt_out.

[beagleboard] Re: Noise Issues

[Louis McCarthy]

Solar panels, by themselves, should not cause any issues. My guess is that 
a power tracker, charge controller, or inverter is creating AC noise. If 
you can detect or find out what frequency they are running at, you may be 
able to create some filters on the inputs to the beaglebone.

You don't say whether the beaglebone is directly connected, in any way, to 
the solar panel system. It they are connected, you may want to optically 
isolate digital/analog inputs to the beaglebone.

I have powered a few BBWs with PCB DC-to-DC devices, from Murata 
(OKI-78SR-5/1.5-W36H-C), with no issues.

Louis

On Monday, September 23, 2013 12:43:22 PM UTC-5, mojok...@gmail.com wrote:

> We noticed the Beaglebone boards are sensitive to noise.  They don' work 
> with inexpensive switching type power supplies.  Also our Beaglebone board 
> is not working next to Solar Panels that are located on-stie.
>
> Has anyone had experience with this?  If so, what have you done to fix the 
> issues?
>
> Thanks,
>
> Jeremy
>
I have powered a few BBW with a cheap DC to DC device from Murata (I have 
powered a few BBW with a cheap DC to DC device from Murata (

On Monday, September 23, 2013 12:43:22 PM UTC-5, mojok...@gmail.com wrote:
>
> We noticed the Beaglebone boards are sensitive to noise.  They don' work 
> with inexpensive switching type power supplies.  Also our Beaglebone board 
> is not working next to Solar Panels that are located on-stie.
>
> Has anyone had experience with this?  If so, what have you done to fix the 
> issues?
>
> Thanks,
>
> Jeremy
>

-- 
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/groups/opt_out.

Re: [beagleboard] Boot with uImage and device tree

[Robert Nelson]

On Thu, Sep 26, 2013 at 3:40 PM,   wrote:
> Hi,
>
> I am looking for a uEnv.txt file which allow me to boot a uImage with a BBM
> .dtb file.
>
> I use this one :
>
>> mmc rescan ; fatload mmc 0 8200 uImage;fatload mmc 0 8000
>> am335x-boneblack.dtb
>> mmcargs=setenv bootargs 'console=ttyO0,115200n8 mem=256M
>> root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait init=/init '
>> fdt addr 8000; fdt resize; bootm 8200 - 8000 ; run mmcargs
>
>
>
> But I can't boot!!

Well why are you running "mmcargs" after bootm?  Once bootm runs,
everything in u-boot afterwards will not be run...

> I don't have serial cable, but I have a HDMI screen;

Get a serial cable... Blind debugging can be painful and a waste of time..

> So what's i need to add in my uEnv.txt in order to have u-boot trace in my
> HDMI screen?

Well first, patches to enable hdmi output/terminal in u-boot.. Could
be a good google summer of code project

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/groups/opt_out.

[beagleboard] Re: Initializing memory on the BBW using Starterware examples

[Louis McCarthy]

This is a pretty specific issue, and since I don't have this exact setup, I 
am shooting in the dark.

1) Are you using the latest Starterware for the AM335x family?
2) Have you tested it without any of your code added to the demo?
3) Have you freshly formatted and partitioned the memory card and then 
copied MLO first, then other files?

It's been a few months since I played around in Starterware 
Louis

On Wednesday, September 18, 2013 12:49:33 PM UTC-5, Warren S wrote:
>
> Hi:
>
>  My BeagleBone White hangs at the function call MMUInit((unsigned 
> int*)pageTable) while running the Demo and the usb_dev_serial examples in 
> TI's Starterware 01.01 in the TI Code Composer Studio v5.  I have 
> corresponded with the TI Applications support team and the TI Starterware 
> community at TI Home  » TI E2E 
> Community» Support 
> Forums  » Embedded 
> Software» 
> StarterWare » 
> StarterWare 
> forum  » the 
> demo in StarterWare_02_00_00_07 is not working for 
> AM3352BZCZ80to
>  no avail.  It runs the C instructions and my added print to console 
> statements just fine until I get to this function call halfway through the 
> MMUConfigAndEnable function call define earlier in the example programs. 
>
> Thanks, 
>
> Warren S.
>

-- 
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/groups/opt_out.

[beagleboard] Boot with uImage and device tree

[gelie . jo]

Hi,

I am looking for a uEnv.txt file which allow me to boot a uImage with a BBM 
.dtb file.

I use this one :

mmc rescan ; fatload mmc 0 8200 uImage;fatload mmc 0 8000 
> am335x-boneblack.dtb
> mmcargs=setenv bootargs 'console=ttyO0,115200n8 mem=256M 
> root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait init=/init '
> fdt addr 8000; fdt resize; bootm 8200 - 8000 ; run mmcargs



But I can't boot!! 

I don't have serial cable, but I have a HDMI screen; 

So what's i need to add in my uEnv.txt in order to have u-boot trace in my 
HDMI screen?


best!

-- 
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/groups/opt_out.

Re: [beagleboard] Re: BBW custom 3.5 LCD

[Louis McCarthy]

If you are running the latest image, it is 3.8. That is what I am running 
on a couple of BBW.

On Thursday, September 26, 2013 3:17:39 PM UTC-5, lisarden wrote:
>
> I suppose BBW boots with the kernel 3.2 which does not have DTC support. 
> Am I right?
>
>
> 2013/9/27 Louis McCarthy >
>
>> I would start by looking at the dts file, for an existing LCD cape, in 
>> /lib/firmware
>>
>> You can modify it, compile it to a dtbo file, and then load it as a test 
>> cape for testing. This is assuming you are using the 3.8 Kernel.
>>
>> You should check out the hipstercircuits blog for good info on displays 
>> and capes.
>>
>> Louis
>>
>>
>> On Monday, September 2, 2013 7:53:13 PM UTC-5, xavier@gmail.comwrote:
>>>
>>> Hi everyone, I'm trying to connect a 3.5" LCD to a BBW, I'm basing my 
>>> connections from the LCD3 cape, however the LCD parameters are different 
>>> (HFP, etc) which I know the right values.
>>> I would like to know which files do I have to modify (or add) with the 
>>> LCD information and how do I configure that the BBW boots using the LCD.
>>>
>>> I have a little experience with linux and BB in general.
>>>
>>> Thank you 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> -- 
> LinkedIn - http://www.linkedin.com/in/maximpodbereznyy
> Company - http://www.linkedin.com/company/mentorel
> Facebook - https://www.facebook.com/mentorel.company
>  

-- 
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/groups/opt_out.

Re: [beagleboard] Re: BBW custom 3.5 LCD

[Maxim Podbereznyy]

I suppose BBW boots with the kernel 3.2 which does not have DTC support. Am
I right?


2013/9/27 Louis McCarthy 

> I would start by looking at the dts file, for an existing LCD cape, in
> /lib/firmware
>
> You can modify it, compile it to a dtbo file, and then load it as a test
> cape for testing. This is assuming you are using the 3.8 Kernel.
>
> You should check out the hipstercircuits blog for good info on displays
> and capes.
>
> Louis
>
>
> On Monday, September 2, 2013 7:53:13 PM UTC-5, xavier@gmail.com wrote:
>>
>> Hi everyone, I'm trying to connect a 3.5" LCD to a BBW, I'm basing my
>> connections from the LCD3 cape, however the LCD parameters are different
>> (HFP, etc) which I know the right values.
>> I would like to know which files do I have to modify (or add) with the
>> LCD information and how do I configure that the BBW boots using the LCD.
>>
>> I have a little experience with linux and BB in general.
>>
>> Thank you 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/groups/opt_out.
>



-- 
LinkedIn - http://www.linkedin.com/in/maximpodbereznyy
Company - http://www.linkedin.com/company/mentorel
Facebook - https://www.facebook.com/mentorel.company

-- 
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/groups/opt_out.

[beagleboard] Re: BBW custom 3.5 LCD

[Louis McCarthy]

I would start by looking at the dts file, for an existing LCD cape, in 
/lib/firmware

You can modify it, compile it to a dtbo file, and then load it as a test 
cape for testing. This is assuming you are using the 3.8 Kernel.

You should check out the hipstercircuits blog for good info on displays and 
capes.

Louis

On Monday, September 2, 2013 7:53:13 PM UTC-5, xavier@gmail.com wrote:
>
> Hi everyone, I'm trying to connect a 3.5" LCD to a BBW, I'm basing my 
> connections from the LCD3 cape, however the LCD parameters are different 
> (HFP, etc) which I know the right values.
> I would like to know which files do I have to modify (or add) with the LCD 
> information and how do I configure that the BBW boots using the LCD.
>
> I have a little experience with linux and BB in general.
>
> Thank you 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/groups/opt_out.

Re: [beagleboard] servo?

[Robert Nelson]

On Thu, Sep 26, 2013 at 2:52 PM, Marcus Diogo  wrote:
> adafruit Adafruit_BBIO does not work with ubuntu precise. :(

You should expand on that...  "what" part does not work with ubuntu
precise? do you even have the correct image?  Did you contact the
author to get it fixed?

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/groups/opt_out.

[beagleboard] Re: Can't get into 192.168.7.2 for BeagleBone!!! But It does work with LCD7 display.

[debbynel]

Hi,

I got my beaglebone today and accessing it from Windows.

Initial setup worked fine. But later could not login via ssh or 
192.168.7.2. After searching I discovered that DHCP was not enabled. 

Quick test: type ping 192.168.7.2 in your windows console. If you receive a 
return message that contain "expired in transit" then enable DHCP for the 
respective network adapter.

Regards

On Thursday, May 30, 2013 11:26:23 PM UTC+2, Xicheng Xu wrote:
>
>
> Hi everyone
>
> I guess logging into 192.168.7.2 is the very first step to play with 
> BeagleBone RevA6a( not BeagleBone Black), but I can't do it. 
> It works with the LCD7 display while having trouble with logging into 
> 192.168.7.2 or shh with either Chrome or Firefox.( With newest Angstrom)
> Clueless now, Any one can help?
>
> 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/groups/opt_out.

Re: [beagleboard] BBB Video Drivers

[Robert Nelson]

On Thu, Sep 26, 2013 at 2:54 PM, garyamort  wrote:
> As a stick in the ground, I wanted to provide a quick summary of  video
> drivers for the BeagleBoneBlack.
>
> There is the Xorg Kernel Mode Setting Driver : an extremely basic frame
> buffer driver and the fallback driver if no better Xorg driver is found.  It
> has extremely limited functionality and does not support screen rotation.
>
> There is the Xorg fbdev Driver: a still basic frame buffer driver, but it
> does support some configuration options including rotate.
>
> There is the tilcdc Driver:  Released by Ron Clark at the beginning of 2013.
> http://lwn.net/Articles/533731/  This driver, if installed, is configured
> via the Device Tree.  For example, see the BB-BONE-LCD7-*.dts files.   These
> files contain the pin connection info and the LCD display configuration
> information and will be used by the tilcdc driver to configure the display.
> Note: I do not know what configuration options are supported for userland
> configuration[ie setting rotation on bootup, or configuring rotation in the
> Xorg.conf file]  This drivers sourcecode is located at drivers/gpu/tilcdc
>
> There is the omap  frame buffer driver: Located at drivers/video/omap   This
> driver requires LCD panel configuration information which is available for
> some LCD panels in the same directory as the driver.  Does this work for the
> BeagleBoneBlack?

No... different IP block... tilcdc != video/omap

> There is the omap2 frame buffer driver: Located at
> drivers/video/omap2/omapfb.  This driver requires LCD panel configuration,
> of which many are already written - see drivers/video/omap2/displays for
> them.  Does this work for the BeagleBoneBlack?

No... different IP block... tilcdc != omapfb

> There is the PVRSRVKVM Driver: Uses the built in SGX graphcis processor to
> accelerate graphics processing and offload processing from the CPU.  This
> driver may not work under Linux Kernel version 3.8.   According to the
> latest release notes, http://processors.wiki.ti.com/index.php/RN_4_10_00_01,
> version 4.10.00.01 works for the Linux 3.8 kernel.  From the release notes:
>
> Validation information
>
> NOTE -
>
> 1. This release has been tested on AM parts only.
>
> 2. This release is build tested only for 387x(TI814x) & 389x(TI816x) & DM
> parts.
>
> 3. This release is build tested only against 3.8 kernel.
>
>
> The BBB uses a 335x processor, not 387x or 389x - so it does not appear that
> it has been tested for the BBB, but it has been tested for the 3.8 kernel.
>
> Also note that the above statement is contradicted later in the release
> notes by:
>
> Kernel(Linux PSP) versions supported or used for validation
>
> Please note that this release has been tested only on AM devices. No testing
> has been done on the DM parts. Only the following devices have been tested &
> details below -
>
> AM335x - 3.2 kernel - http://arago-project.org/git/projects/linux-am33x.git
>
> AM335x Linux PSP 04.06.00.10
> Branch – v3.2-staging, TAG - v3.2_AM335xPSP_04.06.00.10-rc1, commit id
> -c8cce6279f5c126cbf6b6054f1ea0148bfc19511
>
> AM35xx/AM37xx - 2.6.37 kernel
>
> Linux PSP Release : 04.02.00.07.
> Display drivers with DSS2 support ie, CONFIG_OMAP2_DSS=y
>
>
>
>
> My assumption is that the earlier statement overrides the later statement.
>
>  To add to the confusion, many of these drivers are used in combination.
> For example, you might have both the Omap 2 Framebuffer Driver AND the SGX
> Driver installed.  The SGX driver overrides some of the functions in the
> Omap driver(?).   Xorg configuration would be for the Omap driver, not the
> SGX driver[?]
>
> Please correct any of my misassumptions in the above.

The am335x parts do not have the IP block to use the omap/omapfb
driver.  They have an extended/ehanced version of the DaVanci DA8XX..

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/video/da8xx-fb.h

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/groups/opt_out.

[beagleboard] BBB Video Drivers

[garyamort]

As a stick in the ground, I wanted to provide a quick summary of  video 
drivers for the BeagleBoneBlack.

There is the Xorg Kernel Mode Setting Driver : an extremely basic frame 
buffer driver and the fallback driver if no better Xorg driver is found. 
 It has extremely limited functionality and does not support screen 
rotation.

There is the Xorg fbdev Driver: a still basic frame buffer driver, but it 
does support some configuration options including rotate.

There is the tilcdc Driver:  Released by Ron Clark at the beginning of 
2013. http://lwn.net/Articles/533731/  This driver, if installed, is 
configured via the Device Tree.  For example, see the BB-BONE-LCD7-*.dts 
files.   These files contain the pin connection info and the LCD display 
configuration information and will be used by the tilcdc driver to 
configure the display.   Note: I do not know what configuration options are 
supported for userland configuration[ie setting rotation on bootup, or 
configuring rotation in the Xorg.conf file]  This drivers sourcecode is 
located at drivers/gpu/tilcdc

There is the omap  frame buffer driver: Located at drivers/video/omap   
This driver requires LCD panel configuration information which is available 
for some LCD panels in the same directory as the driver.  Does this work 
for the BeagleBoneBlack?

There is the omap2 frame buffer driver: Located at 
drivers/video/omap2/omapfb.  This driver requires LCD panel configuration, 
of which many are already written - see drivers/video/omap2/displays for 
them.  Does this work for the BeagleBoneBlack?

There is the PVRSRVKVM Driver: Uses the built in SGX graphcis processor to 
accelerate graphics processing and offload processing from the CPU.  This 
driver may not work under Linux Kernel version 3.8.   According to the 
latest release notes, http://processors.wiki.ti.com/index.php/RN_4_10_00_01, 
version 4.10.00.01 works for the Linux 3.8 kernel.  From the release notes:

Validation information

*NOTE - *

*1. This release has been tested on AM parts only.* 

*2. This release is build tested only for 387x(TI814x) & 389x(TI816x) & DM 
parts.* 

*3. This release is build tested only against 3.8 kernel. *


The BBB uses a 335x processor, not 387x or 389x - so it does not appear 
that it has been tested for the BBB, but it has been tested for the 3.8 
kernel.

Also note that the above statement is contradicted later in the release 
notes by:

Kernel(Linux PSP) versions supported or used for validation

Please note that this release has been tested only on AM devices. No 
testing has been done on the DM parts. Only the following devices have been 
tested & details below -


   - AM335x - 3.2 kernel - 
  http://arago-project.org/git/projects/linux-am33x.git
   - 
  - AM335x Linux PSP 04.06.00.10
 - Branch – v3.2-staging, TAG - v3.2_AM335xPSP_04.06.00.10-rc1, 
 commit id -c8cce6279f5c126cbf6b6054f1ea0148bfc19511
  

   - AM35xx/AM37xx - 2.6.37 kernel
   - 
  - Linux PSP Release : 04.02.00.07.
 - Display drivers with DSS2 support ie, CONFIG_OMAP2_DSS=y
  
 


My assumption is that the earlier statement overrides the later statement.

 To add to the confusion, many of these drivers are used in combination. 
 For example, you might have both the Omap 2 Framebuffer Driver AND the SGX 
Driver installed.  The SGX driver overrides some of the functions in the 
Omap driver(?).   Xorg configuration would be for the Omap driver, not the 
SGX driver[?]

Please correct any of my misassumptions in the above.

-- 
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/groups/opt_out.

Re: [beagleboard] servo?

[Marcus Diogo]

adafruit Adafruit_BBIO does not work with ubuntu precise. :(


2013/7/17 James Ronald 

> Google *BeagleBone Black servo* and find:
>
> Tutorial: Controlling a Servo with a BeagleBone Black
> learn.adafruit.com/controlling-a-servo-with-a-beaglebone-black/overview*
> *
>
>
> On Wed, Jul 17, 2013 at 8:50 PM, Gerald Coley wrote:
>
>> No it will not work. that is what I am trying to say. You need a driver
>> that will drive the servo lay and can stand the 5V current. Take a look at
>> the LED drivers on the BeagleBone Black schematic. The right transistor in
>> a similar configuration can control the servo.
>>
>> Here is information on what the limits of the board expansion headers
>> are. Voltage is 3.3V max.
>>
>>
>> http://circuitco.com/support/index.php?title=BeagleBoneBlack#Expansion_Header_Usage
>>
>> Do a Google search for motor drivers or servo drivers for various
>> circuits that will work.
>>
>> Gerald
>>
>>
>> On Wed, Jul 17, 2013 at 7:33 PM,  wrote:
>>
>>> I will have to look up what you are referring to about a driver. I am
>>> using the 5v from the BBB pin P9_5. Will it work using the P9_3 (3.3V)?
>>> I have used the Arduino a lot and the typical setup is power and ground
>>> from the board to the servo and then the signal of the servo connected to a
>>> PWM pin. That was what I was expecting with the BBB and it's PWM. Is there
>>> an example online or a tutorial?
>>>
>>>
>>> On Wednesday, July 17, 2013 7:19:43 PM UTC-5, Gerald wrote:
>>>
 OK. So, basically I figure you may have 2-3 more tries before
 the processor blows up. The processor is 3.3V max and the I/O pins cannot
 sink enough current to make the servo turn. Having 5V on the pins will
 damage the processor. You need a driver between the processor and the 
 servo.


 Gerald


 On Wed, Jul 17, 2013 at 7:09 PM,  wrote:

> JR SERVO
> NES-505
>
> 5V on the red wire from BeagleBone Black. Brown wire to the ground on
> the BBB. Orange wire to 'P8_13'
>
> I am using an analogWrite('P8_13',0.5,200);
>
> I have read that servos typicly use 200 Hz but might use as low as 50
> Hz which I have tried. I know the analogWrite takes a 0 - 1 value for the
> second augment but I don't even know how that will translate to angle for
> the servo.
>
>
>
> On Wednesday, July 17, 2013 6:59:56 PM UTC-5, Gerald wrote:
>
>> What Hardware driver are you using to drive the servo? What is the
>> voltage on the servo?
>>
>> Gerald
>>
>>
>>
>> On Wed, Jul 17, 2013 at 6:37 PM,  wrote:
>>
>>> I am new to bonescript having just received my beaglebone black. I
>>> am trying to drive a servo but I can not seem to figure out what to do. 
>>> I
>>> can use PWM to fade an LED but I can't get the servo to respond. Does
>>> anyone know how to drive a servo with a beaglebone black and bonescript?
>>>
>>> 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...@**googlegroups.**com.
>>>
>>> For more options, visit 
>>> https://groups.google.com/**grou**ps/opt_out
>>> .
>>>
>>>
>>>
>>
>>  --
> 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/**groups/opt_out
> .
>
>
>

  --
>>> 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/groups/opt_out.
>>>
>>>
>>>
>>
>>  --
>> 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/groups/opt_out.
>>
>>
>>
>
>  --
> 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 beag

[beagleboard] elapsed time microseconds c++

[ignacio . matador]

hello,

I tried several ways ( clock(), gettimeofday()..) but I can get the proper 
way to measure the elapsed time in microseconds.

I am using eclipse to program in ansi c. Could anybody help me about how to 
measure the elapsed time in microsecond? Could it be possible to enclosed 
the code that I should use? 

thank you so much and sorry for the inconveniences

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/groups/opt_out.

Re: [beagleboard] Re: LCD7 Portrait mode in GDM

[Gerald Coley]

Yes, Circuitco is the company. But the Wiki is not run by Circuitco. I am
not Circuitco.

Gerald


This is the *official BeagleBone Black Wiki* maintained and supported
by BeagleBoard.org a non-profit 501(C) organization.

It is currently hosted by Circuitco, the manufacturer of the BeagleBone Black.



On Thu, Sep 26, 2013 at 2:20 PM, Louis McCarthy  wrote:

> This configuration was performed on the LCD7-00A4 cape by Beagleboardtoys.
> I'm not sure of the exact organization of CircuitCo, but aren't they one in
> the same (BBT and CC)?
>
> Louis
>
>
> On Thursday, September 26, 2013 2:09:11 PM UTC-5, Gerald wrote:
>
>> That suggestion needs to go to the supplier of the cape.
>>
>> Gerald
>> .
>>
>>
>> On Thu, Sep 26, 2013 at 2:08 PM, garyamort  wrote:
>>
>>>
>>>
>>> On Thursday, September 26, 2013 2:15:39 PM UTC-4, Louis McCarthy wrote:
>>>
 Success!

 I installed fbdev (2:0.4.2-r17.0.12):
 opkg install xf86-video-fbdev

 I then enabled fbdev in X11

>>>
>>> Thanks for taking the time to troubleshoot all this Louis!  I took the
>>> liberty of emailing Gerald Coley directly via the e-mail link on
>>> CircuitCo's wiki [http://circuitco.com/support/**index.php?title=**
>>> BeagleBoneBlack]
>>> and asked him to add your config info to the wiki as screen rotation seems
>>> to be a recurring issue with the BBB, and at least having a good "how to"
>>> for one flavor of linux should point the way for others!
>>>
>>> --
>>> 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/**groups/opt_out
>>> .
>>>
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: LCD7 Portrait mode in GDM

[garyamort]

Thanks Gerald, I went ahead and sent that suggestion on the CircuitCo 
directly.

On Thursday, September 26, 2013 3:09:11 PM UTC-4, Gerald wrote:
>
> That suggestion needs to go to the supplier of the cape.
>
> Gerald
> . 
>
>
> On Thu, Sep 26, 2013 at 2:08 PM, garyamort 
> > wrote:
>
>>
>>
>> On Thursday, September 26, 2013 2:15:39 PM UTC-4, Louis McCarthy wrote:
>>
>>> Success! 
>>>
>>> I installed fbdev (2:0.4.2-r17.0.12):
>>> opkg install xf86-video-fbdev
>>>
>>> I then enabled fbdev in X11
>>>
>>
>> Thanks for taking the time to troubleshoot all this Louis!  I took the 
>> liberty of emailing Gerald Coley directly via the e-mail link on 
>> CircuitCo's wiki [
>> http://circuitco.com/support/index.php?title=BeagleBoneBlack] and asked 
>> him to add your config info to the wiki as screen rotation seems to be a 
>> recurring issue with the BBB, and at least having a good "how to" for one 
>> flavor of linux should point the way for others!
>>  
>> -- 
>> 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/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: LCD7 Portrait mode in GDM

[Louis McCarthy]

This configuration was performed on the LCD7-00A4 cape by Beagleboardtoys. 
I'm not sure of the exact organization of CircuitCo, but aren't they one in 
the same (BBT and CC)? 

Louis


On Thursday, September 26, 2013 2:09:11 PM UTC-5, Gerald wrote:
>
> That suggestion needs to go to the supplier of the cape.
>
> Gerald
> . 
>
>
> On Thu, Sep 26, 2013 at 2:08 PM, garyamort 
> > wrote:
>
>>
>>
>> On Thursday, September 26, 2013 2:15:39 PM UTC-4, Louis McCarthy wrote:
>>
>>> Success! 
>>>
>>> I installed fbdev (2:0.4.2-r17.0.12):
>>> opkg install xf86-video-fbdev
>>>
>>> I then enabled fbdev in X11
>>>
>>
>> Thanks for taking the time to troubleshoot all this Louis!  I took the 
>> liberty of emailing Gerald Coley directly via the e-mail link on 
>> CircuitCo's wiki [
>> http://circuitco.com/support/index.php?title=BeagleBoneBlack] and asked 
>> him to add your config info to the wiki as screen rotation seems to be a 
>> recurring issue with the BBB, and at least having a good "how to" for one 
>> flavor of linux should point the way for others!
>>  
>> -- 
>> 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/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: BeagleBone Black - No HDMI Output

[Gerald Coley]

It does not. It was too complicated for them to do as I understand it. I
think the EDID was a little overwhelming.

Gerald


On Thu, Sep 26, 2013 at 2:15 PM, Tomas Espeleta wrote:

> Yeah.. it's a bit confusing: their page actually makes you think they do
> have support for it. I'll ask.
> Thank you very much Gerald!
>
>
> On Thu, Sep 26, 2013 at 9:08 PM, Gerald Coley wrote:
>
>> As I understand it, the SDK from TI has no support for the HDMI display.
>> But, I would ask them and see what they say.
>>
>> Gerald
>>
>>
>>
>> On Thu, Sep 26, 2013 at 1:45 PM,  wrote:
>>
>>>  Could be this the reason why I can have a perfectly working
>>> non-accelerated-android working on my BBB (followed
>>> http://icculus.org/~hendersa/android/, with Robert Nelson's 3.8
>>> kernel), while follwing these instructions
>>> http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide
>>>  I
>>> get a "Video format not supported" on my TV?
>>>
>>> I've tried changing uEnv.txt, changing the resolution to a very standard
>>> one, and it looked like it was ignored Is there any way to workaround
>>> this?
>>>
>>>
>>> optargs=video=HDMI-A-1:640x480@60
>>>
>>>
>>> I'd like to see TI's demo on my tv... even if it's with the old kernel
>>> :)
>>>
>>>
>>> On Thursday, 26 September 2013 17:20:48 UTC+2, Gerald wrote:

 The display driver takes over once it is launched. It does not use the
 uENV.txt parameters. It uses the EDID.

 Gerald

  --
>>> 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/groups/opt_out.
>>>
>>
>>  --
>> 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/0fMTXLPuGS4/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/groups/opt_out.
>>
>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: BeagleBone Black - No HDMI Output

[Tomas Espeleta]

Yeah.. it's a bit confusing: their page actually makes you think they do
have support for it. I'll ask.
Thank you very much Gerald!


On Thu, Sep 26, 2013 at 9:08 PM, Gerald Coley wrote:

> As I understand it, the SDK from TI has no support for the HDMI display.
> But, I would ask them and see what they say.
>
> Gerald
>
>
>
> On Thu, Sep 26, 2013 at 1:45 PM,  wrote:
>
>> Could be this the reason why I can have a perfectly working
>> non-accelerated-android working on my BBB (followed
>> http://icculus.org/~hendersa/android/, with Robert Nelson's 3.8 kernel),
>> while follwing these instructions
>> http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide
>>  I
>> get a "Video format not supported" on my TV?
>>
>> I've tried changing uEnv.txt, changing the resolution to a very standard
>> one, and it looked like it was ignored Is there any way to workaround
>> this?
>>
>>
>> optargs=video=HDMI-A-1:640x480@60
>>
>>
>> I'd like to see TI's demo on my tv... even if it's with the old kernel
>> :)
>>
>>
>> On Thursday, 26 September 2013 17:20:48 UTC+2, Gerald wrote:
>>>
>>> The display driver takes over once it is launched. It does not use the
>>> uENV.txt parameters. It uses the EDID.
>>>
>>> Gerald
>>>
>>>  --
>> 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/groups/opt_out.
>>
>
>  --
> 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/0fMTXLPuGS4/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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: BeagleBone Black - No HDMI Output

[Gerald Coley]

As I understand it, the SDK from TI has no support for the HDMI display.
But, I would ask them and see what they say.

Gerald



On Thu, Sep 26, 2013 at 1:45 PM,  wrote:

> Could be this the reason why I can have a perfectly working
> non-accelerated-android working on my BBB (followed
> http://icculus.org/~hendersa/android/, with Robert Nelson's 3.8 kernel),
> while follwing these instructions
> http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide
>  I
> get a "Video format not supported" on my TV?
>
> I've tried changing uEnv.txt, changing the resolution to a very standard
> one, and it looked like it was ignored Is there any way to workaround
> this?
>
>
> optargs=video=HDMI-A-1:640x480@60
>
>
> I'd like to see TI's demo on my tv... even if it's with the old kernel   :)
>
>
> On Thursday, 26 September 2013 17:20:48 UTC+2, Gerald wrote:
>>
>> The display driver takes over once it is launched. It does not use the
>> uENV.txt parameters. It uses the EDID.
>>
>> Gerald
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] Re: LCD7 Portrait mode in GDM

[garyamort]

On Thursday, September 26, 2013 2:15:39 PM UTC-4, Louis McCarthy wrote:
>
> Success! 
>
> I installed fbdev (2:0.4.2-r17.0.12):
> opkg install xf86-video-fbdev
>
> I then enabled fbdev in X11
>

Thanks for taking the time to troubleshoot all this Louis!  I took the 
liberty of emailing Gerald Coley directly via the e-mail link on 
CircuitCo's wiki [
http://circuitco.com/support/index.php?title=BeagleBoneBlack] and asked him 
to add your config info to the wiki as screen rotation seems to be a 
recurring issue with the BBB, and at least having a good "how to" for one 
flavor of linux should point the way for others!

-- 
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/groups/opt_out.

Re: [beagleboard] Re: LCD7 Portrait mode in GDM

[Gerald Coley]

That suggestion needs to go to the supplier of the cape.

Gerald
.


On Thu, Sep 26, 2013 at 2:08 PM, garyamort  wrote:

>
>
> On Thursday, September 26, 2013 2:15:39 PM UTC-4, Louis McCarthy wrote:
>
>> Success!
>>
>> I installed fbdev (2:0.4.2-r17.0.12):
>> opkg install xf86-video-fbdev
>>
>> I then enabled fbdev in X11
>>
>
> Thanks for taking the time to troubleshoot all this Louis!  I took the
> liberty of emailing Gerald Coley directly via the e-mail link on
> CircuitCo's wiki [
> http://circuitco.com/support/index.php?title=BeagleBoneBlack] and asked
> him to add your config info to the wiki as screen rotation seems to be a
> recurring issue with the BBB, and at least having a good "how to" for one
> flavor of linux should point the way for others!
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: BeagleBone Black - No HDMI Output

[tomas . espeleta]

Could be this the reason why I can have a perfectly working 
non-accelerated-android working on my BBB (followed 
http://icculus.org/~hendersa/android/, with Robert Nelson's 3.8 kernel), 
while follwing these instructions 
http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_DeveloperGuide
 I 
get a "Video format not supported" on my TV?

I've tried changing uEnv.txt, changing the resolution to a very standard 
one, and it looked like it was ignored Is there any way to workaround 
this?


optargs=video=HDMI-A-1:640x480@60


I'd like to see TI's demo on my tv... even if it's with the old kernel   :)


On Thursday, 26 September 2013 17:20:48 UTC+2, Gerald wrote:
>
> The display driver takes over once it is launched. It does not use the 
> uENV.txt parameters. It uses the EDID.
>
> Gerald
>
>

-- 
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/groups/opt_out.

[beagleboard] Re: How can I improve processing time on BB?

[garyamort]

On Thursday, September 26, 2013 8:24:38 AM UTC-4, garyamort wrote:
>
>
>
> On Thursday, September 26, 2013 4:47:17 AM UTC-4, 서재필 wrote:
>>
>> I'm trying to use Beagle Board for real-time audio-processing.
>>
>>
Oh, I just ran across this link[again] when trying to fiddle with my 
desktop sound  - it has no direct bearing for me  but I'd suggest you take 
a look at it.

If your doing Real Time Audio Processing, there is a group dedicated to 
doing just that and have produced a bunch of tools in an open source 
package for working on it.  It's called "Jack", http://jackaudio.org/

Note that the consensus of the Jack Community[which includes professionals 
in audio development] is that the Real Time Kernel options aren't needed 
for most use cases.  http://jackaudio.org/realtime_vs_realtime_kernel

*"No. Realtime scheduling is available on all Linux systems no matter what 
kernel they use, and current versions of JACK use it by default. A kernel 
built with the realtime patches (an "RT kernel") is needed only if:*


   - *You want to run JACK with very low latency settings that require 
  realtime performance that can only be achieved with an RT kernel*
  - *Your hardware configuration triggers poor latency behaviour which 
  might be improved with an RT kernel*
   
*Most users do not need an RT kernel in order to use JACK, and most will be 
happy using settings that are effective without an RT kernel."*


Personally, I'm such an extremely lazy programmer that I'd START with 
implementing my application using Jack and a reasonably sized tempfs drive 
to store files while working - and then ask my performance tuning questions 
on their mailing list as 80% of the issues won't be related to the hardware.



-- 
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/groups/opt_out.

Re: [beagleboard] Re: Extracting eMMC contents using FAT formatted card

[Alexander Holler]

Am 26.09.2013 20:21, schrieb Alexander Holler:



autorun.sh:
#!/bin/sh
echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger
dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M
sync
echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger


I think using dd and creating an image is a pretty bad way to build a
backup.

I would suggest to use

sfdisk -d /dev/foo >sfdisk.emmc.txt
mount emmc
tar cpjf -C emmc .
umount emmc


Of course, it should be

tar cpjf emmc.tar.bz2 -C emmc .

and another tar might be necessary for the second partition.

And putting such a script together with busybox into an in-kernel 
initramfs, and people would just have to build a card with one file, the 
uImage.


Regards,

Alexander Holler


--
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/groups/opt_out.

Re: [beagleboard] Re: Anyone interested in writing or helping with a media playback app?

[Dieter Wirz]

On Thu, Sep 26, 2013 at 3:50 PM, garyamort  wrote:
> On Thursday, September 26, 2013 2:24:11 AM UTC-4, Mike Langensiepen wrote:
>> Is there an app or does anyone fancy giving me a price for writing an app
>> do to the following:
>> Play an ambient audio/video track (whatever format needed)
>> On receiving a trigger input switch to playing another specified
>> audio/video track
>> When 2nd track is finished go back to playing the ambient track.
>>
>> Tracks would need to be full HD
ooops... poor BB

> Of course this moves the time/cost from "writing an app" to "configuring the
> system" as you will need to setup your linux distribution, have it start the
> x-windows environment upon bootup[but not a desktop, just the windowing
> system
No - you don't need X, you can run videos in framebuffer mode.
Search the net for
framebuffer gstreamer mplayer etc. in combination with BB(B)

HTH

-- 
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/groups/opt_out.

[beagleboard] Re: Using a Current Sensor thats Analog Output Is >1.8v

[jsylvestre14]

Ok thanks for your help.  Losing a bit of range isn't a big deal.  I just 
wanted to confirm that voltage divider to work.

On Tuesday, September 24, 2013 2:29:11 PM UTC-5, jsylve...@bsmschool.org 
wrote:
>
> Hello,  
>
> I am using a current sensor  
> http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=111040360152&var=410166550830
>  that 
> outputs analog voltages >1.8v, the maximum voltage the Beaglebone's AIn can 
> accept.  
>
> If I were to use a voltage divider with a capacitor, would this work for 
> my application?
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Extracting eMMC contents using FAT formatted card

[Alexander Holler]

autorun.sh:
#!/bin/sh
echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger
dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M
sync
echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger


I think using dd and creating an image is a pretty bad way to build a 
backup.


I would suggest to use

sfdisk -d /dev/foo >sfdisk.emmc.txt
mount emmc
tar cpjf -C emmc .
umount emmc

Regards,

Alexander Holler

--
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/groups/opt_out.

[beagleboard] Re: LCD7 Portrait mode in GDM

[Louis McCarthy]

Success! 

I installed fbdev (2:0.4.2-r17.0.12):
opkg install xf86-video-fbdev

I then enabled fbdev in X11 by editing the "Device" section of 
/etc/X11/xorg.conf to:
Section "Device"
Identifier  "Builtin Default fbdev Device 0"
Driver  "fbdev"
Option "Rotate" "CCW"
EndSection

That rotated the screen, but the touchscreen needed to swap x and y, and 
invert x, so I added two Options to the "evdev touchscreen catchall" 
identifier of /usr/share/X11/xorg.conf.d/10-evdev.conf:
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "SwapAxes" "true"
Option "InvertX" "true"
EndSection

Which worked for the base X server (clock face pointer and login screen), 
but as soon as the default user logged in, the touchscreen lost its swap 
axes option. I could run: 
xinput --set-prop "ti-tsc" "Evdev Axes Swap" 1
from an xterm window, to get it to work again, but I wanted it to be 
automatic. 

At first I tried adding it to the .xprofile file, but that didn't work. I 
then found that by modifying /etc/pointercal.xinput to the following:
xinput set-int-prop "ti-tsc" "Evdev Axis Calibration" 32 3733 367 79 
3992;xinput 
set-int-prop "ti-tsc" "Evdev Axes Swap" 8 1;
everything worked on a reboot.

Thanks for your help, Gary. I wish it would have worked with modesetting 
and xrandr, but I will leave that as an exercise for another user :)

And for the HDMI vs LCD driver, as far as I know, the base (internal to the 
AM33xx) lcd controller is used for both. I looked at the source dts file 
for HDMI and it defines a similar fb section as the LCD7 dts file. But, at 
this point, I don't need to dig any deeper

Louis


On Wednesday, September 25, 2013 6:39:14 PM UTC-5, garyamort wrote:
>
>
>
> On Wednesday, September 25, 2013 3:21:14 PM UTC-4, Louis McCarthy wrote:
>>
>> Thanks for sticking with me. Knowing that KMS is a type helps me 
>> understand more about the video system.
>>
>
> Hmm, learn something new.  modesetting is a driver too!  I thought it just 
> referred to the KMS type of driver, but it also refers to a fallback driver 
> for X11.
>
> And it only supports a couple of options, one of which is not rotate!
>
>
> If your using some form of debian variant, you can try:
> "sudo apt-get install xserver-xorg-video-fbdev"
>
> Install the basic fbdev driver and give that a shot.
>
> You can also try xserver-xorg-video-omap and xserver-xorg-video-omapfb
> [the name may be slightly different, so you can also try "apt-cache search 
> fbdev", omap and omapfb
>
>
> Now the bad news: I /think/ none of the above will work because they will 
> only be used by the HDMI display by default.  Checking the device tree 
> source for BB-BONE-LCD7 I see lines such as:
> /* Settings for ThreeFive S9700RTWV35TR / LCD7 cape: */
> panel {
> compatible = "tilcdc,panel";
>
> My gut feeling is that this specifies the driver to use: ie use the 
> tildc-panel driver.  You could try exiting x-windows and then running
> "sudo modprobe -v panel-generic-dpi" [might need to do "sudo modprobe -v 
> panel-generic-dpi.ko"]
>
> If that succeeds, then reload x-windows and check the x11 logs to see if 
> the driver has changed.
>
>
>

-- 
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/groups/opt_out.

[beagleboard] Re: Extracting eMMC contents using FAT formatted card

[Jason Kridner]

On Thursday, September 26, 2013 1:26:27 PM UTC-4, David Anders wrote:

> http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents 
>

Added. Feedback welcome.
 

>
> is a good place to start. i am working with bill traynor to organize 
> howto pages along with other specific category groups... 
>
> Dave 
>
> On 09/26/2013 12:23 PM, Jason Kridner wrote: 
> > On Thursday, September 26, 2013 1:20:18 PM UTC-4, David Anders wrote: 
> > 
> >> Jason, 
> >> 
> >> shouldn't this info go up on the elinux.org wiki? 
> >> 
> > Absolutely. Any recommendation on the page location? I will upload it 
> right 
> > away. 
> >   
> > 
> >> Dave 
> >> 
> >> On 09/26/2013 12:16 PM, Jason Kridner wrote: 
> >>> There are lots of ways to extract the contents of the eMMC to save off 
> >> and 
> >>> reuse. I'm proposing a method using Buildroot and an initramfs such 
> that 
> >>> you can simply drop a few files from a .zip onto a normal, 
> FAT-formatted 
> >> SD 
> >>> card to perform the extraction. There are several things really handy 
> >> here, 
> >>> such as the ability to edit autorun.sh to be whatever script you want 
> to 
> >>> run on your board at boot. In the archive, I only have the necessary 
> >>> autorun.sh for *saving* your eMMC content. The flip-side is provided 
> >> here 
> >>> in the text such that you need to go through a couple of steps before 
> >> you 
> >>> trash your eMMC. 
> >>> 
> >>> The steps for saving off your eMMC contents to a file: 
> >>> * Get a 4GB or larger uSD card that is FAT formatted. 
> >>> * Download 
> >> https://s3.amazonaws.com/beagle/beagleboneblack-save-emmc.zipand 
> >>> extract the contents onto your uSD card. 
> >>> * Eject uSD card from your computer, insert into powered-off 
> BeagleBone 
> >>> Black and apply power to your board. 
> >>> * You'll notice USR0 (the LED closest to the S1 button in the corner) 
> >> will 
> >>> (after about 20 seconds) start to blink steadily, rather than the 
> >>> double-pulse "heartbeat" pattern that is typical when your BeagleBone 
> >> Black 
> >>> is running the typical Linux kernel configuration. 
> >>> * It'll run for a bit under 10 minutes and then USR0 will stay ON 
> >> steady. 
> >>> That's your cue to remove power, remove the uSD card and put it back 
> >> into 
> >>> your computer. 
> >>> * You should see a file called BeagleBoneBlack-eMMC-image-X.img, 
> >> where 
> >>> X is a set of random numbers. Save off this file to use for 
> >> restoring 
> >>> your image later. 
> >>> 
> >>> Because the date won't be set on your board, you might want to adjust 
> >> the 
> >>> date on the file to remember when you made it. Delete the file if you 
> >> want 
> >>> to make room for a new backup image. For storage on your computer, 
> these 
> >>> images will typically compress very well, so use your favorite 
> >> compression 
> >>> tool. 
> >>> 
> >>> To restore the file, make sure there is a valid 
> >>> BeagleBoneBlack-eMMC-image-.img file on the uSD card and edit 
> >>> autorun.sh with your favorite text editor to contain the following: 
> >>> #!/bin/sh 
> >>> echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger 
> >>> dd if=/mnt/BeagleBoneBlack-eMMC-image-X.img of=/dev/mmcblk1 bs=10M 
> >>> sync 
> >>> echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger 
> >>> 
> >>> *NOTE*: Be certain to replace the 'X' above with the proper name 
> of 
> >>> your image file. 
> >>> 
> >>> This image was built using Buildroot. The sources are at 
> >>> https://github.com/jadonk/buildroot with tag save-emmc-0.0.1. 
> Download 
> >> via 
> >>> https://github.com/jadonk/buildroot/releases/tag/save-emmc-0.0.1 or 
> >> clone 
> >>> the git repo. It is a small fork from 
> >>> git://git.buildroot.net/buildroottag 
> >>> e9f6011617528646768e69203e85fe64364b7efd. 
> >>> 
> >>> To build, 'make beagleboneblack_defconfig; make; ./mkuimage.sh'. 
>  Output 
> >>> files (am335x-boneblack.dtb, MLO, u-boot.img and uImage) will be in 
> the 
> >>> output/images subdirectory. The following files were created manually. 
> >>> 
> >>> uEnv.txt: 
> >>> bootpart=0:1 
> >>> bootdir= 
> >>> fdtaddr=0x81FF 
> >>> optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
> >>> uenvcmd=load mmc 0 ${loadaddr} uImage;run loadfdt;setenv bootargs 
> >>> console=${console} ${optargs};bootm ${loadaddr} - ${fdtaddr} 
> >>> 
> >>> autorun.sh: 
> >>> #!/bin/sh 
> >>> echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger 
> >>> dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img 
> bs=10M 
> >>> sync 
> >>> echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger 
> >>> 
> >>> The kernel is based on 
> >>> 
> >> 
> https://github.com/beagleboard/kernel/commit/9fdb452245a58158a4bea787cdc663c17681bcfe,
>  
>
> >> 
> >>> but I applied the patches, added firmware and uploaded it to 
> >>> 
> >> 
> https://github.com/beagleboard/linux/commit/ddd36e546e53d3c493075bbebd6188ee843208f9to
>  
> >>> pull down in

Re: [beagleboard] Re: How can I improve processing time on BB?

[William Hermans]

^^^

Fifthly - Look into using the two PRU's to help offload some tasks. Also
look into using using specific external hardware to offload even more from
the CPU.

Could also be that your routines need some tightening up. Have you done any
cycle counting on your code ? Checked the generated ASM ?




On Thu, Sep 26, 2013 at 5:24 AM, garyamort  wrote:

>
>
> On Thursday, September 26, 2013 4:47:17 AM UTC-4, 서재필 wrote:
>>
>> I'm trying to use Beagle Board for real-time audio-processing.
>>
>> I bought this one because of these clock speed(1Ghz).
>>
>> My algorithm running time is about 0.6 ms for one frame in my
>> computer(window7, 2.6Ghz Quad-core).
>>
>> But when I run my algorithm on BB(Angstrom, 1Ghz), it spends about
>> 40ms for one frame.
>>
>> Isn't it ridiculous? Because clock speed defference is just 2 or max 3
>> times. But measuring processing speed is not.
>>
>> Wha'ts wrong with it?
>>
>
>
> Assuming that you can make a fair comparison of clock speed to
> performance[which you can't], your difference is over 10 times, not 2 or 3.
>  Your comparing a quad core device with a single core device.  Right off
> the bat this will cause issues since Linux is not real time operating
> system tuned for a specific set of tasks, it is a general operating system
> - so it is running multiple processes at the same time.  On your quad core
> device, you have some buffer since the running programs will be spread
> between different processors.  The Bone will be running everything on one
> core.
>
>
> Firstly, did you make sure to adjust the priority of your process to give
> it a big share of the processor space?  If running from the command line,
> for example "runmyprogram" instead run it as "sudo nice --adjustment=-20
> runmyprogram*"*
>
> Secondly, you have to consider what your doing.  Your doing audio
> processing.  What do musicians do for that? They use Linux with the Real
> Time performance enhancements installed.  This lets you give your process
> higher priority over almost everything else, including most of the
> operating system.  So you need to recompile your kernel for that.
>
> Thirdly, your processing a large amount of data, correct?  And your trying
> to store it on the "hard drive" I bet - which is a slow MMC card[as opposed
> to your fast SATA hard drive on your windows box].  The simple solution
> there is to sacrifice some memory and setup a ram disk.  Check your
> /etc/fstab file - you probably already have a small ramdisk setup there to
> map to the /temp directory using the tmpfs file system.  Just increase that
> up to 128M and do all your file processing in the /temp folder.
>
> Fourthly, avoid disparaging seeming comments like "isn't it ridiculous"
> and instead phrase them in such a way as to take responsibility for the
> failing such as "I'm sure I am doing something wrong.  What methods are
> there to increase performance?"
>
> Speaking for myself personally, it makes the difference when I answer
> between my taking the time to do a few google searches and provide links to
> articles explaining how to implement something vs just giving the answers
> and leaving looking up implementation to the other party.
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Apple full numeric [Aluminium] keyboard and internal hub does not work

[William Hermans]

Hi Sushant Khanna,

I have read about similar issues with all sorts of devices, and as far as I
can tell the type of hub used can be a big factor in this situation. First,
if you have not tried checking if each device works by its self on the USB
host port ( individually ) I would do so now.

So, I think in this case I would check to see if the keyboard works by its
self with nothing else plugged into it. If it does, then yes this would be
a bit of a quandary, as putting this specific keyboard on another hub may
make the situation worse. All may not be lost though, there could be a
kernel driver module for this specific keyboard, although I would not hold
my breathe.

You may want to try using a different keyboard / mouse, with a known good
working USB hub( if you have such laying around ). Spending money on
something and not having that work either . . . yes, I know would not be
ideal. Said hub should also be self powered.

As to whether you're needing an external power supply I am not sure, and
Gerald would know better than I. However we all could use more information
to help us know what exactly is happening. Such as the serial debug output
at the time the board is powered up with the keyboard and mouse plugged
into the USB port. Sometimes, it can not be overstated how handy a serial
debug interface can be . . .


On Thu, Sep 26, 2013 at 6:35 AM, Gerald Coley wrote:

> Not sure it will fix your issue, but the image you are using is very old.
> I suggest that you try a more up to date image on your board.
>
> http://circuitco.com/support/BeagleBoneBlack
>
>
> Gerald
>
>
>
> On Thu, Sep 26, 2013 at 12:56 AM,  wrote:
>
>> Hi Guys
>>
>> Someone asked a similar question before, but no one had an answer then.
>> I was going to give up and buy another keyboard but when I googled a bit
>> more, I saw that a lot of people are able to use it with their beaglebone
>> black.
>>
>> I will explain the conditions and problem in details.
>>
>> I have a beaglebone black powered up via a USB charger (NOT via the 5V DC
>> adapter)
>> I have it connected to a display via a microHDMI cable.
>> I am running Angstrom. Updated to 4.09.2013 image. (emmc boot)
>>
>> When I plugged in a normal wired optical mouse, it powered up and I was
>> able to use it.
>> I then used an Apple keyboard as described in the title and plugged the
>> mouse to its internal hub on the sides. Nothing worked, both did not show
>> any signs of being powered up.
>> I of course rebooted and checked *lsusb *output. I could see the Apple
>> device listed there.
>>
>> Is this a driver issue or a power supply problem?
>> Kinda new, so help me out please.
>>
>> 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/groups/opt_out.
>>
>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] Re: Extracting eMMC contents using FAT formatted card

[David Anders]

http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents

is a good place to start. i am working with bill traynor to organize 
howto pages along with other specific category groups...


Dave

On 09/26/2013 12:23 PM, Jason Kridner wrote:

On Thursday, September 26, 2013 1:20:18 PM UTC-4, David Anders wrote:


Jason,

shouldn't this info go up on the elinux.org wiki?


Absolutely. Any recommendation on the page location? I will upload it right
away.
  


Dave

On 09/26/2013 12:16 PM, Jason Kridner wrote:

There are lots of ways to extract the contents of the eMMC to save off

and

reuse. I'm proposing a method using Buildroot and an initramfs such that
you can simply drop a few files from a .zip onto a normal, FAT-formatted

SD

card to perform the extraction. There are several things really handy

here,

such as the ability to edit autorun.sh to be whatever script you want to
run on your board at boot. In the archive, I only have the necessary
autorun.sh for *saving* your eMMC content. The flip-side is provided

here

in the text such that you need to go through a couple of steps before

you

trash your eMMC.

The steps for saving off your eMMC contents to a file:
* Get a 4GB or larger uSD card that is FAT formatted.
* Download

https://s3.amazonaws.com/beagle/beagleboneblack-save-emmc.zipand

extract the contents onto your uSD card.
* Eject uSD card from your computer, insert into powered-off BeagleBone
Black and apply power to your board.
* You'll notice USR0 (the LED closest to the S1 button in the corner)

will

(after about 20 seconds) start to blink steadily, rather than the
double-pulse "heartbeat" pattern that is typical when your BeagleBone

Black

is running the typical Linux kernel configuration.
* It'll run for a bit under 10 minutes and then USR0 will stay ON

steady.

That's your cue to remove power, remove the uSD card and put it back

into

your computer.
* You should see a file called BeagleBoneBlack-eMMC-image-X.img,

where

X is a set of random numbers. Save off this file to use for

restoring

your image later.

Because the date won't be set on your board, you might want to adjust

the

date on the file to remember when you made it. Delete the file if you

want

to make room for a new backup image. For storage on your computer, these
images will typically compress very well, so use your favorite

compression

tool.

To restore the file, make sure there is a valid
BeagleBoneBlack-eMMC-image-.img file on the uSD card and edit
autorun.sh with your favorite text editor to contain the following:
#!/bin/sh
echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger
dd if=/mnt/BeagleBoneBlack-eMMC-image-X.img of=/dev/mmcblk1 bs=10M
sync
echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger

*NOTE*: Be certain to replace the 'X' above with the proper name of
your image file.

This image was built using Buildroot. The sources are at
https://github.com/jadonk/buildroot with tag save-emmc-0.0.1. Download

via

https://github.com/jadonk/buildroot/releases/tag/save-emmc-0.0.1 or

clone

the git repo. It is a small fork from
git://git.buildroot.net/buildroottag
e9f6011617528646768e69203e85fe64364b7efd.

To build, 'make beagleboneblack_defconfig; make; ./mkuimage.sh'.  Output
files (am335x-boneblack.dtb, MLO, u-boot.img and uImage) will be in the
output/images subdirectory. The following files were created manually.

uEnv.txt:
bootpart=0:1
bootdir=
fdtaddr=0x81FF
optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
uenvcmd=load mmc 0 ${loadaddr} uImage;run loadfdt;setenv bootargs
console=${console} ${optargs};bootm ${loadaddr} - ${fdtaddr}

autorun.sh:
#!/bin/sh
echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger
dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M
sync
echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger

The kernel is based on


https://github.com/beagleboard/kernel/commit/9fdb452245a58158a4bea787cdc663c17681bcfe,


but I applied the patches, added firmware and uploaded it to


https://github.com/beagleboard/linux/commit/ddd36e546e53d3c493075bbebd6188ee843208f9to

pull down in the Buildroot makefile. The link to the source for the
firmware is in the commit.

I've applied to join the Buildroot mailing list to send these patches
upstream. The power management firmware is not yet loading properly, but
that is something I can look into.

Happy hacking!





--
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/groups/opt_out.

[beagleboard] is the perf tool available for BBB ?

[udai Muhammed]

Hello there, 

I am a TA for a class that uses BBB with Angstrom as a demo board and the 
perf tool is very much needed for couple projects the students have to work 
on. 

i couldn't find a perf installation repository to install it directly to 
the BBB and it seems you can't cross-compile it. 

anybody can help me with this ?

i tried Ubuntu and i installed linux-tools and the perf tool is in the bin 
directory but it doesn't do anything. 

when i run perf --help , the terminal will say that i can't find perf.


any ideas ?

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/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[David Anders]

Anguel,

circuitco responds to ALL emails sent to supp...@beagleboardtoys.com and 
supp...@boardzoo.com for products produced by circuitco. we have responded 
to a number of emails with questions about the jitter issue. we provide 
recommended configurations and setup for all of the products, however we 
sell the hardware independently for developers to do as they choose with 
it. i highlight that fact developers. we can not test every single 
software load out there for every single product. as such a developer is 
responsible for configuring their own software functionality. we provide a 
warranty and guarantee on the hardware along with full documentation. one 
of the ways we keep costs low is for these products to be community 
supported. if you are unhappy with the lcd cape, we will be happy to refund 
your money for both the cape and beaglebone black so that you may select 
something more to your liking. may i suggest the TI AM33x EVM platform? 
(https://estore.ti.com/TMDXEVM3358-AM335x-Evaluation-Module-P2714.aspx). it 
retails for $995USD.

thanks
Dave Anders
Circuitco

On Thursday, September 26, 2013 5:53:32 AM UTC-5, Anguel wrote:
>
> Gerald,
>
> CircuitCo support did not even answer my e-mail regarding the 
> non-functional touchscreen. 4D Systems at least admitted that this is a 
> well known problem. Once again: Why don't they clearly state on their LCD 
> product pages that the touchscreen does not work in latest Angstrom? I 
> really hope that customers see my thread before buying a LCD with 
> touchscreen.
>
> Anguel
>
>
> On Tuesday, September 24, 2013 3:15:23 PM UTC+2, Gerald wrote:
>>
>> That is what I was told by Circuitco. 
>>
>> Gerald
>>
>>
>> On Tue, Sep 24, 2013 at 12:55 AM, Anguel  wrote:
>>
>>> How do you know this is a X11 bug? I see the same bug with TS_LIB. It is 
>>> somewhere deep in the driver.
>>>
>>>
>>> On Monday, September 23, 2013 9:04:12 PM UTC+2, Gerald wrote:
>>> > As was previously indicated to you, this is an issue with X11, a bug. 
>>> If you will fix the X11 it should work fine. Or just use the latest 
>>> Angstrom build.
>>> >
>>> >
>>> > This is you decision as to how you handle it.
>>> >
>>> >
>>> >
>>> > Gerald
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, Sep 23, 2013 at 11:00 AM, Anguel  wrote:
>>> >
>>> >
>>> > Hi Terry,
>>> >
>>> > Nice to know that I am not the only one who cares about the 
>>> touchscreen. Neither CircuitCo nor 4D Systems seem to really care about the 
>>> problem. They sell the displays but don't reply to my e-mails anymore. I 
>>> also reported the problem on Beaglebone IRC but did not receive any help 
>>> there. I even tried tweaking a bit in the kernel but without success. I 
>>> just don't have the experience to dig deeper in the ADC drivers and chase 
>>> for the bug.
>>> >
>>> >
>>> > The latest patches were actually submitted by Zubair Lutfullah, he 
>>> seems to adapt them (from the TI driver developers who write them for the 
>>> older kernel afaik). Zubair told me that he already knew about the jitter 
>>> problem and gave me the following reply: "The touchscreen driver that was 
>>> patched in the linux kernel
>>> > was different compared to the old patches in the beaglebone
>>> > tree. And we try to keep the beaglebone tree close to the
>>> > mainline. The old 3.8 patches were ok. The
>>> > mainlined ones introduced this problem.. A fix would 
>>> require a comparison of the two drivers to
>>> > figure out what went wrong and upload a patch to the
>>> > mainline.. It would require time.."
>>> >
>>> > Unfortunately, Zubair is very busy right now. He also mailed his reply 
>>> to Koen Kooi, one of the main Angstrom developers (also works at CircuitCo 
>>> according to his Google+ profile). I am afraid that Koen is also very busy 
>>> and won't have the time to look into the issue. So we can just hope that 
>>> someone with more experience can fix the issue in the near future.
>>> >
>>> >
>>> > Regards,
>>> > Anguel
>>> >
>>> >
>>> >
>>> >
>>> > On Monday, September 23, 2013 7:08:36 AM UTC+2, terrys...@gmail.comwrote:
>>> >
>>> > Hi Anguel
>>> >
>>> >
>>> > I too have the same problem. I have a LCD4 and a LCD7 and both do the 
>>> same thing.
>>> > I suspect since the 4D Systems displays use the same drivers the 
>>> 4DCAPE-43T does the same thing, so it doesn't seem to be hardware related 
>>> at all since they use different brand touch screens.
>>> >
>>> >
>>> >
>>> > Have you had any reply out of CircuitCo?
>>> > Does CircuitCo actually write the drivers or is it someone else?
>>> > Can anyone help and point us to someone who wrote the drivers that we 
>>> can discuss this with?
>>> >
>>> >
>>> >
>>> > I know a number of other people who have these displays and experience 
>>> the exact same thing, so it is not just isolated to us 2 people.
>>> >
>>> >
>>> > Please can someone point us in the right direction?
>>> >
>>> >
>>> >
>>> > Thanks
>>> >

Re: [beagleboard] Boot fails with microSD: ** Bad partition specification mmc 1:2 **

[basile . se]

BINGO!

I run dos2unix and it booted even with the microSD inserted :)

Thanx a lot Stephen!

On Thursday, September 26, 2013 6:38:06 PM UTC+2, Stephen Agate wrote:
>
> > I thought (and hoped) the problem was due to the missing of CR-LF at the 
> end of the  uEnv.txt as I read in other posts, but it is not :(
>
> I have read that it must be in Unix format, but you imply yours is in DOS 
> format.
>
>
>

-- 
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/groups/opt_out.

[beagleboard] Re: Extracting eMMC contents using FAT formatted card

[Jason Kridner]

On Thursday, September 26, 2013 1:20:18 PM UTC-4, David Anders wrote:

> Jason, 
>
> shouldn't this info go up on the elinux.org wiki? 
>

Absolutely. Any recommendation on the page location? I will upload it right 
away.
 

>
> Dave 
>
> On 09/26/2013 12:16 PM, Jason Kridner wrote: 
> > There are lots of ways to extract the contents of the eMMC to save off 
> and 
> > reuse. I'm proposing a method using Buildroot and an initramfs such that 
> > you can simply drop a few files from a .zip onto a normal, FAT-formatted 
> SD 
> > card to perform the extraction. There are several things really handy 
> here, 
> > such as the ability to edit autorun.sh to be whatever script you want to 
> > run on your board at boot. In the archive, I only have the necessary 
> > autorun.sh for *saving* your eMMC content. The flip-side is provided 
> here 
> > in the text such that you need to go through a couple of steps before 
> you 
> > trash your eMMC. 
> > 
> > The steps for saving off your eMMC contents to a file: 
> > * Get a 4GB or larger uSD card that is FAT formatted. 
> > * Download 
> https://s3.amazonaws.com/beagle/beagleboneblack-save-emmc.zipand 
> > extract the contents onto your uSD card. 
> > * Eject uSD card from your computer, insert into powered-off BeagleBone 
> > Black and apply power to your board. 
> > * You'll notice USR0 (the LED closest to the S1 button in the corner) 
> will 
> > (after about 20 seconds) start to blink steadily, rather than the 
> > double-pulse "heartbeat" pattern that is typical when your BeagleBone 
> Black 
> > is running the typical Linux kernel configuration. 
> > * It'll run for a bit under 10 minutes and then USR0 will stay ON 
> steady. 
> > That's your cue to remove power, remove the uSD card and put it back 
> into 
> > your computer. 
> > * You should see a file called BeagleBoneBlack-eMMC-image-X.img, 
> where 
> > X is a set of random numbers. Save off this file to use for 
> restoring 
> > your image later. 
> > 
> > Because the date won't be set on your board, you might want to adjust 
> the 
> > date on the file to remember when you made it. Delete the file if you 
> want 
> > to make room for a new backup image. For storage on your computer, these 
> > images will typically compress very well, so use your favorite 
> compression 
> > tool. 
> > 
> > To restore the file, make sure there is a valid 
> > BeagleBoneBlack-eMMC-image-.img file on the uSD card and edit 
> > autorun.sh with your favorite text editor to contain the following: 
> > #!/bin/sh 
> > echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger 
> > dd if=/mnt/BeagleBoneBlack-eMMC-image-X.img of=/dev/mmcblk1 bs=10M 
> > sync 
> > echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger 
> > 
> > *NOTE*: Be certain to replace the 'X' above with the proper name of 
> > your image file. 
> > 
> > This image was built using Buildroot. The sources are at 
> > https://github.com/jadonk/buildroot with tag save-emmc-0.0.1. Download 
> via 
> > https://github.com/jadonk/buildroot/releases/tag/save-emmc-0.0.1 or 
> clone 
> > the git repo. It is a small fork from 
> > git://git.buildroot.net/buildroottag 
> > e9f6011617528646768e69203e85fe64364b7efd. 
> > 
> > To build, 'make beagleboneblack_defconfig; make; ./mkuimage.sh'.  Output 
> > files (am335x-boneblack.dtb, MLO, u-boot.img and uImage) will be in the 
> > output/images subdirectory. The following files were created manually. 
> > 
> > uEnv.txt: 
> > bootpart=0:1 
> > bootdir= 
> > fdtaddr=0x81FF 
> > optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
> > uenvcmd=load mmc 0 ${loadaddr} uImage;run loadfdt;setenv bootargs 
> > console=${console} ${optargs};bootm ${loadaddr} - ${fdtaddr} 
> > 
> > autorun.sh: 
> > #!/bin/sh 
> > echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger 
> > dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M 
> > sync 
> > echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger 
> > 
> > The kernel is based on 
> > 
> https://github.com/beagleboard/kernel/commit/9fdb452245a58158a4bea787cdc663c17681bcfe,
>  
>
> > but I applied the patches, added firmware and uploaded it to 
> > 
> https://github.com/beagleboard/linux/commit/ddd36e546e53d3c493075bbebd6188ee843208f9to
>  
> > pull down in the Buildroot makefile. The link to the source for the 
> > firmware is in the commit. 
> > 
> > I've applied to join the Buildroot mailing list to send these patches 
> > upstream. The power management firmware is not yet loading properly, but 
> > that is something I can look into. 
> > 
> > Happy hacking! 
> > 
>
>

-- 
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/gro

[beagleboard] Re: Extracting eMMC contents using FAT formatted card

[David Anders]

Jason,

shouldn't this info go up on the elinux.org wiki?

Dave

On 09/26/2013 12:16 PM, Jason Kridner wrote:

There are lots of ways to extract the contents of the eMMC to save off and
reuse. I'm proposing a method using Buildroot and an initramfs such that
you can simply drop a few files from a .zip onto a normal, FAT-formatted SD
card to perform the extraction. There are several things really handy here,
such as the ability to edit autorun.sh to be whatever script you want to
run on your board at boot. In the archive, I only have the necessary
autorun.sh for *saving* your eMMC content. The flip-side is provided here
in the text such that you need to go through a couple of steps before you
trash your eMMC.

The steps for saving off your eMMC contents to a file:
* Get a 4GB or larger uSD card that is FAT formatted.
* Download https://s3.amazonaws.com/beagle/beagleboneblack-save-emmc.zipand
extract the contents onto your uSD card.
* Eject uSD card from your computer, insert into powered-off BeagleBone
Black and apply power to your board.
* You'll notice USR0 (the LED closest to the S1 button in the corner) will
(after about 20 seconds) start to blink steadily, rather than the
double-pulse "heartbeat" pattern that is typical when your BeagleBone Black
is running the typical Linux kernel configuration.
* It'll run for a bit under 10 minutes and then USR0 will stay ON steady.
That's your cue to remove power, remove the uSD card and put it back into
your computer.
* You should see a file called BeagleBoneBlack-eMMC-image-X.img, where
X is a set of random numbers. Save off this file to use for restoring
your image later.

Because the date won't be set on your board, you might want to adjust the
date on the file to remember when you made it. Delete the file if you want
to make room for a new backup image. For storage on your computer, these
images will typically compress very well, so use your favorite compression
tool.

To restore the file, make sure there is a valid
BeagleBoneBlack-eMMC-image-.img file on the uSD card and edit
autorun.sh with your favorite text editor to contain the following:
#!/bin/sh
echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger
dd if=/mnt/BeagleBoneBlack-eMMC-image-X.img of=/dev/mmcblk1 bs=10M
sync
echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger

*NOTE*: Be certain to replace the 'X' above with the proper name of
your image file.

This image was built using Buildroot. The sources are at
https://github.com/jadonk/buildroot with tag save-emmc-0.0.1. Download via
https://github.com/jadonk/buildroot/releases/tag/save-emmc-0.0.1 or clone
the git repo. It is a small fork from
git://git.buildroot.net/buildroottag
e9f6011617528646768e69203e85fe64364b7efd.

To build, 'make beagleboneblack_defconfig; make; ./mkuimage.sh'.  Output
files (am335x-boneblack.dtb, MLO, u-boot.img and uImage) will be in the
output/images subdirectory. The following files were created manually.

uEnv.txt:
bootpart=0:1
bootdir=
fdtaddr=0x81FF
optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
uenvcmd=load mmc 0 ${loadaddr} uImage;run loadfdt;setenv bootargs
console=${console} ${optargs};bootm ${loadaddr} - ${fdtaddr}

autorun.sh:
#!/bin/sh
echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger
dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M
sync
echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger

The kernel is based on
https://github.com/beagleboard/kernel/commit/9fdb452245a58158a4bea787cdc663c17681bcfe,
but I applied the patches, added firmware and uploaded it to
https://github.com/beagleboard/linux/commit/ddd36e546e53d3c493075bbebd6188ee843208f9to
pull down in the Buildroot makefile. The link to the source for the
firmware is in the commit.

I've applied to join the Buildroot mailing list to send these patches
upstream. The power management firmware is not yet loading properly, but
that is something I can look into.

Happy hacking!



--
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/groups/opt_out.

[beagleboard] Extracting eMMC contents using FAT formatted card

[Jason Kridner]

There are lots of ways to extract the contents of the eMMC to save off and
reuse. I'm proposing a method using Buildroot and an initramfs such that
you can simply drop a few files from a .zip onto a normal, FAT-formatted SD
card to perform the extraction. There are several things really handy here,
such as the ability to edit autorun.sh to be whatever script you want to
run on your board at boot. In the archive, I only have the necessary
autorun.sh for *saving* your eMMC content. The flip-side is provided here
in the text such that you need to go through a couple of steps before you
trash your eMMC.

The steps for saving off your eMMC contents to a file:
* Get a 4GB or larger uSD card that is FAT formatted.
* Download https://s3.amazonaws.com/beagle/beagleboneblack-save-emmc.zipand
extract the contents onto your uSD card.
* Eject uSD card from your computer, insert into powered-off BeagleBone
Black and apply power to your board.
* You'll notice USR0 (the LED closest to the S1 button in the corner) will
(after about 20 seconds) start to blink steadily, rather than the
double-pulse "heartbeat" pattern that is typical when your BeagleBone Black
is running the typical Linux kernel configuration.
* It'll run for a bit under 10 minutes and then USR0 will stay ON steady.
That's your cue to remove power, remove the uSD card and put it back into
your computer.
* You should see a file called BeagleBoneBlack-eMMC-image-X.img, where
X is a set of random numbers. Save off this file to use for restoring
your image later.

Because the date won't be set on your board, you might want to adjust the
date on the file to remember when you made it. Delete the file if you want
to make room for a new backup image. For storage on your computer, these
images will typically compress very well, so use your favorite compression
tool.

To restore the file, make sure there is a valid
BeagleBoneBlack-eMMC-image-.img file on the uSD card and edit
autorun.sh with your favorite text editor to contain the following:
#!/bin/sh
echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger
dd if=/mnt/BeagleBoneBlack-eMMC-image-X.img of=/dev/mmcblk1 bs=10M
sync
echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger

*NOTE*: Be certain to replace the 'X' above with the proper name of
your image file.

This image was built using Buildroot. The sources are at
https://github.com/jadonk/buildroot with tag save-emmc-0.0.1. Download via
https://github.com/jadonk/buildroot/releases/tag/save-emmc-0.0.1 or clone
the git repo. It is a small fork from
git://git.buildroot.net/buildroottag
e9f6011617528646768e69203e85fe64364b7efd.

To build, 'make beagleboneblack_defconfig; make; ./mkuimage.sh'.  Output
files (am335x-boneblack.dtb, MLO, u-boot.img and uImage) will be in the
output/images subdirectory. The following files were created manually.

uEnv.txt:
bootpart=0:1
bootdir=
fdtaddr=0x81FF
optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
uenvcmd=load mmc 0 ${loadaddr} uImage;run loadfdt;setenv bootargs
console=${console} ${optargs};bootm ${loadaddr} - ${fdtaddr}

autorun.sh:
#!/bin/sh
echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger
dd if=/dev/mmcblk1 of=/mnt/BeagleBoneBlack-eMMC-image-$RANDOM.img bs=10M
sync
echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger

The kernel is based on
https://github.com/beagleboard/kernel/commit/9fdb452245a58158a4bea787cdc663c17681bcfe,
but I applied the patches, added firmware and uploaded it to
https://github.com/beagleboard/linux/commit/ddd36e546e53d3c493075bbebd6188ee843208f9to
pull down in the Buildroot makefile. The link to the source for the
firmware is in the commit.

I've applied to join the Buildroot mailing list to send these patches
upstream. The power management firmware is not yet loading properly, but
that is something I can look into.

Happy hacking!

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[William Hermans]

It is obvious, at least to me this person did not even try very hard, and I
can not help wondering if this person even really owns a BBB. My
experiences have been the complete reverse what this person has said.

I also can not help but wonder if this person is smart enough to know what
a pin conflict is.


On Thu, Sep 26, 2013 at 9:04 AM,  wrote:

> In similar way to this:
>
> http://bradsmc.blogspot.com/2013/03/beaglebone-tmp102-temperature-sensor.html
> But I need more sensors
>
> W dniu czwartek, 26 września 2013 11:09:30 UTC+2 użytkownik Diogene
> napisał:
>
>> We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
>> Nothing does work as expected!!!
>> Use of Touchscreen is hawfully slow and use of ADC with this screen hangs
>> up the system!
>>
>> How to get a such bad system. It is the same with angstrom distrib!!!
>>
>> We had developp a specific cape and we can put it in garbage!!!
>>
>> Forget this board and chose other one.
>>
>> Regards to all!
>>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Boot fails with microSD: ** Bad partition specification mmc 1:2 **

[Stephen Agate]

> I thought (and hoped) the problem was due to the missing of CR-LF at the 
end of the  uEnv.txt as I read in other posts, but it is not :(

I have read that it must be in Unix format, but you imply yours is in DOS 
format.


-- 
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/groups/opt_out.

Re: [beagleboard] Re: Weather station Beaglebone

[Gerald Coley]

This should work fine. But, be careful. Any other sensors you add that have
integrated pullup resistors, such as this one, could cause you issues as
the pullup value get smaller.

Gerald



On Thu, Sep 26, 2013 at 11:05 AM,  wrote:

> In a way similar to this, but I need more sensors:
>
> http://bradsmc.blogspot.com/2013/03/beaglebone-tmp102-temperature-sensor.html
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[miqelm]

In similar way to this:
http://bradsmc.blogspot.com/2013/03/beaglebone-tmp102-temperature-sensor.html
But I need more sensors

W dniu czwartek, 26 września 2013 11:09:30 UTC+2 użytkownik Diogene napisał:
>
> We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
> Nothing does work as expected!!!
> Use of Touchscreen is hawfully slow and use of ADC with this screen hangs 
> up the system!
>
> How to get a such bad system. It is the same with angstrom distrib!!!
>
> We had developp a specific cape and we can put it in garbage!!!
>
> Forget this board and chose other one.
>
> Regards to all!
>

-- 
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/groups/opt_out.

[beagleboard] Re: Weather station Beaglebone

[miqelm]

In a way similar to this, but I need more sensors:
http://bradsmc.blogspot.com/2013/03/beaglebone-tmp102-temperature-sensor.html

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[Maxim Podbereznyy]

I don't know which Freescale platform you have chosen but based on my
experience with both Wandboard and Sabre Lite - imx6 running from a SD card
is extremely slow. By slow I mean that even such stupid command like "ls"
can complete up to 1 minute. Impressed?
26.09.2013 18:25 пользователь "Diogene"  написал:

> It just a beginning for TI ARM testing.
> We will go to Freescale products.
> Much more efficient.
>
> For your information, Win Ce has same problems ...
> This project is not a company project but a community project.
> In fact, Angstrom distrib is OK. Ubuntu ported on it is Hawfull!!!
>
> Regards.
>
> Le jeudi 26 septembre 2013 15:25:32 UTC+2, Mickae1 a écrit :
>>
>> well, you shouldn't blame the company behind the BBB, neither the
>> community.
>>
>> *It's entirely your fault*, you decided for your product to use open
>> source solution !
>>
>>  Yes it's attractive, you don't need to buy a license for windows CE, but
>> you should have made some research and discovered since we moved to the new
>> kernel, not all of the functions are available.
>>
>> *It's unacceptable for a company to bet that the BBB will work in few
>> months *
>>
>> In my case, i was at the same position as you 6 months ago, I wanted to
>> use the RS485 Cap ... and you know what ? I decided to spend 2 months to
>> find out how to modify the drivers. And now It's working ! ( Thx  again
>> everyone for your help again)
>>
>>
>> So, you should instead blame yourself or spend some time to help us, and
>> find out what's wrong with the LCD.. .
>>
>> IF you don't have TIME, give some money to this community and I'm sure
>> that a developer will put this bug in priority.
>>
>>
>> Michael Musset,
>>
>>
>> On Thu, Sep 26, 2013 at 2:59 PM, garyamort  wrote:
>>
>>>
>>>
>>> On Thursday, September 26, 2013 5:09:30 AM UTC-4, Diogene wrote:

 We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
 Nothing does work as expected!!!
 Use of Touchscreen is hawfully slow and use of ADC with this screen
 hangs up the system!

 How to get a such bad system. It is the same with angstrom distrib!!!

 We had developp a specific cape and we can put it in garbage!!!


>>> I'll happily pay for shipping if you want to send me the cape and board.
>>> :-)
>>>
>>>
>>>
>>> --
>>> 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/**groups/opt_out
>>> .
>>>
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[Mark Lazarewicz]

For myself if you can't build the kernel and get support why bother.  Never 
wanted to spend the time learn OE . Roberts instructions for Ubuntu from 
scratch  work and wifi works so thats what I plan on using.  Anybody can copy 
binaries to a card then bitch when its changed.  Isnt that why we use linux as 
we gave the source hence the power to fix what we don't like!

Sent from Yahoo! Mail on Android

-- 
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/groups/opt_out.

Re: [beagleboard] Re: BeagleBone Black - No HDMI Output

[Gerald Coley]

The display driver takes over once it is launched. It does not use the
uENV.txt parameters. It uses the EDID.

Gerald



On Thu, Sep 26, 2013 at 10:16 AM,  wrote:

> I met similar issue as well. My monitor is ASUS LS221H which can correctly
> display outputted from my mobile phone Xperia Neo V via HDMI. From here, we
> can confirm the monitor and the cable both function well. After powering
> up, sometimes I could see the logo from BeagleBone Black. Then, what I
> could see is just no signal reported from the monitor.
>
> I referenced the page,
> http://circuitco.com/support/index.php?title=BeagleBoneBlack_HDMI, and
> tried something described in the page via terminal https://192.168.7.2/
> Followings are some information of my board.
>
> *root@beaglebone:/sys/class/drm/card0/card0-HDMI-A-1# xrandr --verbose
>
>  *
> Screen 0: minimum 320 x 200, current 1280 x 720, maximum 2048 x 2048
>
>
> HDMI-0 connected 1280x720+0+0 (0x42) normal (normal left inverted right x
> axis y axis) 474mm x 296mm
>
>Identifier: 0x40
>
>
>Timestamp:  1523547016
>Subpixel:   unknown
>Gamma:  1.0:1.0:1.0
>Brightness: 1.0
>Clones:
>CRTC:   0
>CRTCs:  0
>Transform:  1.00 0.00 0.00
>0.00 1.00 0.00
>0.00 0.00 1.00
>   filter:
>EDID:
>00000469f12201010101
>20130103802f1e782e78f5a655489b26
>125054bfef80b30081809500950f9040
>714f0101010121399030621a274068b0
>3600da28111c00ff0039384c
>4d56443030343433360a00fd0038
>4b1f5111000a20202020202000fc
>00415355532d4c533232314801ff
>02031e764b909f859484930312010716
>23090707830165030c00023a
>801871382d40582c9600da281118
>023a80d072382d40102c4580da281100
>001e011d8018711c1620582c2500da28
>119e011d80d0721c1620102c2580
>da28119e011d00bc52d01e20b828
>5540da28111e00dd
>   1280x720 (0x41)   74.2MHz +HSync +VSync
> h: width  1280 start 1720 end 1760 total 1980 skew0 clock
> 37.5KHz
> v: height  720 start  725 end  730 total  750   clock
> 50.0Hz
>   1280x720 (0x42)   74.2MHz +HSync +VSync *current
> h: width  1280 start 1390 end 1430 total 1650 skew0 clock
> 45.0KHz
> v: height  720 start  725 end  730 total  750   clock
> 60.0Hz
>   720x576 (0x43)   27.0MHz -HSync -VSync
> h: width   720 start  732 end  796 total  864 skew0 clock
> 31.2KHz
> v: height  576 start  581 end  586 total  625   clock
> 50.0Hz
>   720x480 (0x44)   27.0MHz -HSync -VSync
> h: width   720 start  736 end  798 total  858 skew0 clock
> 31.5KHz
> v: height  480 start  489 end  495 total  525   clock
> 59.9Hz
>   640x480 (0x45)   25.2MHz -HSync -VSync
> h: width   640 start  656 end  752 total  800 skew0 clock
> 31.5KHz
> v: height  480 start  490 end  492 total  525   clock
> 59.9Hz
>
> *root@beaglebone:/sys/class/drm/card0/card0-HDMI-A-1# parse-edid edid*
> parse-edid: parse-edid version 2.0.0
> parse-edid: EDID checksum passed.
>
>
>
># EDID version 1 revision 3
> Section "Monitor"
># Block type: 2:0 3:ff
># Block type: 2:0 3:fd
># Block type: 2:0 3:fc
>Identifier "ASUS-LS221Hÿÿ"
>VendorName "ACI"
>ModelName "ASUS-LS221Hÿÿ"
># Block type: 2:0 3:ff
># Block type: 2:0 3:fd
>HorizSync 31-81
>VertRefresh 56-75
># Max dot clock (video bandwidth) 170 MHz
># Block type: 2:0 3:fc
># DPMS capabilities: Active off:yes  Suspend:no  Standby:no
>
>
>
>Mode"1680x1050" # vfreq 59.954Hz, hfreq 65.290kHz
>DotClock146.25
>HTimings1680 1784 1960 2240
>VTimings1050 1053 1059 1089
>Flags   "+HSync" "-VSync"
>EndMode
># Block type: 2:0 3:ff
># Block type: 2:0 3:fd
># Block type: 2:0 3:fc
> EndSection
>
> *ID.txt*
> Cloud9 GNOME Image 2013.06.20
>
> *root@beaglebone:~# cat /proc/cmdline *
> console=ttyO0,115200n8 video=HDMI-A-1::640x480@60 root=/dev/mmcblk0p2 ro
> rootfstype=ext4 rootwait
>
> Finally, the three steps below work like a charm
>
> *root@beaglebone:~# export XAUTHORITY=`ls
> /var/run/gdm/auth-for-root-*/database` *
> *root@beaglebone:~# export DISPLAY=:0.0 *
> *root@beaglebone:~# xrandr --output HDMI-0 --mode 1280x720 --rate 60*
>
> *root@beaglebone:/sys/class/drm/card0/card0-HDMI-A-1# fbset*
>
>
>
> mode "1280x720-0"
># D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
>geometry 1280 720 1280 720 16
>timin

[beagleboard] Re: BeagleBone Black - No HDMI Output

[honercek]

I met similar issue as well. My monitor is ASUS LS221H which can correctly 
display outputted from my mobile phone Xperia Neo V via HDMI. From here, we 
can confirm the monitor and the cable both function well. After powering 
up, sometimes I could see the logo from BeagleBone Black. Then, what I 
could see is just no signal reported from the monitor.

I referenced the page, 
http://circuitco.com/support/index.php?title=BeagleBoneBlack_HDMI, and 
tried something described in the page via terminal https://192.168.7.2/
Followings are some information of my board.

*root@beaglebone:/sys/class/drm/card0/card0-HDMI-A-1# xrandr --verbose 

   *
Screen 0: minimum 320 x 200, current 1280 x 720, maximum 2048 x 2048   

  
HDMI-0 connected 1280x720+0+0 (0x42) normal (normal left inverted right x 
axis y axis) 474mm x 296mm 

   Identifier: 0x40 

 
   Timestamp:  1523547016
   Subpixel:   unknown
   Gamma:  1.0:1.0:1.0
   Brightness: 1.0
   Clones:
   CRTC:   0
   CRTCs:  0
   Transform:  1.00 0.00 0.00
   0.00 1.00 0.00
   0.00 0.00 1.00
  filter:
   EDID:
   00000469f12201010101
   20130103802f1e782e78f5a655489b26
   125054bfef80b30081809500950f9040
   714f0101010121399030621a274068b0
   3600da28111c00ff0039384c
   4d56443030343433360a00fd0038
   4b1f5111000a20202020202000fc
   00415355532d4c533232314801ff
   02031e764b909f859484930312010716
   23090707830165030c00023a
   801871382d40582c9600da281118
   023a80d072382d40102c4580da281100
   001e011d8018711c1620582c2500da28
   119e011d80d0721c1620102c2580
   da28119e011d00bc52d01e20b828
   5540da28111e00dd
  1280x720 (0x41)   74.2MHz +HSync +VSync
h: width  1280 start 1720 end 1760 total 1980 skew0 clock   
37.5KHz
v: height  720 start  725 end  730 total  750   clock   
50.0Hz
  1280x720 (0x42)   74.2MHz +HSync +VSync *current
h: width  1280 start 1390 end 1430 total 1650 skew0 clock   
45.0KHz
v: height  720 start  725 end  730 total  750   clock   
60.0Hz
  720x576 (0x43)   27.0MHz -HSync -VSync
h: width   720 start  732 end  796 total  864 skew0 clock   
31.2KHz
v: height  576 start  581 end  586 total  625   clock   
50.0Hz
  720x480 (0x44)   27.0MHz -HSync -VSync
h: width   720 start  736 end  798 total  858 skew0 clock   
31.5KHz
v: height  480 start  489 end  495 total  525   clock   
59.9Hz
  640x480 (0x45)   25.2MHz -HSync -VSync
h: width   640 start  656 end  752 total  800 skew0 clock   
31.5KHz
v: height  480 start  490 end  492 total  525   clock   
59.9Hz

*root@beaglebone:/sys/class/drm/card0/card0-HDMI-A-1# parse-edid edid*
parse-edid: parse-edid version 2.0.0
parse-edid: EDID checksum passed.


 
   # EDID version 1 revision 3
Section "Monitor"
   # Block type: 2:0 3:ff
   # Block type: 2:0 3:fd
   # Block type: 2:0 3:fc
   Identifier "ASUS-LS221Hÿÿ"
   VendorName "ACI"
   ModelName "ASUS-LS221Hÿÿ"
   # Block type: 2:0 3:ff
   # Block type: 2:0 3:fd
   HorizSync 31-81
   VertRefresh 56-75
   # Max dot clock (video bandwidth) 170 MHz
   # Block type: 2:0 3:fc
   # DPMS capabilities: Active off:yes  Suspend:no  Standby:no


 
   Mode"1680x1050" # vfreq 59.954Hz, hfreq 65.290kHz
   DotClock146.25
   HTimings1680 1784 1960 2240
   VTimings1050 1053 1059 1089
   Flags   "+HSync" "-VSync"
   EndMode
   # Block type: 2:0 3:ff
   # Block type: 2:0 3:fd
   # Block type: 2:0 3:fc
EndSection

*ID.txt*
Cloud9 GNOME Image 2013.06.20

*root@beaglebone:~# cat /proc/cmdline *
console=ttyO0,115200n8 video=HDMI-A-1::640x480@60 root=/dev/mmcb

[beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[Richard Cook]

 Ah, I hear a troll!

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[Robert Nelson]

On Thu, Sep 26, 2013 at 9:12 AM, Diogene  wrote:
> It just a beginning for TI ARM testing.
> We will go to Freescale products.
> Much more efficient.
>
> For your information, Win Ce has same problems ...
> This project is not a company project but a community project.
> In fact, Angstrom distrib is OK. Ubuntu ported on it is Hawfull!!!

Humm, strange, as the defacto ubuntu maintainer, for some reason I do
not see any email/bug messages from you regarding this issue.. SO
whatever, if you don't try, it's not my problem...

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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[Gerald Coley]

I would try to explain how wrong your are. But I doubt you would understand
any of it. I would not all all convince you not to go to Freescale and use
their community based forum for support.


Gerald



On Thu, Sep 26, 2013 at 9:12 AM, Diogene  wrote:

> It just a beginning for TI ARM testing.
> We will go to Freescale products.
> Much more efficient.
>
> For your information, Win Ce has same problems ...
> This project is not a company project but a community project.
> In fact, Angstrom distrib is OK. Ubuntu ported on it is Hawfull!!!
>
> Regards.
>
> Le jeudi 26 septembre 2013 15:25:32 UTC+2, Mickae1 a écrit :
>>
>> well, you shouldn't blame the company behind the BBB, neither the
>> community.
>>
>> *It's entirely your fault*, you decided for your product to use open
>> source solution !
>>
>>  Yes it's attractive, you don't need to buy a license for windows CE, but
>> you should have made some research and discovered since we moved to the new
>> kernel, not all of the functions are available.
>>
>> *It's unacceptable for a company to bet that the BBB will work in few
>> months *
>>
>> In my case, i was at the same position as you 6 months ago, I wanted to
>> use the RS485 Cap ... and you know what ? I decided to spend 2 months to
>> find out how to modify the drivers. And now It's working ! ( Thx  again
>> everyone for your help again)
>>
>>
>> So, you should instead blame yourself or spend some time to help us, and
>> find out what's wrong with the LCD.. .
>>
>> IF you don't have TIME, give some money to this community and I'm sure
>> that a developer will put this bug in priority.
>>
>>
>> Michael Musset,
>>
>>
>> On Thu, Sep 26, 2013 at 2:59 PM, garyamort  wrote:
>>
>>>
>>>
>>> On Thursday, September 26, 2013 5:09:30 AM UTC-4, Diogene wrote:

 We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
 Nothing does work as expected!!!
 Use of Touchscreen is hawfully slow and use of ADC with this screen
 hangs up the system!

 How to get a such bad system. It is the same with angstrom distrib!!!

 We had developp a specific cape and we can put it in garbage!!!


>>> I'll happily pay for shipping if you want to send me the cape and board.
>>> :-)
>>>
>>>
>>>
>>> --
>>> 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/**groups/opt_out
>>> .
>>>
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] drm_ioctl noisiness in dmesg

[Chris Ross]

That's fine.  I was just curious if there was some other debug level, that 
might note connect/disconnect of the port, or other useful things that were 
less constant, also might exist.  I've removed it totally for now.

On Wednesday, September 25, 2013 3:57:03 PM UTC-4, Gerald wrote:
>
> It was there because we were having HDMI issues an the information sent 
> out was found to be useful in debugging the HDMI issue.
>
> If you remove it totally, then that should stop the messages from being 
> sent.
>
> Gerald
>
>
>
>
> On Wed, Sep 25, 2013 at 2:27 PM, Chris Ross 
> > wrote:
>
>> Every second or so, my BBB (running 2013.09.04) emits:
>>
>> [  626.556210] [drm:drm_ioctl], pid=238, cmd=0xc01864b1, nr=0xb1, dev 
>> 0xe200, auth=1
>> [  626.556323] [drm:drm_ioctl], ret = -38
>>
>> into dmesg.  I saw a comment in another post 
>> here
>>  suggesting 
>> removing the *drm.debug=7* in the *uEnv.txt* on the FAT partition.  But 
>> I assume that was originally put there for some reason, and has remained, 
>> so I wanted to ask
>>
>>
>>1. Why was it originally added?
>>2. Is there another value (other than 7) that might be useful, and 
>>not emit these above messages? 
>>
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[Diogene]

It just a beginning for TI ARM testing.
We will go to Freescale products.
Much more efficient.

For your information, Win Ce has same problems ...
This project is not a company project but a community project.
In fact, Angstrom distrib is OK. Ubuntu ported on it is Hawfull!!!

Regards.

Le jeudi 26 septembre 2013 15:25:32 UTC+2, Mickae1 a écrit :
>
> well, you shouldn't blame the company behind the BBB, neither the 
> community.
>
> *It's entirely your fault*, you decided for your product to use open 
> source solution !
>
>  Yes it's attractive, you don't need to buy a license for windows CE, but 
> you should have made some research and discovered since we moved to the new 
> kernel, not all of the functions are available.
>
> *It's unacceptable for a company to bet that the BBB will work in few 
> months *
>
> In my case, i was at the same position as you 6 months ago, I wanted to 
> use the RS485 Cap ... and you know what ? I decided to spend 2 months to 
> find out how to modify the drivers. And now It's working ! ( Thx  again 
> everyone for your help again)
>
>
> So, you should instead blame yourself or spend some time to help us, and 
> find out what's wrong with the LCD.. .
>
> IF you don't have TIME, give some money to this community and I'm sure 
> that a developer will put this bug in priority.
>
>
> Michael Musset,
>
>
> On Thu, Sep 26, 2013 at 2:59 PM, garyamort 
> > wrote:
>
>>
>>
>> On Thursday, September 26, 2013 5:09:30 AM UTC-4, Diogene wrote:
>>>
>>> We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
>>> Nothing does work as expected!!!
>>> Use of Touchscreen is hawfully slow and use of ADC with this screen 
>>> hangs up the system!
>>>
>>> How to get a such bad system. It is the same with angstrom distrib!!!
>>>
>>> We had developp a specific cape and we can put it in garbage!!!
>>>
>>>
>> I'll happily pay for shipping if you want to send me the cape and board. 
>> :-)
>>
>>  
>>
>> -- 
>> 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/groups/opt_out.
>>
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] BBB Arch Linux Device Tree

[Miguel Aveiro]

I think you can try this:
http://protofusion.org/wordpress/2013/06/beaglebone-black-and-dtc/

Regards,
Miguel Aveiro


2013/9/26 Nick Glynn 

> You need to use the patched version of DTC provided by TI, the one in the
> kernel hasn't got device tree fragment support which is the error you're
> getting.
>
> Regards,
> Nick
>
>
> On 26 September 2013 10:37, Seçkin Alan  wrote:
>
>> Hi everyone,
>>
>> I install Arch Linux on BBB e-MMC. I need serial port and read this(
>> http://hipstercircuits.**com/enable-serialuarttty-on-**beaglebone-black/)
>> article.
>>
>> I just copy & paste "nano enable-uart5.dts", after paste enable uart5
>> code in nano.
>>
>> Save & exit enable-uart5.dts file.
>>
>> I try compile this file with dtc,
>> dtc -O dtb -o enable-uart5-00A0.dtbo -b 0 -@ enable-uart5.dts
>> Compiler return -h message, -@ argument isn't accept dtc.
>>
>> I remove -@ argument and try again, this time compiler return error
>> message
>>
>> [root@alarm ~]# dtc -O dtb -o enable-uart5-00A0.dtbo -b 0
>> enable-uart5.dts
>> Error: enable-uart5.dts:1.1-2 syntax error
>> FATAL ERROR: Unable to parse input tree
>>
>>
>> What can I do?
>> Thank you.
>> Best 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/groups/opt_out.
>>
>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] Re: Anyone interested in writing or helping with a media playback app?

[garyamort]

On Thursday, September 26, 2013 2:24:11 AM UTC-4, Mike Langensiepen wrote:
>
> Apologies in advance if this is in the wrong area
>
> Is there an app or does anyone fancy giving me a price for writing an app 
> do to the following:
> Play an ambient audio/video track (whatever format needed)
> On receiving a trigger input switch to playing another specified 
> audio/video track
> When 2nd track is finished go back to playing the ambient track.
>
> Tracks would need to be full HD
>
>
I know that VLC Media player has a web interface for adding items to the 
playlist and playing videos remotely.  It can also be configured to loop 
the playlist.

So with that, you could invoke VLC from the command line and give it a file 
to play automatically - then use the web interface to "trigger" switching 
to another file immediately while leaving the initial file in the playlist 
to be looped back to once done.

I'm fairly sure ALL the major video player apps for linux have a web 
interface.

Of course this moves the time/cost from "writing an app" to "configuring 
the system" as you will need to setup your linux distribution, have it 
start the x-windows environment upon bootup[but not a desktop, just the 
windowing system], and then start VL - that is assuming you don't want a 
desktop, you just want a pure video player.

Then you can design your trigger app. 

Not a non-trivial amount of time, mind 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/groups/opt_out.

[beagleboard] Re: Help with UART on BBB using Python

[Patrick Finucane]

okay to answer my own question after a little more looking around.
 
Two good places to read for more information are shown below.  I found them 
in another thread (that I somehow missed before posting)
 
*
http://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/exporting-and-unexporting-an-overlay
*
*http://hipstercircuits.com/enable-serialuarttty-on-beaglebone-black/*
I still don't know why the Adafruit library is not doing the overlay 
correctly.

-- 
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/groups/opt_out.

Re: [beagleboard] Anyone interested in writing or helping with a media playback app?

[Gerald Coley]

Just curious. What board would this application be running one?

Gerald


On Thu, Sep 26, 2013 at 1:24 AM, Mike Langensiepen <
m...@ipprofessional.com.au> wrote:

> Apologies in advance if this is in the wrong area
>
> Is there an app or does anyone fancy giving me a price for writing an app
> do to the following:
> Play an ambient audio/video track (whatever format needed)
> On receiving a trigger input switch to playing another specified
> audio/video track
> When 2nd track is finished go back to playing the ambient track.
>
> Tracks would need to be full HD
>
> Thanks
>
> Mike
>
>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[garyamort]

On Tuesday, September 24, 2013 5:33:36 AM UTC-4, Anguel wrote:
>
>
>  
>
>> The concept here is the people that buy them, know how Linux works and 
>> can get things going themselves and make what ever tweaks are 
>> required. Supporting all the different kernel versions and distributions, 
>> that is no feasible.
>>
>
> Probably this is the nice business concept used by TI, CircuitCo, etc. 
> Sell chips and boards, make money, but let the open source community write 
> the software and support everything for free. Just make a product, label it 
> to be "for developers" and sell it without any support.
>


There is a difference between "any support" and "not supported".

"Not supported" means that it has been tested under a very specific 
software configuration and works for that configuration.  If you check the 
Linux Source code, you will find a LOT of code written by Texas Instruments 
- so they are certainly providing SOME support.

Interestingly, if you check the LCD drivers you will find that for small 
LCD screens, most of those drivers come from Nokia[or at the very least are 
based off Nokia drivers].

So no, it is not "the community" that is expected to support things "for 
free".  How it works is that Nokia, a cell phone manufacturer, decides to 
use a Texas Instruments processor in a cell phone.  They decide to use a 
specific model of LCD screen.   They pay developers to create an LCD driver 
for a Texas Instruments supported linux kernel.  If they find a bug in the 
TI LCD interface, they contact TI and TI works with them to fix it.  Once 
they have the TI supported kernel working, they then try to use the same 
driver in the latest version of Android.  If it doesn't work, their 
developers have to figure out what changes were made that broke something, 
and then they fix it.  Considering that their going to order 100,000+ TI 
processors, they probably pay TI for support so their developers and TI's 
developers work on the driver.

When that is all done, this driver which was written by Nokia with Texas 
Instruments help is then given to "the community" for free - under the 
terms of the standard GPL license, including:
"THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY 
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, *YOU ASSUME THE COST OF 
ALL NECESSARY SERVICING, REPAIR OR CORRECTION*."

Please note that last line as it is the one you seem to object to, and yet 
it is the very reason companies are willing to give away applications they 
paid developers to write to the community - as they are not required to 
support them and you agreed to assume the cost.

Android does NOT use the X11 window system, so the driver written by Nokia 
for their phone may not work properly for a Ubuntu desktop.  As the reason 
Nokia paid developers to write it was for an android phone, I can't see any 
reason to expect them to make sure it works for Ubuntu "for free".

Your receiving a huge amount of support from TI and CitcuitCo - however 
your "tone of voice" is demanding that they FIX the problem.  They are not 
required to fix the problem, and you agreed to assume the cost of all 
correction.  In all fairness, they should be billing you for the time spent 
responding to you as you agreed to "assume the cost".  

You have identified a problem.  Programmers from "the community", "Texas 
Instruments", and "CircuitCo" have acknowledged the problem, done a good 
bit of deductive reasoning to determine where the problem lies and the 
general idea of how to fix it and given this information to you for free.

There are four solutions specifically for you:

A) Use the linux versions that are known to work for the device, move on 
with your life.

B) Wait for someone to be willing to fix it "for free"

C) Fix it "yourself" - note this does not mean you personally, this means 
either you fix it or hire someone to fix it.

D) Give up in frustration and use a different product.  If you wish, loudly 
proclaim that "everything just works out of the box".  A few weeks down the 
road you will discover a different problem with the interaction of a 
completely different set of drivers that the vendor of that product doesn't 
use and does not support.  When you do, if you choose to loudly proclaim 
your "solution" you can choose to acknowledge that your solution that "just 
worked" actually does not work so others who may be misled by your comments 
to also switch don't suffer the same issue.  Or you can keep quiet about it 
to avoid looking foolish and thus cause economic harm to others.


As a summary "not supported" means that the company is not

Re: [beagleboard] Apple full numeric [Aluminium] keyboard and internal hub does not work

[Gerald Coley]

Not sure it will fix your issue, but the image you are using is very old. I
suggest that you try a more up to date image on your board.

http://circuitco.com/support/BeagleBoneBlack


Gerald



On Thu, Sep 26, 2013 at 12:56 AM,  wrote:

> Hi Guys
>
> Someone asked a similar question before, but no one had an answer then.
> I was going to give up and buy another keyboard but when I googled a bit
> more, I saw that a lot of people are able to use it with their beaglebone
> black.
>
> I will explain the conditions and problem in details.
>
> I have a beaglebone black powered up via a USB charger (NOT via the 5V DC
> adapter)
> I have it connected to a display via a microHDMI cable.
> I am running Angstrom. Updated to 4.09.2013 image. (emmc boot)
>
> When I plugged in a normal wired optical mouse, it powered up and I was
> able to use it.
> I then used an Apple keyboard as described in the title and plugged the
> mouse to its internal hub on the sides. Nothing worked, both did not show
> any signs of being powered up.
> I of course rebooted and checked *lsusb *output. I could see the Apple
> device listed there.
>
> Is this a driver issue or a power supply problem?
> Kinda new, so help me out please.
>
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes

[Gerald Coley]

I would not buy it either. Contact the president at:

cl...@circuitco.com

Gerald


On Thu, Sep 26, 2013 at 5:53 AM, Anguel  wrote:

> Gerald,
>
> CircuitCo support did not even answer my e-mail regarding the
> non-functional touchscreen. 4D Systems at least admitted that this is a
> well known problem. Once again: Why don't they clearly state on their LCD
> product pages that the touchscreen does not work in latest Angstrom? I
> really hope that customers see my thread before buying a LCD with
> touchscreen.
>
> Anguel
>
>
>
> On Tuesday, September 24, 2013 3:15:23 PM UTC+2, Gerald wrote:
>
>> That is what I was told by Circuitco.
>>
>> Gerald
>>
>>
>> On Tue, Sep 24, 2013 at 12:55 AM, Anguel  wrote:
>>
>>> How do you know this is a X11 bug? I see the same bug with TS_LIB. It is
>>> somewhere deep in the driver.
>>>
>>>
>>> On Monday, September 23, 2013 9:04:12 PM UTC+2, Gerald wrote:
>>> > As was previously indicated to you, this is an issue with X11, a bug.
>>> If you will fix the X11 it should work fine. Or just use the latest
>>> Angstrom build.
>>> >
>>> >
>>> > This is you decision as to how you handle it.
>>> >
>>> >
>>> >
>>> > Gerald
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, Sep 23, 2013 at 11:00 AM, Anguel  wrote:
>>> >
>>> >
>>> > Hi Terry,
>>> >
>>> > Nice to know that I am not the only one who cares about the
>>> touchscreen. Neither CircuitCo nor 4D Systems seem to really care about the
>>> problem. They sell the displays but don't reply to my e-mails anymore. I
>>> also reported the problem on Beaglebone IRC but did not receive any help
>>> there. I even tried tweaking a bit in the kernel but without success. I
>>> just don't have the experience to dig deeper in the ADC drivers and chase
>>> for the bug.
>>> >
>>> >
>>> > The latest patches were actually submitted by Zubair Lutfullah, he
>>> seems to adapt them (from the TI driver developers who write them for the
>>> older kernel afaik). Zubair told me that he already knew about the jitter
>>> problem and gave me the following reply: "The touchscreen driver that was
>>> patched in the linux kernel
>>> > was different compared to the old patches in the beaglebone
>>> > tree. And we try to keep the beaglebone tree close to the
>>> > mainline. The old 3.8 patches were ok. The
>>> > mainlined ones introduced this problem.. A fix would
>>> require a comparison of the two drivers to
>>> > figure out what went wrong and upload a patch to the
>>> > mainline.. It would require time.."
>>> >
>>> > Unfortunately, Zubair is very busy right now. He also mailed his reply
>>> to Koen Kooi, one of the main Angstrom developers (also works at CircuitCo
>>> according to his Google+ profile). I am afraid that Koen is also very busy
>>> and won't have the time to look into the issue. So we can just hope that
>>> someone with more experience can fix the issue in the near future.
>>> >
>>> >
>>> > Regards,
>>> > Anguel
>>> >
>>> >
>>> >
>>> >
>>> > On Monday, September 23, 2013 7:08:36 AM UTC+2, terrys...@gmail.comwrote:
>>> >
>>> > Hi Anguel
>>> >
>>> >
>>> > I too have the same problem. I have a LCD4 and a LCD7 and both do the
>>> same thing.
>>> > I suspect since the 4D Systems displays use the same drivers the
>>> 4DCAPE-43T does the same thing, so it doesn't seem to be hardware related
>>> at all since they use different brand touch screens.
>>> >
>>> >
>>> >
>>> > Have you had any reply out of CircuitCo?
>>> > Does CircuitCo actually write the drivers or is it someone else?
>>> > Can anyone help and point us to someone who wrote the drivers that we
>>> can discuss this with?
>>> >
>>> >
>>> >
>>> > I know a number of other people who have these displays and experience
>>> the exact same thing, so it is not just isolated to us 2 people.
>>> >
>>> >
>>> > Please can someone point us in the right direction?
>>> >
>>> >
>>> >
>>> > Thanks
>>> > Terry
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > 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/**groups/opt_out
>>> .
>>>
>>> --
>>> 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/**groups/opt_out
>>> .
>>>
>>
>>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you ar

Re: [beagleboard] Boot fails with microSD: ** Bad partition specification mmc 1:2 **

[Gerald Coley]

That is what it should say.

Gerald



On Thu, Sep 26, 2013 at 4:18 AM,  wrote:

> Sorry,
>
> After flashing the BBB the ID.txt contains:
>
> *CLoud9 GNOME Image 2013.09.04*
> and not
>
> *CLoud9 GNOME Image 2013.06.20*
> as I wrongly wrote in my previous post.
>
>
> BR
> Marco
>
>
> On Thursday, September 26, 2013 11:13:12 AM UTC+2, basi...@gmail.comwrote:
>>
>> Hi Gerald,
>>
>> thanks for your reply!
>> I followed your suggestion using the latest firmware.
>> After flashing the BBB I see now that the ID.txt files shows:
>>
>> *CLoud9 GNOME Image 2013.06.20*
>> root@beaglebone:~# more /etc/version
>>
>> Angstrom v2012.12
>> root@beaglebone:~#
>>
>> root@beaglebone:~# uname -a
>> Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l
>> GNU/Linux
>>
>> I repartitioned my microSD as before (UENV and SD) and created the
>> uEnv.txt in primary FAT32 partition (UENV ) as above.
>>
>> If I insert the microSD into the BBB, the microSD is detected and the two
>> partitions are automatically mounted under /media
>>
>> root@beaglebone:/# cd /media/
>> root@beaglebone:/media# ls
>> BEAGLEBONE  SD  UENV  card  cf  hdd  mmc1  net  ram  realroot  union
>> root@beaglebone:/media# more UENV/uEnv.txt
>> mmcdev=1
>> bootpart=1:2
>> mmcroot=/dev/mmcblk1p2 ro
>> optargs=quiet
>> root@beaglebone:/media#
>>
>> The problem is when I reboot the BBB with the microSD already in.
>> I still receive the same error message as before (I attach the complete
>> console output *BBBlog.txt*):
>>
>> SD/MMC found on device 0
>> reading uEnv.txt
>> 66 bytes read in 3 ms (21.5 KiB/s)
>> Loaded environment from uEnv.txt
>> Importing environment from mmc ...
>> gpio: pin 55 (gpio 55) value is 1
>> mmc_send_cmd : timeout: No status update
>>  **Bad partition specification mmc 1:2
>> U-Boot#
>> I thought (and hoped) the problem was due to the missing of CR-LF at the
>> end of the  uEnv.txt as I read in other posts, but it is not :(
>>
>> What I really don't get is why and how I did manage few days ago to boot
>> the BBB with the microSD in, just after following the instructions in
>> http://circuitco.com/support/**index.php?title=MicroSD_As_**Extra_Storage
>>
>> But I can't know achieve the same result.
>> (I had to re-flash the BBB from scratch because I did later on other
>> mistakes ... I'm learning :) )
>>
>> Clearly this **Bad partition specification mmc *1:2* error message is
>> related to the following settings in the uEnv.txt
>> mmcdev=1
>> bootpart=*1:2*
>>
>> But why now suddenly doesn't it accept 1:2 while it did it few days ago?
>>
>> Thanks in advance for any help/saggestion.
>>
>> Marco
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

Re: [beagleboard] BBB Arch Linux Device Tree

[Nick Glynn]

You need to use the patched version of DTC provided by TI, the one in the
kernel hasn't got device tree fragment support which is the error you're
getting.

Regards,
Nick


On 26 September 2013 10:37, Seçkin Alan  wrote:

> Hi everyone,
>
> I install Arch Linux on BBB e-MMC. I need serial port and read this(
> http://hipstercircuits.**com/enable-serialuarttty-on-**beaglebone-black/)
> article.
>
> I just copy & paste "nano enable-uart5.dts", after paste enable uart5 code
> in nano.
>
> Save & exit enable-uart5.dts file.
>
> I try compile this file with dtc,
> dtc -O dtb -o enable-uart5-00A0.dtbo -b 0 -@ enable-uart5.dts
> Compiler return -h message, -@ argument isn't accept dtc.
>
> I remove -@ argument and try again, this time compiler return error message
>
> [root@alarm ~]# dtc -O dtb -o enable-uart5-00A0.dtbo -b 0 enable-uart5.dts
> Error: enable-uart5.dts:1.1-2 syntax error
> FATAL ERROR: Unable to parse input tree
>
>
> What can I do?
> Thank you.
> Best 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] permission denied to pins unless root

[sam . outerbabylon]

I'm trying to run a simple led blink example like here:

http://www.phys-x.org/rbots/index.php?option=com_content&view=article&id=104:lesson-1-beaglebone-black-blink-led&catid=46:beaglebone-black&Itemid=81

I'm running a Ubuntu image on my beaglebone black with node 0.8.x.  I get a 
permission problem that looks like some form of failure to have access to 
the pins.  I added my user to the dialout group and that didn't work.  Then 
I added my user to every group I could find and that didn't work either.  
The only way I can get the code to run and do the blinking is if I run it 
as root.  My question is, how do I give my user access to whatever is 
needed to reach the pins running as non-root.  The permission problem looks 
like the following:

fs.js:338
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), 
mode);
 ^
Error: EACCES, permission denied 
'/sys/class/leds/beaglebone:green:usr0/trigger'
at Object.fs.openSync (fs.js:338:18)
at Object.fs.writeFileSync (fs.js:756:15)
at Object.f.pinMode 
(/home/ubuntu/projects/hello_express/node_modules/bonescript/index.js:132:20)
at Object. 
(/home/ubuntu/projects/hello_express/hello_express.js:31:3)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.runMain (module.js:492:10)

Thanks for any help in advance.  I'm pretty excited to get this running. 

- Samuel

-- 
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/groups/opt_out.

[beagleboard] Anyone interested in writing or helping with a media playback app?

[Mike Langensiepen]

Apologies in advance if this is in the wrong area

Is there an app or does anyone fancy giving me a price for writing an app 
do to the following:
Play an ambient audio/video track (whatever format needed)
On receiving a trigger input switch to playing another specified 
audio/video track
When 2nd track is finished go back to playing the ambient track.

Tracks would need to be full HD

Thanks

Mike

-- 
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/groups/opt_out.

[beagleboard] BBB Arch Linux Device Tree

[Seçkin Alan]

Hi everyone,

I install Arch Linux on BBB e-MMC. I need serial port and read this(
http://hipstercircuits.com/enable-serialuarttty-on-beaglebone-black/) 
article.

I just copy & paste "nano enable-uart5.dts", after paste enable uart5 code 
in nano.

Save & exit enable-uart5.dts file. 

I try compile this file with dtc,
dtc -O dtb -o enable-uart5-00A0.dtbo -b 0 -@ enable-uart5.dts
Compiler return -h message, -@ argument isn't accept dtc.

I remove -@ argument and try again, this time compiler return error message

[root@alarm ~]# dtc -O dtb -o enable-uart5-00A0.dtbo -b 0 enable-uart5.dts
Error: enable-uart5.dts:1.1-2 syntax error
FATAL ERROR: Unable to parse input tree


What can I do?
Thank you.
Best 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/groups/opt_out.

[beagleboard] BBB Arch Linux Device Tree

[Seçkin Alan]

Hi everyone,

I install Arch Linux on BBB e-MMC. I need serial port and read this(
http://hipstercircuits.com/enable-serialuarttty-on-beaglebone-black/) 
article.

I just copy & paste "nano enable-uart5.dts", after paste enable uart5 code 
in nano.

Save & exit enable-uart5.dts file. 

I try compile this file with dtc,
dtc -O dtb -o enable-uart5-00A0.dtbo -b 0 -@ enable-uart5.dts
Compiler return -h message, -@ argument isn't accept dtc.

I remove -@ argument and try again, this time compiler return error message

[root@alarm ~]# dtc -O dtb -o enable-uart5-00A0.dtbo -b 0 enable-uart5.dts
Error: enable-uart5.dts:1.1-2 syntax error
FATAL ERROR: Unable to parse input tree


What can I do?
Thank you.
Best 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/groups/opt_out.

[beagleboard] permission denied to pins when non-root

[sam . outerbabylon]

I'm trying to do this:

http://www.phys-x.org/rbots/index.php?option=com_content&view=article&id=104:lesson-1-beaglebone-black-blink-led&catid=46:beaglebone-black&Itemid=81

I'm running ubuntu on my beaglebone black with nodejs 0.8.x

I can't figure out how to get it running without running as root.  It seems 
like there is some sort of permissions problem with my user because the 
project runs fine under root.  I added myself to the user group dialout but 
it didn't make a difference.  My question is, what do I need to do to give 
my user permission to the pin states.  The crash looks like this:

fs.js:338
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), 
mode);
 ^
Error: EACCES, permission denied 
'/sys/class/leds/beaglebone:green:usr0/trigger'
at Object.fs.openSync (fs.js:338:18)
at Object.fs.writeFileSync (fs.js:756:15)
at Object.f.pinMode 
(/home/ubuntu/projects/hello_express/node_modules/bonescript/index.js:132:20)
at Object. 
(/home/ubuntu/projects/hello_express/hello_express.js:31:3)
at Module._compile (module.js:449:26)
at Object.Module._extensions..js (module.js:467:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.runMain (module.js:492:10)
at process.startup.processNextTick.process._tickCallback (node.js:245:9)


Thanks in advance.

- Samuel

-- 
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/groups/opt_out.

[beagleboard] Apple full numeric [Aluminium] keyboard and internal hub does not work

[sushantkhanna1989]

Hi Guys

Someone asked a similar question before, but no one had an answer then.
I was going to give up and buy another keyboard but when I googled a bit 
more, I saw that a lot of people are able to use it with their beaglebone 
black.

I will explain the conditions and problem in details.

I have a beaglebone black powered up via a USB charger (NOT via the 5V DC 
adapter)
I have it connected to a display via a microHDMI cable.
I am running Angstrom. Updated to 4.09.2013 image. (emmc boot)

When I plugged in a normal wired optical mouse, it powered up and I was 
able to use it.
I then used an Apple keyboard as described in the title and plugged the 
mouse to its internal hub on the sides. Nothing worked, both did not show 
any signs of being powered up.
I of course rebooted and checked *lsusb *output. I could see the Apple 
device listed there.

Is this a driver issue or a power supply problem?
Kinda new, so help me out please.

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/groups/opt_out.

Re: [beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[Micka]

well, you shouldn't blame the company behind the BBB, neither the community.

*It's entirely your fault*, you decided for your product to use open source
solution !

 Yes it's attractive, you don't need to buy a license for windows CE, but
you should have made some research and discovered since we moved to the new
kernel, not all of the functions are available.

*It's unacceptable for a company to bet that the BBB will work in few
months *

In my case, i was at the same position as you 6 months ago, I wanted to use
the RS485 Cap ... and you know what ? I decided to spend 2 months to find
out how to modify the drivers. And now It's working ! ( Thx  again everyone
for your help again)


So, you should instead blame yourself or spend some time to help us, and
find out what's wrong with the LCD.. .

IF you don't have TIME, give some money to this community and I'm sure that
a developer will put this bug in priority.


Michael Musset,


On Thu, Sep 26, 2013 at 2:59 PM, garyamort  wrote:

>
>
> On Thursday, September 26, 2013 5:09:30 AM UTC-4, Diogene wrote:
>>
>> We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
>> Nothing does work as expected!!!
>> Use of Touchscreen is hawfully slow and use of ADC with this screen hangs
>> up the system!
>>
>> How to get a such bad system. It is the same with angstrom distrib!!!
>>
>> We had developp a specific cape and we can put it in garbage!!!
>>
>>
> I'll happily pay for shipping if you want to send me the cape and board.
> :-)
>
>
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

[beagleboard] Help with UART on BBB using Python

[Patrick Finucane]

Hi,
 
I am new to BBB and Linux.  I am trying to set up a very simple BBB to 
Arduino serial connection.  I am running Angstorm, which I updated.  I have 
loaded the adafruit python library's and have been able to control servo 
and steppers.  I installed pyserial and python can import it.
 
I have tried to follow this 
http://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black/uart 
example 
from adafruit. But it throws messages that are not included in the example 
like "return 1 lookup_uart_by_name".  And I get this error.
 

> serial.serialutil.SerialException: could not open port /dev/ttyO1: [Errno 
> 2] No such file or directory: '/dev/ttyO1'

 
I think that the adafruit library is failing to create the overlays.  If I 
check the /dev folder I don't see ttyO0, ttyO1 etc.  I do see ttyS1 thur 
ttyS3, is that the UART connection?  Are the ttyO1 files there by default 
or is that an "overlay" that must be created?  
 
If the adafruit library is failing to create the overlay can I create one 
by hand?  Is it just a file I can copy into the correct location?  
 
As you can tell I am a little lost (to the point I don't even know what I 
should be googling) so any help would be greatly appreciated.
 
thanks,
Patrick
 
 
 

-- 
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/groups/opt_out.

[beagleboard] Re: Beaglebone Black ... What a Bull Shit !!!

[garyamort]

On Thursday, September 26, 2013 5:09:30 AM UTC-4, Diogene wrote:
>
> We have tested BBB with LCD7 cape and Unbuntu 12.04 & 13.04.
> Nothing does work as expected!!!
> Use of Touchscreen is hawfully slow and use of ADC with this screen hangs 
> up the system!
>
> How to get a such bad system. It is the same with angstrom distrib!!!
>
> We had developp a specific cape and we can put it in garbage!!!
>
>
I'll happily pay for shipping if you want to send me the cape and board. :-)

 

-- 
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/groups/opt_out.

Re: [beagleboard] Re: Modbus

[garyamort]

On Thursday, September 26, 2013 8:43:44 AM UTC-4, garyamort wrote:
>
>
>
>
> Then modify the bandwidth-client and random-client to swap the localhost 
> address[127.0.0.1, port 1502] with the gateway adddress[192.168.7.3, port 
> 502] and rerun them to see if you get a connection.
>

Opps. I think I have my terminology wrong.  I automatically think of 
"master" as the server and "slave" as the client - but for Modbus this is 
reversed?  Ie the Master is the system which makes the connection and 
requests data.  While the slave is the one to wait for connections and 
respond?

If that's the case, then you would need to change the port number in 
bandwidth-server and random-server from 1502 to 502[to match the HMI 
Master] and run them, then the HMI Master can connect to them and try to 
read/write data.  Obviously once you have it connecting then you will need 
to modify your server code to respond to the appropriate commands.


-- 
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/groups/opt_out.

[beagleboard] Re: BBB SPI slave, bad data stuck on bus

[shedmeister]

Problem solved.  My assumption was that the last value written to the TX 
FIFO would be the value stuck on the bus if I stopped feeding the FIFO. 
 The TRM (24.3.3.2.2) explicitly says this:

"When the FIFO is enabled, the data read while the underflow flag is set 
will not be the last word written to the FIFO."

I assume that "data read" refers to data read by the master.  And I never 
did figure out what the byte stuck on the bus corresponded to, seems fairly 
arbitrary.

Anyway, the solution is:  If using the TX FIFO, you must keep it serviced. 
 If you want to implement a lazy man's transmitter, that is, only write to 
the transmitter when you actually have something to send, then don't use 
FIFO mode.  In this mode it works more like other SPI devices - the byte 
repeated on the bus will be the last byte written to the TX register.

Thanks,
 Jim



On Sunday, August 25, 2013 5:09:32 PM UTC-4, shedmeister wrote:
>
> I'm having an intermittent problem running the BBB's SPI1 in slave mode. 
>  I have designed all my TX messages to end in 0, and have verified every 
> way I know how that the last byte written to MCSPI_TX0 is 0.  But after a 
> few minutes of running, there is a non-zero value stuck on the output.  It 
> is usually 0x80, (I am in 8-bit mode), and I can clearly see the 0x80 
> coming out of the D1 line on a scope.  The communication is very reliable 
> initially, several messages get through OK before the error.  I have to 
> soft reset the BBB'S SPI to clear the error condition.
>
> Any ideas?
>  Thanks,
>   Jim
>
>
>

-- 
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/groups/opt_out.

Re: [beagleboard] device tree support

[Robert Nelson]

On Thu, Sep 26, 2013 at 12:17 AM, Saransh Jain  wrote:
> Thanks RobertCNelson
>
> I asked for uimage because I also wanted to try booting using tftp which
> requires transferring uimage and device tree to the ram.Can I use zimage
> instead of uimage for tftpboot?If so,is there any change in the command for
> boot?

tftpboot is just a media transfer command.. You just going to tfpboot
some binary from a server to an andress. zImage just needs to be
called by "bootz " where as uImage needs "bootm "

> Also I am not sure  how the boot using uimage and zimage takes place and
> what difference does it make in u-boot.You said that the uimage has a load
> address hardcoded.So how does zimage gets the load address?Can you please
> elaborate? Thanks  for the help.

Well, the soc already knows the address...

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/groups/opt_out.

Re: [beagleboard] Re: Modbus

[garyamort]

On Wednesday, September 25, 2013 2:00:52 PM UTC-4, Gerald wrote:
>
> The BB cannot be modified. But, there is another board that supports it.
>
> http://www.ti.com/tool/tmdxice3359
>
> It requires special SW in the PRU to support it.
>
> Gerald
>
>
>
I'm not at all familiar with Modbus, so I expect I am wrong, but would not 
his use case be supported?  He's not doing direct Modbus communication, but 
rather encapsulating it inside TCP/IP and then sending it over the network. 
 The gateway device is responsible for converting the TCPIP packets into 
correct modbus format for the actual modbus network[and vice versa going 
back]

Wouldn't the PRU/ethernet configuration be used if using the Ethernet 
wiring to run an Ethercat network ?

For testing, instead of node.js I'd go with libmodbus as it is an extremely 
mature implementation: http://libmodbus.org/

Install libmodbus and compile the test apps 
https://github.com/stephane/libmodbus/tree/master/tests and run them.

Then modify the bandwidth-client and random-client to swap the localhost 
address[127.0.0.1, port 1502] with the gateway adddress[192.168.7.3, port 
502] and rerun them to see if you get a connection.

After that, your dependent on what you actually want to do - you will need 
to copy one of the client apps and modify it to send the commands your 
interested in.

-- 
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/groups/opt_out.

[beagleboard] anyone using barebox for their BBB?

[Robert P. J. Day]

  thought i'd check in on barebox again, and i see there have been
definite, recent patches for BBB support:

http://www.spinics.net/lists/u-boot-v2/msg15909.html

  anyone using barebox on a regular basis for booting their BBB? any
issues?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
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/groups/opt_out.

[beagleboard] Re: How can I improve processing time on BB?

[garyamort]

On Thursday, September 26, 2013 4:47:17 AM UTC-4, 서재필 wrote:
>
> I'm trying to use Beagle Board for real-time audio-processing.
>  
> I bought this one because of these clock speed(1Ghz).
>  
> My algorithm running time is about 0.6 ms for one frame in my 
> computer(window7, 2.6Ghz Quad-core).
>  
> But when I run my algorithm on BB(Angstrom, 1Ghz), it spends about 
> 40ms for one frame.
>  
> Isn't it ridiculous? Because clock speed defference is just 2 or max 3 
> times. But measuring processing speed is not.
>  
> Wha'ts wrong with it?
>


Assuming that you can make a fair comparison of clock speed to 
performance[which you can't], your difference is over 10 times, not 2 or 3. 
 Your comparing a quad core device with a single core device.  Right off 
the bat this will cause issues since Linux is not real time operating 
system tuned for a specific set of tasks, it is a general operating system 
- so it is running multiple processes at the same time.  On your quad core 
device, you have some buffer since the running programs will be spread 
between different processors.  The Bone will be running everything on one 
core.


Firstly, did you make sure to adjust the priority of your process to give 
it a big share of the processor space?  If running from the command line, 
for example "runmyprogram" instead run it as "sudo nice --adjustment=-20 
runmyprogram*"*

Secondly, you have to consider what your doing.  Your doing audio 
processing.  What do musicians do for that? They use Linux with the Real 
Time performance enhancements installed.  This lets you give your process 
higher priority over almost everything else, including most of the 
operating system.  So you need to recompile your kernel for that.

Thirdly, your processing a large amount of data, correct?  And your trying 
to store it on the "hard drive" I bet - which is a slow MMC card[as opposed 
to your fast SATA hard drive on your windows box].  The simple solution 
there is to sacrifice some memory and setup a ram disk.  Check your 
/etc/fstab file - you probably already have a small ramdisk setup there to 
map to the /temp directory using the tmpfs file system.  Just increase that 
up to 128M and do all your file processing in the /temp folder.

Fourthly, avoid disparaging seeming comments like "isn't it ridiculous" and 
instead phrase them in such a way as to take responsibility for the failing 
such as "I'm sure I am doing something wrong.  What methods are there to 
increase performance?"

Speaking for myself personally, it makes the difference when I answer 
between my taking the time to do a few google searches and provide links to 
articles explaining how to implement something vs just giving the answers 
and leaving looking up implementation to the other party.

-- 
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/groups/opt_out.

Re: [beagleboard] Re: problems with webcams

[Matthew Witherwax]

-o is not used to indicate which frames to convert to OpenCV Mats and 
requires an integer argument
should read
-o is now used to indicate which frames to convert to OpenCV Mats and 
requires an integer argument

On Thursday, September 26, 2013 6:46:39 AM UTC-5, Matthew Witherwax wrote:
>
> Mike,
>
> Here is the cleaned up one.  Here are the differences:
> -o is not used to indicate which frames to convert to OpenCV Mats and 
> requires an integer argument
> -o 1 would convert every frame
> -o 2 would convert every 2nd or ever other, etc
> default is 1
>
> -p is similar to -o in the original framegrabber.  However, it doesn't 
> actually output anything.  It just controls if any frames are to be 
> converted.
>
> Captured count and processed count variables have been renamed and moved 
> to the top.
>
> Formatting has been corrected.
>
>
> Testing of your procedure to follow.
>
>
> On Wed, Sep 25, 2013 at 12:55 PM, Matthew Witherwax wrote:
>
>> Mike,
>>
>> Looking over the code in you document, I noticed some formatting was off 
>> and I needed to clean up the way I handled processing the subset of the 
>> frames.  I am cleaning things up and will get you a new version shortly.
>>
>>
>> On Tue, Sep 24, 2013 at 8:53 PM, Michael Darling wrote:
>>
>>> Thanks!  You're absolutely welcome to distribute it freely. I don't have 
>>> my own website so that's a great way to share the information.
>>>
>>> Luckily I have most of my CV algorithm done. I have a bit of cleaning up 
>>> to do but most of my work is implementing hardware from here on out.
>>>
>>> Thanks again SO much for your help!  I look forward to getting feedback 
>>> on the write up.
>>>
>>> -Mike
>>>
>>>
>>> On Tuesday, September 24, 2013, Matthew Witherwax wrote:
>>>
 Mike,

 Great write up.  When I have some free time, I will replicate your 
 steps on my BBB running Arch Linux.  Not sure if you have a personal 
 website, but would you mind me posting this to my blog once it makes it 
 out 
 of draft?

 I look forward to seeing your aircraft in action; on to the CV problems!


 On Tue, Sep 24, 2013 at 7:39 PM, Michael Darling wrote:

 Hi Richard,

 Here is a summary of what I ended up doing to get 30 fps out of the 
 BBB. You are right -- it simply came down to taking advantage of NEON 
 hardware acceleration.  My little "How-To" guide might be a bit verbose, 
  but you can skip all of the background information and skip right to the 
 steps I took if you like. However reading some of the background 
 information might give you some more insight into what I have already 
 tried 
 with the PS3 Eye (along with many others like Matthew) and what we have 
 learned. Its also chock-full of great references on the topic.

 Right now, I am considering this a DRAFT as I have not gone back 
 through to make sure that all the commands I pasted will work verbatim. If 
 you're pretty comfortable in Linux, I'm sure this is enough for you to 
 replicate what I have done.

 I wrote it up in LaTeX, as that was the easiest for me, so here it is 
 in both PDF and HTML format.

 Best of luck.  If you end up taking a look at this, please let me know 
 if you have any comments or suggestions for improvement.

 -Mike


 On Tue, Sep 24, 2013 at 3:52 PM, rh_ wrote:

 On Tue, 24 Sep 2013 13:41:14 -0500
 Matthew Witherwax 
 wrote:

 > Richard,
 >
 > Please see the post
 > http://blog.lemoneerlabs.com/post/BBB-webcamsconcerning the PS3Eye,
 > C920, and frame rates.  I believe it will answer
 > your questions.

 Ok it seems that OpenCV is the limiter. But the camera is significant.
 I like the idea of using a USB camera due to low cost. But I dont like
 it due to limited features.  However the limitations of cheap USB might
 be overcome by using two cameras. Although only to a small degree.
 Probably need a camera cape to get at the camera features. And a
 feature-full camera.  I am thinking of repurposing a video camera
 as most have lots of features but are fairly cheap.

 --
 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/G5Xs2JuwD_4/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/groups/opt_out.


  -- 
 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://group