Re: [beagleboard] Unable to ping host machine

[Tsan-Ming Chou]

You are welcome.


2014-04-17 14:37 GMT+08:00 Jacob Vasu :

> Hi Tsan-Ming Chou...that worked! Thanks a lot! And thanks for your time
> too, William Hermans!
>
>
> On Thursday, April 17, 2014 11:42:59 AM UTC+5:30, Tsan-Ming Chou wrote:
>
>> Please refer to "How to enable ICMP echo requests (Ping) in Windows XP"  (
>> http://wiki.phys.ethz.ch/readme/how_to_enable_icmp_
>> echo_requests_ping_in_windows_xp_service_pack_2).
>>
>>
>> 2014-04-17 13:26 GMT+08:00 William Hermans :
>>
>>> That gateway address should be wrong. That would be the network.
>>> 192.168.1.1 may be the gateway / nameserver, but i am not sure how your
>>> network is setup.
>>>
>>> How are your BBxM and host computer connected ? USBNET or ethernet ? IS
>>> there a router between the two systems or is teh BBxM connected directly to
>>> the host computer ? Host to me implies they are directly connected, but I
>>> do not remember if the xM has onboard ethernet or not.
>>>
>>>
>>> On Wed, Apr 16, 2014 at 10:22 PM, Jacob Vasu  wrote:
>>>
 I get this:
  ubuntu@bbxm:~$ cat /etc/network/interfaces
 auto lo
 iface lo inet loopback
 auto eth0
 iface eth0 inet static
 address 192.168.1.4
 netmask 255.255.255.0
 gateway 192.168.1.0
 hwaddress ether 3e:7f:da:ee:b1:db

 On Thursday, April 17, 2014 10:37:24 AM UTC+5:30, William Hermans wrote:

> Ok, I am not sure what you're doing there, but those nameservers do
> not match your ifconfig output.
>
> Try commenting out all of those atleast temporarily by adding a pound
> sign in front of ech statement ( # ) andthen add . . .
>
>  nameserver 192.168.1.1
>
> Just for kicks what do you have in /etc/network/interfaces ?
>
>
>
>
> On Wed, Apr 16, 2014 at 9:56 PM, Jacob Vasu  wrote:
>
>> Hi William,
>>
>> ubuntu@bbxm:~$ cat /etc/resolv.conf
>> domain mathworks.com
>> search mathworks.com
>> nameserver 144.212.95.9
>> nameserver 144.212.95.8
>> nameserver 144.212.2.11
>>
>> Thanks!
>>
>> On Thursday, April 17, 2014 9:13:42 AM UTC+5:30, William Hermans
>> wrote:
>>
>>> What is the contents of /etc/resolv.conf ?
>>>
>>>
>>> On Wed, Apr 16, 2014 at 8:24 PM, Jacob Vasu wrote:
>>>

 Hi,

 I'm using MATLAB to program my beagleboard xm. I ran into a strange
 problem. I'm able to ping the board from my host machine (Windows 7) 
 but
 not the other way around i.e. I cannot ping my host from the bbxm. 
 Here are
 my results for ifconfig on the bbxm:

 ubuntu@bbxm:~$ ifconfig
 eth0  Link encap:Ethernet  HWaddr 3e:7f:da:ee:b1:db
   inet addr:192.168.1.4  Bcast:192.168.1.255
  Mask:255.255.255.0
   inet6 addr: fe80::3c7f:daff:feee:b1db/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1488  Metric:1
   RX packets:297 errors:0 dropped:0 overruns:0 frame:0
   TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:1000
   RX bytes:20184 (20.1 KB)  TX bytes:4860 (4.8 KB)

 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:16436  Metric:1
   RX packets:22 errors:0 dropped:0 overruns:0 frame:0
   TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:1656 (1.6 KB)  TX bytes:1656 (1.6 KB)

 My BB OS is ubuntu
 ubuntu@bbxm:~$ lsb_release -a
 No LSB modules are available.
 Distributor ID: Ubuntu
 Description:Ubuntu 11.04
 Release:11.04
 Codename:   natty

 Any idea what's causing this? 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/d/optout.

>>>
>>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google
>> Groups "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to beagleboard...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the

Re: [beagleboard] Re: PRU Multiply and accumulate - how many cycles?

[Bas Laarhoven]

Ah, you didn't mention you were synchronizing the PRUs in your first mail!

Note that use of the MAC is not that obvious, and there is (was?) little 
documentation.
Some issues I found had to do with the overflow/carry flag. It seems to 
lag one cycle and it cannot be cleared without clearing the entire 
accumulator.


Now this information is more than a year old (11/2012), so maybe the 
silicon and/or documentation have been fixed in the meantime, but be 
prepared for some surprises!


-- Bas


On 17-4-2014 1:59, Lenny wrote:


Thanks for the help Bas!

I guess i found the problem:

In my code, I used PRU0 simply as a timer with the code

LOOP:
WAIT(250 cycles)
XOUT 14,r5,4 //transfer register r5 from PRU0 to PRU1
JMP LOOP

In the meantime, PRU1 did some tasks, including multiplication using 
XOUT/XIN 0,r25,1 and similar instructions, and finally should have 
stalled at the instruction

XIN 14,r5,4
in order to synchronize with PRU0.

However, if the timing is initially not right, it can happen that PRU0 
waits for the other PRU while blocking the XCHG port with its XOUT 
14,... command. If now PRU1 wants to retrieve the result of a 
multiplication, e.g. execute XIN 0,r26,4, then it will wait until the 
XCHG port is liberated by PRU0, which itself will wait for maximally 
1024 cycles if PRU1 accepts its XOUT request while keeping the port 
blocked, such that PRU1 can never get to that section in the code in 
time. In this case the two PRU's block each other and the programs 
runs about 1000 times slower!


Also, the controls which are run to ensure a proper transfer through 
the XCHG port are quite basic: It seems to me that for a successful 
transfer between two PRUs, one only needs one PRU that is willing to 
write (launching XOUT 14,... ) and the other willing to read (XIN 
14,...). The actual registers which are to be read or written, or the 
amount of data does not have to match between the two commands. If 
they dont match, I dont know what data is actually written, but at 
least none of the PRUs stalls for 1024 cycles.

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google 
Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to beagleboard+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unable to ping host machine

[William Hermans]

well first, I am not a network guru, however I think that. . .

nameserver in /etc/resolv.conf would be 192.168.1.1 ( assuming by modem,
its a DSL/cable modem + router)
gateway in /etc/network/interfaces would be your host computers ip
Then, you BBxM would be any IP in the same range as your host computer.
192.168.1.4 would work fine as long as there was nothing else on the
network with this IP already.

Anyhow, sounds like you've solved your issue already, but you did have some
funky settings anyhow. SO they already needed fixing.


On Thu, Apr 17, 2014 at 12:37 AM, Tsan-Ming Chou wrote:

> You are welcome.
>
>
> 2014-04-17 14:37 GMT+08:00 Jacob Vasu :
>
> Hi Tsan-Ming Chou...that worked! Thanks a lot! And thanks for your time
>> too, William Hermans!
>>
>>
>> On Thursday, April 17, 2014 11:42:59 AM UTC+5:30, Tsan-Ming Chou wrote:
>>
>>> Please refer to "How to enable ICMP echo requests (Ping) in Windows XP"
>>> (http://wiki.phys.ethz.ch/readme/how_to_enable_icmp_
>>> echo_requests_ping_in_windows_xp_service_pack_2).
>>>
>>>
>>> 2014-04-17 13:26 GMT+08:00 William Hermans :
>>>
  That gateway address should be wrong. That would be the network.
 192.168.1.1 may be the gateway / nameserver, but i am not sure how your
 network is setup.

 How are your BBxM and host computer connected ? USBNET or ethernet ? IS
 there a router between the two systems or is teh BBxM connected directly to
 the host computer ? Host to me implies they are directly connected, but I
 do not remember if the xM has onboard ethernet or not.


 On Wed, Apr 16, 2014 at 10:22 PM, Jacob Vasu  wrote:

> I get this:
>  ubuntu@bbxm:~$ cat /etc/network/interfaces
> auto lo
> iface lo inet loopback
> auto eth0
> iface eth0 inet static
> address 192.168.1.4
> netmask 255.255.255.0
> gateway 192.168.1.0
> hwaddress ether 3e:7f:da:ee:b1:db
>
> On Thursday, April 17, 2014 10:37:24 AM UTC+5:30, William Hermans
> wrote:
>
>> Ok, I am not sure what you're doing there, but those nameservers do
>> not match your ifconfig output.
>>
>> Try commenting out all of those atleast temporarily by adding a pound
>> sign in front of ech statement ( # ) andthen add . . .
>>
>>  nameserver 192.168.1.1
>>
>> Just for kicks what do you have in /etc/network/interfaces ?
>>
>>
>>
>>
>> On Wed, Apr 16, 2014 at 9:56 PM, Jacob Vasu wrote:
>>
>>> Hi William,
>>>
>>> ubuntu@bbxm:~$ cat /etc/resolv.conf
>>> domain mathworks.com
>>> search mathworks.com
>>> nameserver 144.212.95.9
>>> nameserver 144.212.95.8
>>> nameserver 144.212.2.11
>>>
>>> Thanks!
>>>
>>> On Thursday, April 17, 2014 9:13:42 AM UTC+5:30, William Hermans
>>> wrote:
>>>
 What is the contents of /etc/resolv.conf ?


 On Wed, Apr 16, 2014 at 8:24 PM, Jacob Vasu wrote:

>
> Hi,
>
> I'm using MATLAB to program my beagleboard xm. I ran into a
> strange problem. I'm able to ping the board from my host machine 
> (Windows
> 7) but not the other way around i.e. I cannot ping my host from the 
> bbxm.
> Here are my results for ifconfig on the bbxm:
>
> ubuntu@bbxm:~$ ifconfig
> eth0  Link encap:Ethernet  HWaddr 3e:7f:da:ee:b1:db
>   inet addr:192.168.1.4  Bcast:192.168.1.255
>  Mask:255.255.255.0
>   inet6 addr: fe80::3c7f:daff:feee:b1db/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1488  Metric:1
>   RX packets:297 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:20184 (20.1 KB)  TX bytes:4860 (4.8 KB)
>
> 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:16436  Metric:1
>   RX packets:22 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:1656 (1.6 KB)  TX bytes:1656 (1.6 KB)
>
> My BB OS is ubuntu
> ubuntu@bbxm:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:Ubuntu 11.04
> Release:11.04
> Codename:   natty
>
> Any idea what's causing this? 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 re

[beagleboard] Updating to the most recent of R Nelson's kernel sources

[cwrseckford]

Does anyone know the set of git commands needed to update one of R Nelson's 
kernel sources?  His original shell scripts are faultless, but the only way 
I can find to update a  build to the most recent version is to wipe the 
directory and start again with a full download.  This needs several hours 
and a fast connection, and there must be some set of git fetch commands 
that would just get the most recent files needed.  However, git and I are 
violently antipathetic, and I can't find out what those commands might be.

Thanks for any ideas - Will

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Updating to the most recent of R Nelson's kernel sources

[Charles Steinkuehler]

On 4/17/2014 7:37 AM, cwrseckf...@gmail.com wrote:
> Does anyone know the set of git commands needed to update one of R Nelson's 
> kernel sources?  His original shell scripts are faultless, but the only way 
> I can find to update a  build to the most recent version is to wipe the 
> directory and start again with a full download.  This needs several hours 
> and a fast connection, and there must be some set of git fetch commands 
> that would just get the most recent files needed.  However, git and I are 
> violently antipathetic, and I can't find out what those commands might be.
> 
> Thanks for any ideas - Will

Did you try a simple:

  git pull origin

...from inside your working copy?

Also, take a look at the system.sh.sample file.  If you have a Linux
kernel git repository locally (or care to create one), you can point to
it with a system.sh file (created using the system.sh.sample as an
example) and it will get reused so you won't need to download it each
time you build.  Robert's scripts will download and reuse a copy of the
kernel source for you, but it's inside the working directory so if you
delete everything and re-clone the Robert's linux-dev repo, you'll have
to download the kernel source all over again.

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Updating to the most recent of R Nelson's kernel sources

[Robert Nelson]

On Thu, Apr 17, 2014 at 7:37 AM,   wrote:
> Does anyone know the set of git commands needed to update one of R Nelson's
> kernel sources?  His original shell scripts are faultless, but the only way
> I can find to update a  build to the most recent version is to wipe the
> directory and start again with a full download.  This needs several hours
> and a fast connection, and there must be some set of git fetch commands that
> would just get the most recent files needed.  However, git and I are
> violently antipathetic, and I can't find out what those commands might be.
>
> Thanks for any ideas - Will

git checkout master -f
git pull

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Where is asoundlib.h?

[KurtE]

Thanks, that does look cleaner.  I hope this works for mbelg...   

Personally I am happy that I moved my BBBk to Debian, but locally I have 
updated my readme with the information, in case I need to do this again 
(will update on my github soon).   Also looks like good general purpose 
advice so again thanks.

On Wednesday, April 16, 2014 8:41:24 PM UTC-7, john3909 wrote:
>
>
> From: KurtE >
> Reply-To: >
> Date: Wednesday, April 16, 2014 at 5:45 PM
> To: >
> Subject: Re: [beagleboard] Where is asoundlib.h?
>
> I could be wrong, but when I was trying to do this awhile ago on Angstrom, 
> I did not find it.  I ended up downloading and building the stuff on the 
> BBBk.  Now with Debian, I can now do like I did on the Raspberry Pi and and 
> do the apt-get install libasound2-dev
>
> More details on what I do is up on my Readme file of my github Raspberry 
> Pi project(Bad name, but was first linux box): 
> https://github.com/KurtE/Raspberry_Pi 
>
> From that readme:
>
> I did not find any valid packages to install the ALSA, so I did it 
> manually: 
>
> wget ftp://ftp.alsa-project.org/pub/lib/a...1.0.25.tar.bz2 
> tar jxf alsa-lib-1.0.25.tar.bz2
> cd alsa-lib-1.0.25
> ./configure
> make install
>
> Try this instead,
>
> apt-get source libasound2
> cd alsa-lib-1.0.25
> // if you want debug symbols
> export DEB_BUILD_OPTION=nostrip noopt debug
> dpkg-buildpackage -rfakeroot -uc -us -j8 -aarmhf
>
> // The dpkg-buildpackage uses the settings a patches in the debian folder 
> and builds the library as intended
> // This commands creates Debian packages in the parent folder.
>
> cd ..
> sudo dpkg -i libasound2* deb
>
> Regards,
> John
>
>
> This did not set the USB device to be default sound device, I used the 
> command: aplay -L to list the nodes. From which I created the configuration 
> file: /etc/asound.conf pcm.!default sysdefault:Device
>
> Again there may be easier ways, but that is what I did.  Note: I am using 
> a USB sound adapter...
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Robert Nelson]

On Thu, Apr 17, 2014 at 9:38 AM, Micka  wrote:
> Hi,
>
> My beagle received a multicast attack ( from an equipment not well
> configured ) .
>
> Since then, the LCD doesn't work anymore, but when I change the BBB with a a
> new one with the same SDCard, the LCD work . ... So the problem is not in
> the LCD 7 Cap, but in the BBB.

Really? I find it hard to believe those two events are linked...

> But I can't find where, and why ? Gerald is it possible that the board is
> broken electrically ?
> Robert or someone else do you know a program that can prevent this ? or a
> patch ? my idea is to monitor the bandwidth and stop the interface if the
> bandwidth is used too much . .

setup a firewall?

> I tested this :
>
> export SLOTS=/sys/devices/bone_capemgr.9/slots
> debian@beaglebone:/Distrib/Scripts$ cat $SLOTS
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART4
>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART1
>
> So there is no LCD7 Cap mounted 

So.. What happens when you try to manually load the cape dtbo?

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Cody Lacey]

Was your hub plugged in at boot or after?  I may have a workaround you can
try.
If you know the hub enumerates post the contents of /sys/bus/usb/devices


On Wed, Apr 16, 2014 at 9:59 PM, William Hermans  wrote:

> I have no hands on with this sort of thing, but I have noticed on many
> occations that "we" always need to research the hardware we use on a
> particular Linux Distro.
>
> .Which kernel are you using again ? 3.8.x does not do Hotplug very well,
> or even at all. SO if you're hot plugging USB devices into the hub after
> the system is up and running, It could be that the hub may buffer you from
> a kernel oops, but still does not recognize the devices.
>
> It could also be that you need to compile a module or two into the kernel
> statically for the HUB to work properly. But that is just a guess on my
> behalf that could be wrong. I have not personally noticed anything specific
> to this when browsing menuconfig, but I was not looking for this sort of
> thing when compiling my own kernel.
>
> *OR* Maybe you just need a different hub . . . Perhaps someone with more
> experience with this sort of thing will reply and give us their 2 cents.
>
>
> On Wed, Apr 16, 2014 at 7:40 PM,  wrote:
>
>> Hi William,
>>
>> Yes, I realize that the pain is self-inflicted and I want to be clear
>> about that. I have a favourite golfer that once said,"I'm an idiot!". I've
>> uttered those very words once or twice lately. Judging by the forums I
>> think others have said similar things.
>>
>> You would never believe it by my comments but in the late 1980's I was
>> doing this full time on a RT VME chassis running UniFlex (Unix variant). I
>> wrote drivers in C and 68030 assembly language and did some very neat
>> stuff. The learning curve was steep back then too. Ah, but I was young!
>> Time didn't matter...So I had to see what the kids are getting into these
>> days.
>>
>> I am actually more concerned with another issue regarding attaching a USB
>> hub to the USB host on the BBB. After I've done that the system won't
>> enumerate any of the devices I've put into the hub. But according to dmesg
>> the hub itself was successfully installed.
>>
>> Ideas?
>>
>>
>>
>> On Monday, April 14, 2014 3:24:04 PM UTC-7, William Hermans wrote:
>>>
>>> macarr, just so you know I have been using Debian for a good while and
>>> it took me 2-3 tries to get his steps right myself. At the time the
>>> instructions were a bit less clear, but the fault was my own ( I was a bit
>>> rusty with some of the steps / commands ).
>>>
>>> I am currently rebuilding my own kernel to the latest from scratch, and
>>> so far they seem to work perfectly ( I am about half way through, e.g. I've
>>> downloaded all the tools and have compiled the kernel).
>>>
>>> @Robert, I should be able to do the same steps I took back in December
>>> to get a working TFTP/NSF boot/root with the latest kernel ?
>>>
>>> What about 3.13 ? I remember you saying something about it being a
>>> "different animal" some months ago.
>>>
>>> I would ask on your comments pages for your site, but . . . Yeah editor
>>> wont stop loading.
>>>
>>>
>>> On Mon, Apr 14, 2014 at 1:15 PM,  wrote:
>>>
 Yes Robert,

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

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

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

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

 Respectfully,

  --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to beagleboard...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.o

[beagleboard] Building the WL18xx Cape Kernel Patch with Angstrom for BeagleBone Black

[lafaireroberto]

I was wondering if anyone had any information regarding the flashing of the 
patched kernel files for the Beagle Bone Black so as to ensure Wi-Fi Cape 
functionality (TL18XX). I am aware of the following Wiki:

http://processors.wiki.ti.com/index.php/Using_the_WL18xx_Cape_with_BeagleBone_Black

However, this specifically describes the process for an experienced Linux 
user using an Ubuntu distribution. Unfortunately, I am still learning Linux 
from scratch and have tried to follow this process using an Ubuntu 
distribution booted from a USB disk on my personal Windows 8.1 computer, 
which is where all the software is being developed, but to no avail. 

Is there anyone I can get in contact with for technical support on building 
an image file that will flash the eMMC of the Beagle Bone Black with the 
kernel patch applied along with the Angstrom Distribution that comes with 
the Beagle Bone Black?

If anyone has the latest Angstrom Distribution pre-built image with the 
patch already applied it would be extremely helpful or some simpler 
instructions for a novice Linux user still learning all the intricate inner 
workings.

Thank you for your time!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Black & Audio

[mattnmusic4]

Hi Victor:
The SoundsCape by Simple Media Networks may be just what you are 
looking for: http://kck.st/1jumP8o   

This cape provides line out & Headphone out with some very nice mixing 
features.

On Thursday, April 25, 2013 5:40:48 AM UTC-4, victor@gmail.com wrote:
>
> Hello,
>
> I'm looking forward to buy a BeagleBone black because it features HDMI but 
> I'm disapointed there is not audio jack 3.5 output.
> I know that audio can transit via HDMI but I would like to use the 
> BeagleBone as a media center (including audio) and I need multiple outputs.
>
> 1. Is there any way to extract audio to a 3.5mm audio jack from the HDMI 
> (a solution that cost less than 40$)
> 2. Why are the audio capes so expensive ? They cost more than the 
> BeagleBone itself :|
>
> Any advice appreciated on how-to connect a BeagleBone (black or not) to a 
> 3.5 mm jack.
>
> Bye bye

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[C Wong]

Hey Bas,

Quick side question: was wondering if you're able to run any PRU related 
test apps? I have an application that needs xenomai and the PRU(s) and had 
a hard time getting the standard-available debian eMMC image to play with 
xenomai and the pru nicely. I was able to quickly modify the 
cloud9-Angstrom build and add both xenomai where the pru module loads and 
ran the example apps fine, so off I went that route (with everything 
working except hdmi--ok for now). Debian offers some nice compatibility 
with folks I work with that use ROS, but don't want to about-face finding 
that I can't get xenomai or the PRU to work right...

thanks
--C

On Monday, April 14, 2014 1:51:58 AM UTC-7, Bas Laarhoven wrote:
>
>  
> Robert,
>
> The Embest board I received from Farnell last week ago has been used in my 
> BeBoPr++ production test system and I have not experienced any 
> incompatibilities. 
>
> As I posted earlier, the Angstrom software on the board was identical to 
> that on a original rev B BBB. The only differences discovered thus far are 
> mechanical and quality related. I replaced Angstrom with the Debian trial 
> image and have had no problems (other than those that were present on the 
> original BBB too). 
>
> The on-board EEPROM contents differ and can be used to identify the boards 
> if needed:
>
> Embest:
>
> 000 aa 55 33 ee 41 33 33 35 42 4e 4c 54 30 30 41 35
> 020 33 30 30 31 42 42 42 4b 39 36 30 30 58 41 58 58
> 040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 060 30 31 32 33 34 35 36 37 38 39 41 42 43 44 45 46
> 100 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>
> strings: "A335BNLT00A53001BBBK9600XAXX" "0123456789ABCDEF"
>
> BBB:
> 000 aa 55 33 ee 41 33 33 35 42 4e 4c 54 30 30 30 42
> 020 31 30 31 34 42 42 42 4b 31 30 39 33 ff ff ff ff
> 040 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 060 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 100 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>
> strings: "A335BNLT000B1014BBBK1093"
>
> Except from that, both boards seem identical from a software point of view.
>
> -- Bas
>
>
> On 14-4-2014 8:59, robert.berger wrote:
>  
> Hi Jason,
>
> On Monday, April 14, 2014 2:07:00 AM UTC+3, Jason Kridner wrote: 
>>
>> Just about to post this to http://beagleboard.org/blog, but it 
>> wouldn't hurt to get a bit of community feedback before pushing this 
>> out there 
>>
>  
> What I would be interested is software (binary) compatibility between the 
> Circuitco BBB and the Embest BB Black.
> I can't find it right now, but Rob Nelson mentioned something like "only 
> supports the Circuitco Version".
>
> Can you please enlighten me a bit on possible differences which require 
> software adjustments?
>
> I mean can I take an SD card which runs on a  Circuitco BBB and expect 
> this to work on an Embest BB Black?
>
> BTW I will do a webinar "From Arduino Uno to BeagleBone Black (and 
> back)![1] on 17th and such a question might arise.
>
> Regards,
>
> Robert
>
> [1] http://www.element14.com/community/events/4021
>
>  
>
>   -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>
>  

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Change default state of GPIO pin

[het . oosten]

I have a beeper which is controlled by GPIO P9.12. The problem is that the 
default state of this pin is high (I think this is the problem). So I have 
a long and annoying beep when the BBB boots. This stops when my programm is 
loaded, then everything works as it should. 

Is there a way to set the default state of this pin to low?

Regards,

Rob

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: HDMI to VGA, on boot the board displays its logo, but then ceases to display anything. Please Help

[kaitong758]

you can touch the componet RT1.RT1 is a PTC. When your HDMI to VGA cable 
need stronger power supply, the RT1 will got hot. The power supply of HDMI 
to VGA cable will be cut off. So you can short the two pins of RT1. Maybe 
the problem can be solved.

On Saturday, March 22, 2014 4:20:03 AM UTC+8, Sam McDermott wrote:
>
> I recently got my beaglebone black, and thought that it would be a great 
> way to replace my old computer with something small that has equal power. 
>  I also wanted to reuse the old VGA monitor from the computer, so I got a 
> micro HDMI to VGA cable.  I plugged it into the monitor and it seemed to 
> work for a few seconds while the board booted, but then after the logo 
> disappeared I got a fuzzy screen and a no signal message.  I have two 
> questions.  First, what is going wrong, clearly all of the parts work?  And 
> second, How can I fix it or would it be best to abandon ship?  Link to 
> video on YouTube: http://youtu.be/ICbChuMQ9u8
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB USB0 change from client to host

[marcmltd]

Hello
I have finally managed to get my hands on an BBB and started to try and get 
my system up and running the way I need by building a kernel (3.14.1).
 
I am attempting to use the USB client port (USB0) in host mode and think I 
have done all the things necessary to get this working:
 
Kernel config has EHCI enabled and set to host only
Hardware mod on the board to short pins 4&5 of micro socket to force USB-ID 
low to indicate host mode.
Changed the arch/arm/boot/dts/am335x-bone-common.dtsi file to put it into 
host mode
usb@47401000 {
status = "okay";
dr_mode = "host";
};
usb@47401800 {
status = "okay";
dr_mode = "host";
};
 
No matter what I plug in nothing gets identified ???
 
Plugging into the USB1 host port is fine so the kernel is configured 
correctly.
 
 
Boot log shows ports being identified:
[2.057294] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
[2.063996] musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned 
bus number 1
[2.072673] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[2.079868] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[2.087467] usb usb1: Product: MUSB HDRC host driver
[2.092722] usb usb1: Manufacturer: Linux 3.14.1 musb-hcd
[2.098402] usb usb1: SerialNumber: musb-hdrc.0.auto
[2.104856] hub 1-0:1.0: USB hub found
[2.108880] hub 1-0:1.0: 1 port detected
[2.117574] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[2.124275] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned 
bus number 2
[2.133045] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[2.140253] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[2.147851] usb usb2: Product: MUSB HDRC host driver
[2.153105] usb usb2: Manufacturer: Linux 3.14.1 musb-hcd
[2.158786] usb usb2: SerialNumber: musb-hdrc.1.auto
[2.165268] hub 2-0:1.0: USB hub found
[2.169312] hub 2-0:1.0: 1 port detected

Any ideas ???
 
Thanks
marc 
 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Network Block Device or Network File System on BeagleBone Black

[cocoya354]

Hi!

Have a BeagleBone Black fresh from package, and i see, there is an USB 
client port. I am thinking about setup a Network Block Device Client or 
Network File System Client on that USB client port. A would like to use BBB 
as a mass storage device via that port, and connect it to a USB host 
system. I will install an NDB / NFS server too somewhere on network, and 
would like to configure BBB to connect to that.

I dont know much about BBB driver package, is there support or not. Plase 
tell me if this idea is about impossible, or give me tipps / links for 
something documentation / blog / forum topic if that exists. Thank you in 
any advance.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] USB mass storage on BeagleBone shown as mass storage under Windows

[ibinsdahanse]

Solved :-)
Thx !!!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB UART2 Write Issue (C/C++)

[Michael B.]

Hi,

I'm currently using the BBB to control a rover robot for a project at my 
university. I'm currently having an issue using the UART file /dev/ttyOx to 
write an array of characters to a smart servo using c/c++.
More specifically, I've opened the file using 
fopen("/dev/ttyO2", "wb")

which should open it in binary mode. I've also tried the c++ equivalent 
with 
ofstream file("/dev/ttyO2", ios::out|ios::binary)

For the most part these have worked fine. I have been using the UART tool 
for the PicKit 2 to verify what I've been receiving. But, despite having 
opened the file in binary mode, if I try to write 0x0A it will still append 
0x0D to form CRLF, or newline. 

For example, if I create a character array: 
char c[] = {0xFF,0xFF,0x0A,0x01,..}

This is seen on the UART tool:
 FF FF 0D 0A 01 ...

If anyone knows a fix, or can offer any insight (should I be approaching it 
incorrectly), I would greatly appreciate it.


 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Where is asoundlib.h?

[mbelge1971]

John: The instructions you provided are for debian. It does not work on 
Angstrom.

I solved this issue by uninstalling and re-installing alsa-dev package:

# opkg install alsa-dev

Then I got the alsa headers under /usr/include/alsa directory as expected. 

Murat

On Thursday, April 17, 2014 9:29:05 AM UTC-4, KurtE wrote:
>
> Thanks, that does look cleaner.  I hope this works for mbelg...   
>
> Personally I am happy that I moved my BBBk to Debian, but locally I have 
> updated my readme with the information, in case I need to do this again 
> (will update on my github soon).   Also looks like good general purpose 
> advice so again thanks.
>
> On Wednesday, April 16, 2014 8:41:24 PM UTC-7, john3909 wrote:
>>
>>
>> From: KurtE 
>> Reply-To: 
>> Date: Wednesday, April 16, 2014 at 5:45 PM
>> To: 
>> Subject: Re: [beagleboard] Where is asoundlib.h?
>>
>> I could be wrong, but when I was trying to do this awhile ago on 
>> Angstrom, I did not find it.  I ended up downloading and building the stuff 
>> on the BBBk.  Now with Debian, I can now do like I did on the Raspberry Pi 
>> and and do the apt-get install libasound2-dev
>>
>> More details on what I do is up on my Readme file of my github Raspberry 
>> Pi project(Bad name, but was first linux box): 
>> https://github.com/KurtE/Raspberry_Pi 
>>
>> From that readme:
>>
>> I did not find any valid packages to install the ALSA, so I did it 
>> manually: 
>>
>> wget ftp://ftp.alsa-project.org/pub/lib/a...1.0.25.tar.bz2 
>> tar jxf alsa-lib-1.0.25.tar.bz2
>> cd alsa-lib-1.0.25
>> ./configure
>> make install
>>
>> Try this instead,
>>
>> apt-get source libasound2
>> cd alsa-lib-1.0.25
>> // if you want debug symbols
>> export DEB_BUILD_OPTION=nostrip noopt debug
>> dpkg-buildpackage -rfakeroot -uc -us -j8 -aarmhf
>>
>> // The dpkg-buildpackage uses the settings a patches in the debian folder 
>> and builds the library as intended
>> // This commands creates Debian packages in the parent folder.
>>
>> cd ..
>> sudo dpkg -i libasound2* deb
>>
>> Regards,
>> John
>>
>>
>> This did not set the USB device to be default sound device, I used the 
>> command: aplay -L to list the nodes. From which I created the configuration 
>> file: /etc/asound.conf pcm.!default sysdefault:Device
>>
>> Again there may be easier ways, but that is what I did.  Note: I am using 
>> a USB sound adapter...
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] remove device-tree-compiler fail

[aderson . lin]

1.apt-get install device-tree-compiler  , then using dtc -v to get ver 
1.3.0-gf8cb5dd9-dirty
 
But I need device-tree-compiler ver1.4.0 or above for making uImage, then 
2.download device-tree-compiler_1.4.0+dfsg-1_amd64.deb from web site
3.Dpkg -i device-tree-compiler_1.4.0+dfsg-1_amd64.deb , then using dtc -v 
to get ver 1.3.0-gf8cb5dd9-dirty
4. I do below process, then using dtc -v to get ver 1.3.0-gf8cb5dd9-dirty
apt-get remove device-tree-compiler 
apt-get remove --auto-remove device-tree-compiler  
apt-get purge device-tree-compiler 
 apt-get purge --auto-remove device-tree-compiler  
How can I install the right DTC version?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] remove device-tree-compiler fail

[Robert Nelson]

On Thu, Apr 17, 2014 at 8:28 AM,   wrote:
> 1.apt-get install device-tree-compiler  , then using dtc -v to get ver
> 1.3.0-gf8cb5dd9-dirty
>
> But I need device-tree-compiler ver1.4.0 or above for making uImage, then
> 2.download device-tree-compiler_1.4.0+dfsg-1_amd64.deb from web site
> 3.Dpkg -i device-tree-compiler_1.4.0+dfsg-1_amd64.deb , then using dtc -v to
> get ver 1.3.0-gf8cb5dd9-dirty
> 4. I do below process, then using dtc -v to get ver 1.3.0-gf8cb5dd9-dirty
> apt-get remove device-tree-compiler
> apt-get remove --auto-remove device-tree-compiler
> apt-get purge device-tree-compiler
> apt-get purge --auto-remove device-tree-compiler
> How can I install the right DTC version?

which dtc
/usr/local/bin/dtc

probably have an older locally installed version.

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Micka]

export SLOTS=/sys/devices/bone_capemgr.9/slots

sudo echo BB-BONE-LCD7-01-00A0 > $SLOTS

[ 2058.656875] bone-capemgr bone_capemgr.9: failed to load firmware
'BB-BONE-LCD7-01--00A0.dtbo'
echo: write error: No such file or directory

where i'm wrong ?





On Thu, Apr 17, 2014 at 4:47 PM, Robert Nelson wrote:

> On Thu, Apr 17, 2014 at 9:38 AM, Micka  wrote:
> > Hi,
> >
> > My beagle received a multicast attack ( from an equipment not well
> > configured ) .
> >
> > Since then, the LCD doesn't work anymore, but when I change the BBB with
> a a
> > new one with the same SDCard, the LCD work . ... So the problem is not in
> > the LCD 7 Cap, but in the BBB.
>
> Really? I find it hard to believe those two events are linked...
>
> > But I can't find where, and why ? Gerald is it possible that the board is
> > broken electrically ?
> > Robert or someone else do you know a program that can prevent this ? or a
> > patch ? my idea is to monitor the bandwidth and stop the interface if the
> > bandwidth is used too much . .
>
> setup a firewall?
>
> > I tested this :
> >
> > export SLOTS=/sys/devices/bone_capemgr.9/slots
> > debian@beaglebone:/Distrib/Scripts$ cat $SLOTS
> >  0: 54:PF---
> >  1: 55:PF---
> >  2: 56:PF---
> >  3: 57:PF---
> >  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
> >  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
> >  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART4
> >  8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART1
> >
> > So there is no LCD7 Cap mounted 
>
> So.. What happens when you try to manually load the cape dtbo?
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Micka]

Yes those events are related, because it's the second time that I lost a
BBB when I've a "UDP attack" . Most of the time, the BBB freeze completely.


On Thu, Apr 17, 2014 at 4:47 PM, Robert Nelson wrote:

> On Thu, Apr 17, 2014 at 9:38 AM, Micka  wrote:
> > Hi,
> >
> > My beagle received a multicast attack ( from an equipment not well
> > configured ) .
> >
> > Since then, the LCD doesn't work anymore, but when I change the BBB with
> a a
> > new one with the same SDCard, the LCD work . ... So the problem is not in
> > the LCD 7 Cap, but in the BBB.
>
> Really? I find it hard to believe those two events are linked...
>
> > But I can't find where, and why ? Gerald is it possible that the board is
> > broken electrically ?
> > Robert or someone else do you know a program that can prevent this ? or a
> > patch ? my idea is to monitor the bandwidth and stop the interface if the
> > bandwidth is used too much . .
>
> setup a firewall?
>
> > I tested this :
> >
> > export SLOTS=/sys/devices/bone_capemgr.9/slots
> > debian@beaglebone:/Distrib/Scripts$ cat $SLOTS
> >  0: 54:PF---
> >  1: 55:PF---
> >  2: 56:PF---
> >  3: 57:PF---
> >  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
> >  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
> >  7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART4
> >  8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART1
> >
> > So there is no LCD7 Cap mounted 
>
> So.. What happens when you try to manually load the cape dtbo?
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Robert Nelson]

On Thu, Apr 17, 2014 at 9:59 AM, Micka  wrote:
> export SLOTS=/sys/devices/bone_capemgr.9/slots
>
> sudo echo BB-BONE-LCD7-01-00A0 > $SLOTS
>
> [ 2058.656875] bone-capemgr bone_capemgr.9: failed to load firmware
> 'BB-BONE-LCD7-01--00A0.dtbo'
> echo: write error: No such file or directory
>
> where i'm wrong ?

When there is a "version" (00A0) you need to use the ":" separator..

echo BB-BONE-LCD7-01:00A0 > $SLOTS

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Micka]

root@beaglebone:/# echo BB-BONE-LCD7-01:00A0 > $SLOTS
[ 2688.700962] bone-capemgr bone_capemgr.9: failed to load firmware
'BB-BONE-LCD7-01-00A0.dtbo'
bash: echo: write error: No such file or directory



On Thu, Apr 17, 2014 at 5:04 PM, Robert Nelson wrote:

> On Thu, Apr 17, 2014 at 9:59 AM, Micka  wrote:
> > export SLOTS=/sys/devices/bone_capemgr.9/slots
> >
> > sudo echo BB-BONE-LCD7-01-00A0 > $SLOTS
> >
> > [ 2058.656875] bone-capemgr bone_capemgr.9: failed to load firmware
> > 'BB-BONE-LCD7-01--00A0.dtbo'
> > echo: write error: No such file or directory
> >
> > where i'm wrong ?
>
> When there is a "version" (00A0) you need to use the ":" separator..
>
> echo BB-BONE-LCD7-01:00A0 > $SLOTS
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Robert Nelson]

On Thu, Apr 17, 2014 at 10:09 AM, Micka  wrote:
> root@beaglebone:/# echo BB-BONE-LCD7-01:00A0 > $SLOTS
> [ 2688.700962] bone-capemgr bone_capemgr.9: failed to load firmware
> 'BB-BONE-LCD7-01-00A0.dtbo'
> bash: echo: write error: No such file or directory

root@beaglebone:~# ls /lib/firmware/BB-BONE-LCD7*
/lib/firmware/BB-BONE-LCD7-01-00A2.dtbo
/lib/firmware/BB-BONE-LCD7-01-00A3.dtbo
/lib/firmware/BB-BONE-LCD7-01-00A4.dtbo

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Micka]

with the working BBB ( same SDCard ), I've :

export SLOTS=/sys/devices/bone_capemgr.9/slot
cat $SLOTS =>
0: 54:P---L BeagleBone LCD7 CAPE,00A3,Beagleboardtoys,BB-BONE-LCD7-01


And I just broke the broken one, no more boot, LED, ... BUt it's my fault
this time, I put the BBB not correctly on the LCD 7.


But before that, when the BBB somehow was working, it was searching
for the version
(00A0)   which was not the correct one. Because with a working BBB, the
version is A3 ...



On Thu, Apr 17, 2014 at 5:11 PM, Robert Nelson wrote:

> On Thu, Apr 17, 2014 at 10:09 AM, Micka  wrote:
> > root@beaglebone:/# echo BB-BONE-LCD7-01:00A0 > $SLOTS
> > [ 2688.700962] bone-capemgr bone_capemgr.9: failed to load firmware
> > 'BB-BONE-LCD7-01-00A0.dtbo'
> > bash: echo: write error: No such file or directory
>
> root@beaglebone:~# ls /lib/firmware/BB-BONE-LCD7*
> /lib/firmware/BB-BONE-LCD7-01-00A2.dtbo
> /lib/firmware/BB-BONE-LCD7-01-00A3.dtbo
> /lib/firmware/BB-BONE-LCD7-01-00A4.dtbo
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Robert Nelson]

On Thu, Apr 17, 2014 at 10:24 AM, Micka  wrote:
> with the working BBB ( same SDCard ), I've :
>
> export SLOTS=/sys/devices/bone_capemgr.9/slot
> cat $SLOTS =>
> 0: 54:P---L BeagleBone LCD7 CAPE,00A3,Beagleboardtoys,BB-BONE-LCD7-01
>
>
> And I just broke the broken one, no more boot, LED, ... BUt it's my fault
> this time, I put the BBB not correctly on the LCD 7.
>
>
> But before that, when the BBB somehow was working, it was searching for the
> version (00A0)   which was not the correct one. Because with a working BBB,
> the version is A3 ...

echo BB-BONE-LCD7-01:00A3 > $SLOTS

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Micka]

It's  broken I said... But one thing I'm sure. It's that the bbb don't
handle well a flood on his ethernet port.

Micka,
On Apr 17, 2014 5:25 PM, "Robert Nelson"  wrote:

> On Thu, Apr 17, 2014 at 10:24 AM, Micka  wrote:
> > with the working BBB ( same SDCard ), I've :
> >
> > export SLOTS=/sys/devices/bone_capemgr.9/slot
> > cat $SLOTS =>
> > 0: 54:P---L BeagleBone LCD7 CAPE,00A3,Beagleboardtoys,BB-BONE-LCD7-01
> >
> >
> > And I just broke the broken one, no more boot, LED, ... BUt it's my fault
> > this time, I put the BBB not correctly on the LCD 7.
> >
> >
> > But before that, when the BBB somehow was working, it was searching for
> the
> > version (00A0)   which was not the correct one. Because with a working
> BBB,
> > the version is A3 ...
>
> echo BB-BONE-LCD7-01:00A3 > $SLOTS
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UDP ATTACK => no more screen on the LCD7

[Robert Nelson]

On Thu, Apr 17, 2014 at 10:35 AM, Micka  wrote:
> It's  broken I said... But one thing I'm sure. It's that the bbb don't
> handle well a flood on his ethernet port.

Specially in 3.8... Use 3.14.x for better usb/ethernet.

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Changing PWM frequency at run time

[Strawson]

Hello all,
 
As (probably) most of you are aware, the most straightforward method of 
changing the pwm period (frequency) is at boot by setting it in a .dts 
overlay. This may be the solution for 90% of pwm users, but we have run 
into the situation where we would like to change the pwm period at run time 
to avoid re-compiling the .dts overlay when we wish to swap between 
different applications. After poking around I present our breadcrumb trail:

Start with 
*http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/drivers/pwm/pwm-tiehrpwm.c*
This is apparently near the current source tree.  There is a func() 
ehrpwm_pwm_config  that talks about setting the period and duty. 

Once compiled, it seems to end up in the beaglebone's file system here. Is 
this .ko strictly necessary if we only fix the pwm period at boot? Is this 
the real kernel module? The name implies this is not the official pwm 
driver, but perhaps it is?

*/lib/modules/3.8.13/kernel/drivers/pwm/pwm_test.ko*

There is a note that seems to point out the limitations of common clock 
sources
/*
* Period values should be same for multiple PWM channels as IP uses
* same period register for multiple channels.
*/
There is a note to allow this if and only if:
 /*
  * Allow channel to reconfigure period if no other
  * channels being configured.
  */

And if that if and only if fails it gripes
   dev_err(chip->dev, "Period value conflicts with 
channel %d\n", i);
   return -EINVAL;
 
 
The routine continues to set the channel pwm->hwpwm.  Apparently, the pwm 
chip pointed to by *pc has NUM_PWM_CHANNELs, which is 2?  A trial hack 
might be to just ignore that gripe and configure all/both channels.  For 
example,  this seems to do the actual write:
ehrpwm_write(pc->mmio_base, TBPRD, period_cycles);

But apparently, each channel has its own compare register, just a common 
clock:
if (pwm->hwpwm == 1)
   /* Channel 1 configured with compare B register */
   cmp_reg = CMPB;
else
   /* Channel 0 configured with compare A register */
   cmp_reg = CMPA;
 
ehrpwm_write(pc->mmio_base, cmp_reg, duty_cycles);
 
So, if a hack at the source is to be tried, I’d comment out the check about 
the other channel already having a differing value.  We can trust ourselves 
to work within the constraint and remember that changing Channel 1’s clock 
also changes Channel 0’s clock. Of course, even trying this requires 
recompiling the kernel OR trying to make a tiehrpwm_test .ko of our own. 
Unfortunately neither of these options are within our skill-set.

The author obviously recognized the clock dependency between the two 
channels and trapped it. But how did they expect users to deal with it? And 
who was the author? It would be nice to ask them.  The header on this file 
shows credit to Texas Instruments circa 2012 but no human names given.


There is a public workaround to allow setting of the pwm_period ONCE at 
run-time. We have successfully tested this within the 9.04 Angstrom release 
on the Beaglebone black. It requires a (included and precompiled) .ko 
kernel module which will unfortunately not load in the recent Debian 
builds.  

*https://github.com/SaadAhmad/beaglebone-black-cpp-PWM/blob/master/driver/pwm_test.c*

The driver source file at* 
https://github.com/SaadAhmad/beaglebone-black-cpp-PWM/blob/master/driver/pwm_test.c*
Includes the same Texas Instruments header as if Saad is from TI, or 
perhaps he just copied it over without changing.

He has a personal URL http://saadahmad.ca/ Well, this “explains” quite a 
bit of how he does it. He doesn’t conclude with a proposed set of changes 
to the kernel, but has built a work around.  It requires changing the the 
pwm_test.ko and setting the pwm period in the device tree to 0 at boot, 
then setting it only once at run-time.



We would like to see a (hopefully) small fix in the official TI ehrpwm 
driver that allows us to change the pwm period as frequently as we wish at 
run-time make its way into the beaglebone black build chain.

Best,
C Briggs, J Strawson

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Changing PWM frequency at run time

[robert.berger]

Hi,

On Thursday, April 17, 2014 7:48:50 PM UTC+3, Strawson wrote:
>
> Hello all,
>  
> As (probably) most of you are aware, the most straightforward method of 
> changing the pwm period (frequency) is at boot by setting it in a .dts 
> overlay. This may be the solution for 90% of pwm users, but we have run 
> into the situation where we would like to change the pwm period at run time 
> to avoid re-compiling the .dts overlay when we wish to swap between 
> different applications. 
>

How about something like this in runtime?

echo 0 > /sys/class/pwm/pwmchip1/export

cd /sys/class/pwm/pwmchip1/pwm0

1 kHz:
echo 0 > enable
echo 100 > period
echo 50 > duty_cycle
echo 1 > enable

100 Hz:
echo 0 > enable
echo 1000 > period
echo 500 > duty_cycle
echo 1 > enable

Regards,

Robert

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Custom built Debian with RealTime kernel

[Clément_C]

Hello everyone,

First, I'd like to thank you for all the support and the amazing work done 
on the BeagleBoneBlack.

I'm kind of a newbie here. Got my board for a few weeks on Angstrom. I'm an 
electronic engineering student in France and for a specific project I need 
a custom built distribution.
- The distribution needs to be minimal (no extra un-needed packages)
- I need a RealTime kernel
- I need a late kernel (the 3.8 doesn't have some kernel modules which I 
need). 3.14 for instance ?
- I need gstreamer packages and gstreamer plugin packages to ship with the 
image.
- I need to produce an image to flash the eMMC with that distro.

I have visited a lot of pages including RobertCNelson github which looks 
really active regarding BBB kernels. I successfully upgraded to Debian 
Wheezy Kernel 3.14 using this tutorial 
: http://datko.net/2014/03/21/bbb_upgrade_3_13/

Now I would need to generate my own image with specific packages and, most 
important, a real-time kernel. It seems that the Beaglebone github has a 
3.8-rt branch but no 3.14-rt branch, so I guess I have to patch a "regular" 
3.14 with RT-PREEMPT patches. 

Could someone give me some hints and how-to's for me to build such a thing ?

Thanks everyone for your support.

Clement C.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB UART2 Write Issue (C/C++)

[Alex Gal]

Hi Michael,

> I'm currently using the BBB to control a rover robot for a project at my
> university. I'm currently having an issue using the UART file /dev/ttyOx to
> write an array of characters to a smart servo using c/c++.
> More specifically, I've opened the file using
> fopen("/dev/ttyO2", "wb")
>
> which should open it in binary mode. I've also tried the c++ equivalent with
> ofstream file("/dev/ttyO2", ios::out|ios::binary)
>
> For the most part these have worked fine. I have been using the UART tool
> for the PicKit 2 to verify what I've been receiving. But, despite having
> opened the file in binary mode, if I try to write 0x0A it will still append
> 0x0D to form CRLF, or newline.
>
> For example, if I create a character array:
> char c[] = {0xFF,0xFF,0x0A,0x01,..}
>
> This is seen on the UART tool:
>  FF FF 0D 0A 01 ...
>
> If anyone knows a fix, or can offer any insight (should I be approaching it
> incorrectly), I would greatly appreciate it.

I believe you have to properly configure your serial port (baud rate,
line discipline, etc).

See this wiki page:

http://en.wikibooks.org/wiki/Serial_Programming/termios

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Official eQEP driver Support

[Strawson]

Hello all,

In an effort to make use of the eQEP modules on the beaglebone black we 
stumbled across the following encoder patch and were able to compile a 
loadable kernel module with the help of TI. Hopefully this will make its 
way to the "thirdparty" script in the debian build farm so the community 
can use this without recompiling

*https://github.com/Teknoman117/beaglebot/tree/master/encoders 
*


I would like to make known a bug we ran into with reading the eQEP module 
that resulted in position values not updating after exactly 1020 reads 
without closing the file pointer. If the file pointer is closed 
and re-opened for every read, the behavior is normal, but opening/closing 
the file is painfully slow. I unfortunately don't really know where to 
begin with finding and fixing this problem, but any insight would be 
appreciated.

Best,
J Strawson, C Briggs

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] VIO, Sitara B15 & B5 voltage levels (Gerald)

[Ross Morrison]

Hi All (Gerald),

A bit confused about the differences between the BBW and BBB Sitara 
balls B15 and B5 voltage levels. Reviewing the schematic for the BBW it 
appears PORZ (B15) is being driven from the TPS65217B pin PGOOD (26) and 
PGOOD's power supply source VIO is at 3.3v. While on the Sitara RTC_PORZ 
(B5) is being driven at 1.8 v due to the resistor divider R141 and R18. 
My understanding from reading the TRM on the Sitara is that both B15 and 
B5 are 1.8v level pins.


Now on the BBB, both B15 and B5 on the Sitara are being driven directly 
from the TPS65217C who's VIO is at 1.8v and this all makes sense.


Any help in clarifying my confusion would certainly help.

We're in the process of bringing up our new custom board based on the 
BBB and have burned up a Sitara because we pushed 3.3v into the VIO pin 
of the TPS65217C and therefore killed the Sitara via B15 and B5.


Thanks 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/d/optout.

Re: [beagleboard] Custom built Debian with RealTime kernel

[Robert Nelson]

On Thu, Apr 17, 2014 at 12:22 PM, Clément_C
 wrote:
> Hello everyone,
>
> First, I'd like to thank you for all the support and the amazing work done
> on the BeagleBoneBlack.
>
> I'm kind of a newbie here. Got my board for a few weeks on Angstrom. I'm an
> electronic engineering student in France and for a specific project I need a
> custom built distribution.
> - The distribution needs to be minimal (no extra un-needed packages)
> - I need a RealTime kernel
> - I need a late kernel (the 3.8 doesn't have some kernel modules which I
> need). 3.14 for instance ?
> - I need gstreamer packages and gstreamer plugin packages to ship with the
> image.
> - I need to produce an image to flash the eMMC with that distro.
>
> I have visited a lot of pages including RobertCNelson github which looks
> really active regarding BBB kernels. I successfully upgraded to Debian
> Wheezy Kernel 3.14 using this tutorial :
> http://datko.net/2014/03/21/bbb_upgrade_3_13/
>
> Now I would need to generate my own image with specific packages and, most
> important, a real-time kernel. It seems that the Beaglebone github has a
> 3.8-rt branch but no 3.14-rt branch, so I guess I have to patch a "regular"
> 3.14 with RT-PREEMPT patches.
>
> Could someone give me some hints and how-to's for me to build such a thing ?

This should make it easy to get started..

https://github.com/RobertCNelson/linux-dev/commit/bd69ecb7570865a29dd24fd779fa8568ffa39e5d

Just fork the linux-dev repo,

checkout the am33x-v3.14 branch and un-comment the rt line at the
bottom of patch.sh

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Official eQEP driver Support

[Robert Nelson]

On Thu, Apr 17, 2014 at 12:30 PM, Strawson  wrote:
> Hello all,
>
> In an effort to make use of the eQEP modules on the beaglebone black we
> stumbled across the following encoder patch and were able to compile a
> loadable kernel module with the help of TI. Hopefully this will make its way
> to the "thirdparty" script in the debian build farm so the community can use
> this without recompiling
>
> https://github.com/Teknoman117/beaglebot/tree/master/encoders

It looks pretty self-contained, i have no problem adding to the
current kernel patches..

> I would like to make known a bug we ran into with reading the eQEP module
> that resulted in position values not updating after exactly 1020 reads
> without closing the file pointer. If the file pointer is closed and
> re-opened for every read, the behavior is normal, but opening/closing the
> file is painfully slow. I unfortunately don't really know where to begin
> with finding and fixing this problem, but any insight would be appreciated.


yikes, it still needs a little work then..

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Change default state of GPIO pin

[kyle]

Not that I know of.  The device tree can change the pin config to default low 
but that does not take effect till boot up so there would still be several 
seconds in the HW default condition.   I just recently went through something 
similar where I had to redesign a lot of stuff on my own PCB since there are 
quite a few pins that seem to have driven states that were at odds with my 
design.  I was considering going through my existing pin-map document and 
noting the power-on (pre-device-tree) states of any pins that are driven / 
pulled one way or the other.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[macarr]

Hi William and Cody,

I have some partially good news. Using Robert's link I did successfully 
build and install v3.14.1-bone2 and I have my BBB up and running. Thanks 
for your support. BTW, watching the board boot over the serial port is jaw 
dropping-ly cool. The software checksum
 calculation speeds seems to be amazing. The arm4regs are reporting 685.2 
MB/sec. Now I'm having fun.

So now to the questions you are asking so that you can help me.

Note: The USB hub is an externally powered Belkin HS USB 2.0 hub model 
F5U233.

It is not recognized at boot time. I'll try a hot plug and look at dmesg.

No messages appended to dmesg after the hot plug. 

the /sys/bus/usb/devices file is empty.

On Thursday, April 17, 2014 7:48:42 AM UTC-7, cody wrote:
>
> Was your hub plugged in at boot or after?  I may have a workaround you can 
> try.
> If you know the hub enumerates post the contents of /sys/bus/usb/devices
>
>
> On Wed, Apr 16, 2014 at 9:59 PM, William Hermans 
> 
> > wrote:
>
>> I have no hands on with this sort of thing, but I have noticed on many 
>> occations that "we" always need to research the hardware we use on a 
>> particular Linux Distro.
>>
>> .Which kernel are you using again ? 3.8.x does not do Hotplug very well, 
>> or even at all. SO if you're hot plugging USB devices into the hub after 
>> the system is up and running, It could be that the hub may buffer you from 
>> a kernel oops, but still does not recognize the devices.
>>
>> It could also be that you need to compile a module or two into the kernel 
>> statically for the HUB to work properly. But that is just a guess on my 
>> behalf that could be wrong. I have not personally noticed anything specific 
>> to this when browsing menuconfig, but I was not looking for this sort of 
>> thing when compiling my own kernel.
>>
>> *OR* Maybe you just need a different hub . . . Perhaps someone with more 
>> experience with this sort of thing will reply and give us their 2 cents.
>>
>>
>> On Wed, Apr 16, 2014 at 7:40 PM, > wrote:
>>
>>> Hi William,
>>>
>>> Yes, I realize that the pain is self-inflicted and I want to be clear 
>>> about that. I have a favourite golfer that once said,"I'm an idiot!". I've 
>>> uttered those very words once or twice lately. Judging by the forums I 
>>> think others have said similar things.
>>>
>>> You would never believe it by my comments but in the late 1980's I was 
>>> doing this full time on a RT VME chassis running UniFlex (Unix variant). I 
>>> wrote drivers in C and 68030 assembly language and did some very neat 
>>> stuff. The learning curve was steep back then too. Ah, but I was young! 
>>> Time didn't matter...So I had to see what the kids are getting into these 
>>> days.
>>>
>>> I am actually more concerned with another issue regarding attaching a 
>>> USB hub to the USB host on the BBB. After I've done that the system won't 
>>> enumerate any of the devices I've put into the hub. But according to dmesg 
>>> the hub itself was successfully installed.
>>>
>>> Ideas?
>>>
>>>
>>>
>>> On Monday, April 14, 2014 3:24:04 PM UTC-7, William Hermans wrote:

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

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

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

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

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


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

> Yes Robert,
>
> You are correct on all counts. I was unaware of the 
> http://eewiki.net/display/linuxonarm/BeagleBone+Black.
>  I performed a google search and found the first site I mentioned.
>
> Being "new" can be a painful process. Not working on a staff with 
> others to learn from is even more painful.
>
> The biggest obstacle is that "you don't know what you don't know". 
>
> Again, I thank you for your efforts. I will be persistent.
>
> Respectfully,
>
>  -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google 
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, 

[beagleboard] Problem: Less eMMC Memory 2GB on BBB :( plz Help TY!

[Divyang Jain]

only 50 MB of space Left on My EMMC, I want to Install My Drivers and 
applications in my External memory card.How can i do that?

# I boot from EMMC, 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Official eQEP driver Support

[William Hermans]

Strawson, best thing I personally can think of, would be to use two or more
pointers to the same file, and rotate between them. Closing one down while
the other continues operating.


On Thu, Apr 17, 2014 at 11:09 AM, Robert Nelson wrote:

> On Thu, Apr 17, 2014 at 12:30 PM, Strawson  wrote:
> > Hello all,
> >
> > In an effort to make use of the eQEP modules on the beaglebone black we
> > stumbled across the following encoder patch and were able to compile a
> > loadable kernel module with the help of TI. Hopefully this will make its
> way
> > to the "thirdparty" script in the debian build farm so the community can
> use
> > this without recompiling
> >
> > https://github.com/Teknoman117/beaglebot/tree/master/encoders
>
> It looks pretty self-contained, i have no problem adding to the
> current kernel patches..
>
> > I would like to make known a bug we ran into with reading the eQEP module
> > that resulted in position values not updating after exactly 1020 reads
> > without closing the file pointer. If the file pointer is closed and
> > re-opened for every read, the behavior is normal, but opening/closing the
> > file is painfully slow. I unfortunately don't really know where to begin
> > with finding and fixing this problem, but any insight would be
> appreciated.
>
>
> yikes, it still needs a little work then..
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[William Hermans]

Serial boot ? I have not done that yet, Id like to read a write up of that
if you wrote one. e.g. I have no hands on with serial booting, and perhaps
would like to know how.


On Thu, Apr 17, 2014 at 11:45 AM,  wrote:

> Hi William and Cody,
>
> I have some partially good news. Using Robert's link I did successfully
> build and install v3.14.1-bone2 and I have my BBB up and running. Thanks
> for your support. BTW, watching the board boot over the serial port is jaw
> dropping-ly cool. The software checksum
>  calculation speeds seems to be amazing. The arm4regs are reporting 685.2
> MB/sec. Now I'm having fun.
>
> So now to the questions you are asking so that you can help me.
>
> Note: The USB hub is an externally powered Belkin HS USB 2.0 hub model
> F5U233.
>
> It is not recognized at boot time. I'll try a hot plug and look at dmesg.
>
> No messages appended to dmesg after the hot plug.
>
> the /sys/bus/usb/devices file is empty.
>
>
> On Thursday, April 17, 2014 7:48:42 AM UTC-7, cody wrote:
>
>> Was your hub plugged in at boot or after?  I may have a workaround you
>> can try.
>> If you know the hub enumerates post the contents of /sys/bus/usb/devices
>>
>>
>> On Wed, Apr 16, 2014 at 9:59 PM, William Hermans wrote:
>>
>>> I have no hands on with this sort of thing, but I have noticed on many
>>> occations that "we" always need to research the hardware we use on a
>>> particular Linux Distro.
>>>
>>> .Which kernel are you using again ? 3.8.x does not do Hotplug very well,
>>> or even at all. SO if you're hot plugging USB devices into the hub after
>>> the system is up and running, It could be that the hub may buffer you from
>>> a kernel oops, but still does not recognize the devices.
>>>
>>> It could also be that you need to compile a module or two into the
>>> kernel statically for the HUB to work properly. But that is just a guess on
>>> my behalf that could be wrong. I have not personally noticed anything
>>> specific to this when browsing menuconfig, but I was not looking for this
>>> sort of thing when compiling my own kernel.
>>>
>>> *OR* Maybe you just need a different hub . . . Perhaps someone with more
>>> experience with this sort of thing will reply and give us their 2 cents.
>>>
>>>
>>> On Wed, Apr 16, 2014 at 7:40 PM,  wrote:
>>>
 Hi William,

 Yes, I realize that the pain is self-inflicted and I want to be clear
 about that. I have a favourite golfer that once said,"I'm an idiot!". I've
 uttered those very words once or twice lately. Judging by the forums I
 think others have said similar things.

 You would never believe it by my comments but in the late 1980's I was
 doing this full time on a RT VME chassis running UniFlex (Unix variant). I
 wrote drivers in C and 68030 assembly language and did some very neat
 stuff. The learning curve was steep back then too. Ah, but I was young!
 Time didn't matter...So I had to see what the kids are getting into these
 days.

 I am actually more concerned with another issue regarding attaching a
 USB hub to the USB host on the BBB. After I've done that the system won't
 enumerate any of the devices I've put into the hub. But according to dmesg
 the hub itself was successfully installed.

 Ideas?



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

[beagleboard] Robot language BBB software/hardware question

[StillWatter]

Hi all

I'm new to the board. I have purchased a BBB that will be here in a few 
weeks and would like some advice.I've searched  for a few days but seem to 
be going in circles because i'm just not clear on the interface so please 
forgive me if this is a commonly asked question.

I'm building a robot with some wheelchair motors coupled to an existing 
sabertooth 2x25. The Sabertooth (has a 5v output)  will power the BBB 
board, i'd also like to have wireless access to the robot and would like to 
know:

1) What is the most user friendly software interface I can use/practice 
with to get familiar with while I wait on the board? I've used some Linux 
and enjoy it (installed a few distros: mint, ubuntu, MCE) but this is 
mostly due to some great walkthrough tutorials. I've not found great 
tutorials yet for BBB. As an add on to this, when I install one of the 
available distro's, are there commands in place or something like that from 
a list or something similar? I'm not a programmer.

2) Robot functions aren't exotic: follow a set path outside up to 100 yards 
(without a line) at a certain time and the ability to send rf signals. I 
figure I need the following hardware capes: Bluetooth, RF, clock. Any 
advice on which of these to get would be great. If it were a perfect world 
I would figure out how to make the robot recharge.

3) Also, what other forum resources are out there that you would recommend?

Any assistance would really be appreciated.

regards
SW

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Help me running my first Hello word application on beagle board

[salman khalid]

First Login to your BB via ssh terminal (only if you have connected your BB 
with the network)

ssh BB-ipaddress

if you have successfully logged in then open up another terminal and use 
scp to transfer your binary to BB

scp /path/to/binary/on/host/pc root@BB-ipaddress:~/
this will copy binary to root user home directory

you can run it by 
./binary_name

On Friday, April 4, 2014 11:49:15 AM UTC+5, utnay...@gmail.com wrote:
>
>
> Hi friends i am using Beagle Board for the first tym and am new to the 
> Linux environment, i am using Eclipse C/C++ IDE and am using MinGW cross 
> compiler tool chain, i have successfully compiled the example hello word 
> application using cross GCC, but after that i am completely lost, i have 
> the project files, i have completely setup beagle board for angstrom 
> environment but kindly guide me through further steps that i need to know.  
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] VIO, Sitara B15 & B5 voltage levels (Gerald)

[Ross Morrison]

Never mind again. After digging deeper into the TRM and referring to 
note 11 for VDDSHV6 (page 42), that power supply can be 3.3v and 
therefore B15 is happy at 3.3v. On the other hand RTC_PORZ can only be 
at 1.8 (VDDS_RTC). I understand fully now and the confusion between the 
BBW and BBB is gone.


Again, thank you Gerald and team for all the great work.

Ross



On 04/17/2014 10:31 AM, Ross Morrison wrote:

Hi All (Gerald),

A bit confused about the differences between the BBW and BBB Sitara 
balls B15 and B5 voltage levels. Reviewing the schematic for the BBW 
it appears PORZ (B15) is being driven from the TPS65217B pin PGOOD 
(26) and PGOOD's power supply source VIO is at 3.3v. While on the 
Sitara RTC_PORZ (B5) is being driven at 1.8 v due to the resistor 
divider R141 and R18. My understanding from reading the TRM on the 
Sitara is that both B15 and B5 are 1.8v level pins.


Now on the BBB, both B15 and B5 on the Sitara are being driven 
directly from the TPS65217C who's VIO is at 1.8v and this all makes 
sense.


Any help in clarifying my confusion would certainly help.

We're in the process of bringing up our new custom board based on the 
BBB and have burned up a Sitara because we pushed 3.3v into the VIO 
pin of the TPS65217C and therefore killed the Sitara via B15 and B5.


Thanks 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/d/optout.

[beagleboard] Angstrom freezing on boot

[João Paulo]

Hi,

Suddenly my bealgebone stop booting.
The log message is:

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[1.156059] omap_i2c 44e0b000.i2c: controller timed out
[1.156104] tps65217 0-0024: Failed to read INT reg
[1.156123] tps65217 0-0024: Failed to probe pwr_but
[2.156056] omap_i2c 44e0b000.i2c: controller timed out
[3.159960] omap_i2c 44e0b000.i2c: controller timed out
[3.192906] omap2_mbox_probe: platform not supported
[4.262857] omap_i2c 44e0b000.i2c: controller timed out
[5.272375] omap_i2c 44e0b000.i2c: controller timed out
[6.786039] omap_i2c 44e0b000.i2c: controller timed out
[7.797989] omap_i2c 44e0b000.i2c: controller timed out
[9.311445] omap_i2c 44e0b000.i2c: controller timed out
[   10.323312] omap_i2c 44e0b000.i2c: controller timed out
[   11.836824] omap_i2c 44e0b000.i2c: controller timed out
[   12.848568] omap_i2c 44e0b000.i2c: controller timed out
[   14.362226] omap_i2c 44e0b000.i2c: controller timed out
[   15.373935] omap_i2c 44e0b000.i2c: controller timed out
[   16.887705] omap_i2c 44e0b000.i2c: controller timed out
[   17.899350] omap_i2c 44e0b000.i2c: controller timed out
[   19.413079] omap_i2c 44e0b000.i2c: controller timed out
[   20.424713] omap_i2c 44e0b000.i2c: controller timed out
[   21.938389] omap_i2c 44e0b000.i2c: controller timed out
[   22.950188] omap_i2c 44e0b000.i2c: controller timed out
[   24.463792] omap_i2c 44e0b000.i2c: controller timed out
[   25.475572] omap_i2c 44e0b000.i2c: controller timed out
[   26.989170] omap_i2c 44e0b000.i2c: controller timed out
[   28.000916] omap_i2c 44e0b000.i2c: controller timed out
[   28.514549] bone-capemgr bone_capemgr.8: Failed to scan baseboard eeprom
[   28.539322] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' 
failed
[   28.575588] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[   28.587309] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status 
-22
[   28.594619] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
device pinctrl-single
[   28.672322] cpufreq_cpu0: failed to scale voltage up: -22
[   28.678238] cpufreq_cpu0: failed to scale voltage up: -22
[   28.971626] hub 1-0:1.0: unable to enumerate USB device on port 1


I dont have any device connected in the USB.

any idea?

Thanks

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[macarr]

Hi William,

I boot the BBB from the SD card but I purchased the Adafruit debugging 
cablehttp://www.adafruit.com/products/954.At
 first I was using Win7(64) and downloaded a copy of Putty for uSoft. The 
default settings for the BBB serial port is 115.2 Kb, 8 data bits,no 
parity, 1 stop bit and no handshaking. In putty create/load/save a profile 
for the serial port you are connected to. You can see which one by looking 
in control panel device manager serial ports. The com port you need will be 
connected to a Prolific USB to Serial bridge.

The physical connections from the cable to the BBB are

BBB   WireFunction
Pin 1  Black  Signal Ground
Pin 4  Green  Receive
Pin 5  White  Transmit

I did the same thing in Ubuntu but the serial port is /dev/ttyUSB0 with the 
port configuration settings the same. In Ubuntu, from a terminal enter sudo 
putty prior to starting the BBB. 

It's a must have setup to debug u-boot and capture the kernel boot. U-boot 
is a piece of work all to itself. But if you know how to use it you can 
back drive the information you get from it to the area in uEnv.txt and the 
boot loader. Once the kernel is started the kernel messages reflect what 
you can get from dmesg after you log into the BBB. Yes it is very 
interesting and exciting/fun.

I keep the serial cable connected all the time and my other work is done 
through the network connections. I use tightvncserver on the BBB and 
tightvncviwer on the pc for a remote desktop session or Cloud-9 from google 
chrome as advertised on BB website.

Hope I helped.

Mike

On Thursday, April 17, 2014 11:54:04 AM UTC-7, William Hermans wrote:
>
> Serial boot ? I have not done that yet, Id like to read a write up of that 
> if you wrote one. e.g. I have no hands on with serial booting, and perhaps 
> would like to know how.
>
>
> On Thu, Apr 17, 2014 at 11:45 AM, > wrote:
>
>> Hi William and Cody,
>>
>> I have some partially good news. Using Robert's link I did successfully 
>> build and install v3.14.1-bone2 and I have my BBB up and running. Thanks 
>> for your support. BTW, watching the board boot over the serial port is jaw 
>> dropping-ly cool. The software checksum
>>  calculation speeds seems to be amazing. The arm4regs are reporting 685.2 
>> MB/sec. Now I'm having fun.
>>
>> So now to the questions you are asking so that you can help me.
>>
>> Note: The USB hub is an externally powered Belkin HS USB 2.0 hub model 
>> F5U233.
>>
>> It is not recognized at boot time. I'll try a hot plug and look at dmesg.
>>
>> No messages appended to dmesg after the hot plug. 
>>
>> the /sys/bus/usb/devices file is empty.
>>
>>
>> On Thursday, April 17, 2014 7:48:42 AM UTC-7, cody wrote:
>>
>>> Was your hub plugged in at boot or after?  I may have a workaround you 
>>> can try.
>>> If you know the hub enumerates post the contents of /sys/bus/usb/devices
>>>
>>>
>>> On Wed, Apr 16, 2014 at 9:59 PM, William Hermans wrote:
>>>
  I have no hands on with this sort of thing, but I have noticed on 
 many occations that "we" always need to research the hardware we use on a 
 particular Linux Distro.

 .Which kernel are you using again ? 3.8.x does not do Hotplug very 
 well, or even at all. SO if you're hot plugging USB devices into the hub 
 after the system is up and running, It could be that the hub may buffer 
 you 
 from a kernel oops, but still does not recognize the devices.

 It could also be that you need to compile a module or two into the 
 kernel statically for the HUB to work properly. But that is just a guess 
 on 
 my behalf that could be wrong. I have not personally noticed anything 
 specific to this when browsing menuconfig, but I was not looking for this 
 sort of thing when compiling my own kernel.

 *OR* Maybe you just need a different hub . . . Perhaps someone with 
 more experience with this sort of thing will reply and give us their 2 
 cents.


 On Wed, Apr 16, 2014 at 7:40 PM,  wrote:

> Hi William,
>
> Yes, I realize that the pain is self-inflicted and I want to be clear 
> about that. I have a favourite golfer that once said,"I'm an idiot!". 
> I've 
> uttered those very words once or twice lately. Judging by the forums I 
> think others have said similar things.
>
> You would never believe it by my comments but in the late 1980's I was 
> doing this full time on a RT VME chassis running UniFlex (Unix variant). 
> I 
> wrote drivers in C and 68030 assembly language and did some very neat 
> stuff. The learning curve was steep back then too. Ah, but I was young! 
> Time didn't matter...So I had to see what the kids are getting into these 
> days.
>
> I am actually more concerned with another issue regarding attaching a 
> USB hub to the USB host on the BBB. After I've done that the system won't 

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

[macarr]

Hi Cody,

I posted this to both you and William but in a different post.

 Note: The USB hub is an externally powered Belkin HS USB 2.0 hub model 
F5U233.

It is not recognized at boot time. I'll try a hot plug and look at dmesg.

No messages appended to dmesg after the hot plug. 

the /sys/bus/usb/devices file is empty.

I appreciate your help.

Mike

On Thursday, April 17, 2014 7:48:42 AM UTC-7, cody wrote:
>
> Was your hub plugged in at boot or after?  I may have a workaround you can 
> try.
> If you know the hub enumerates post the contents of /sys/bus/usb/devices
>
>
> On Wed, Apr 16, 2014 at 9:59 PM, William Hermans 
> 
> > wrote:
>
>> I have no hands on with this sort of thing, but I have noticed on many 
>> occations that "we" always need to research the hardware we use on a 
>> particular Linux Distro.
>>
>> .Which kernel are you using again ? 3.8.x does not do Hotplug very well, 
>> or even at all. SO if you're hot plugging USB devices into the hub after 
>> the system is up and running, It could be that the hub may buffer you from 
>> a kernel oops, but still does not recognize the devices.
>>
>> It could also be that you need to compile a module or two into the kernel 
>> statically for the HUB to work properly. But that is just a guess on my 
>> behalf that could be wrong. I have not personally noticed anything specific 
>> to this when browsing menuconfig, but I was not looking for this sort of 
>> thing when compiling my own kernel.
>>
>> *OR* Maybe you just need a different hub . . . Perhaps someone with more 
>> experience with this sort of thing will reply and give us their 2 cents.
>>
>>
>> On Wed, Apr 16, 2014 at 7:40 PM, > wrote:
>>
>>> Hi William,
>>>
>>> Yes, I realize that the pain is self-inflicted and I want to be clear 
>>> about that. I have a favourite golfer that once said,"I'm an idiot!". I've 
>>> uttered those very words once or twice lately. Judging by the forums I 
>>> think others have said similar things.
>>>
>>> You would never believe it by my comments but in the late 1980's I was 
>>> doing this full time on a RT VME chassis running UniFlex (Unix variant). I 
>>> wrote drivers in C and 68030 assembly language and did some very neat 
>>> stuff. The learning curve was steep back then too. Ah, but I was young! 
>>> Time didn't matter...So I had to see what the kids are getting into these 
>>> days.
>>>
>>> I am actually more concerned with another issue regarding attaching a 
>>> USB hub to the USB host on the BBB. After I've done that the system won't 
>>> enumerate any of the devices I've put into the hub. But according to dmesg 
>>> the hub itself was successfully installed.
>>>
>>> Ideas?
>>>
>>>
>>>
>>> On Monday, April 14, 2014 3:24:04 PM UTC-7, William Hermans wrote:

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

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

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

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

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


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

> Yes Robert,
>
> You are correct on all counts. I was unaware of the 
> http://eewiki.net/display/linuxonarm/BeagleBone+Black.
>  I performed a google search and found the first site I mentioned.
>
> Being "new" can be a painful process. Not working on a staff with 
> others to learn from is even more painful.
>
> The biggest obstacle is that "you don't know what you don't know". 
>
> Again, I thank you for your efforts. I will be persistent.
>
> Respectfully,
>
>  -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google 
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to beagleboard...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

  -- 
>>> For more options, visit http://beagleboard.org/discuss
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this gro

Re: [beagleboard] Change default state of GPIO pin

[Guy Grotke]

Is it high (IE. driven) or is it just floating?  To quote the TI Technical 
Reference: “At reset, all the GPIO related pins are configured as input and 
output capabilities are disabled.”  Unless the boot process or some program 
sets your pin up as an output, then it would just float in a high impedance 
state until your device tree stuff says otherwise.  Does your peripheral device 
make that loud beep if it is powered but disconnected from P9.12?

If so, then you could change your circuit so it needs to be actively driven or 
sunk with a maximum of about 4 ma.  (To stay within the current limits of a 
GPIO pin.)  That could be as simple as adding a weak pulldown resistor.  I 
would start with a 10K and watch with a scope during startup to see if it ever 
is driven high.

You need to understand the current and voltage characteristics of anything you 
attach to a GPIO pin because you can burn up a GPIO (or even the whole chip) 
just by trying to drive an LED without a transistor or IC buffer.

From: het.oos...@gmail.com 
Sent: Thursday, April 17, 2014 2:19 AM
To: beagleboard@googlegroups.com 
Subject: [beagleboard] Change default state of GPIO pin

I have a beeper which is controlled by GPIO P9.12. The problem is that the 
default state of this pin is high (I think this is the problem). So I have a 
long and annoying beep when the BBB boots. This stops when my programm is 
loaded, then everything works as it should. 

Is there a way to set the default state of this pin to low?

Regards,

Rob

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Custom built Debian with RealTime kernel

[Clément_C]

Thanks very much Robert !

I've forked your repo on https://github.com/GunMan-fr/linux-dev
and uncommented the rt line in patch.sh .

Then I built the kernel using build_kernel.sh and everything worked 
perfectly :) !

Now I was trying to build a debian image with build_deb.sh and it fails 
everytime.

I get a huge lot of this error :

ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
preloaded: ignored.

and the process finally crashes with this error :

ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be 
preloaded: ignored.
make[1]: *** [deb-pkg] Error 2
make: *** [deb-pkg] Error 2

Maybe I forgot to do something ?

Thanks very much for your help.

Clément.






Le jeudi 17 avril 2014 19:35:36 UTC+2, RobertCNelson a écrit :
>
> On Thu, Apr 17, 2014 at 12:22 PM, Clément_C 
> > wrote: 
> > Hello everyone, 
> > 
> > First, I'd like to thank you for all the support and the amazing work 
> done 
> > on the BeagleBoneBlack. 
> > 
> > I'm kind of a newbie here. Got my board for a few weeks on Angstrom. I'm 
> an 
> > electronic engineering student in France and for a specific project I 
> need a 
> > custom built distribution. 
> > - The distribution needs to be minimal (no extra un-needed packages) 
> > - I need a RealTime kernel 
> > - I need a late kernel (the 3.8 doesn't have some kernel modules which I 
> > need). 3.14 for instance ? 
> > - I need gstreamer packages and gstreamer plugin packages to ship with 
> the 
> > image. 
> > - I need to produce an image to flash the eMMC with that distro. 
> > 
> > I have visited a lot of pages including RobertCNelson github which looks 
> > really active regarding BBB kernels. I successfully upgraded to Debian 
> > Wheezy Kernel 3.14 using this tutorial : 
> > http://datko.net/2014/03/21/bbb_upgrade_3_13/ 
> > 
> > Now I would need to generate my own image with specific packages and, 
> most 
> > important, a real-time kernel. It seems that the Beaglebone github has a 
> > 3.8-rt branch but no 3.14-rt branch, so I guess I have to patch a 
> "regular" 
> > 3.14 with RT-PREEMPT patches. 
> > 
> > Could someone give me some hints and how-to's for me to build such a 
> thing ? 
>
> This should make it easy to get started.. 
>
>
> https://github.com/RobertCNelson/linux-dev/commit/bd69ecb7570865a29dd24fd779fa8568ffa39e5d
>  
>
> Just fork the linux-dev repo, 
>
> checkout the am33x-v3.14 branch and un-comment the rt line at the 
> bottom of patch.sh 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Custom built Debian with RealTime kernel

[Robert Nelson]

On Thu, Apr 17, 2014 at 6:05 PM, Clément_C
 wrote:
> Thanks very much Robert !
>
> I've forked your repo on https://github.com/GunMan-fr/linux-dev
> and uncommented the rt line in patch.sh .
>
> Then I built the kernel using build_kernel.sh and everything worked
> perfectly :) !
>
> Now I was trying to build a debian image with build_deb.sh and it fails
> everytime.
>
> I get a huge lot of this error :
>
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be
> preloaded: ignored.
>
> and the process finally crashes with this error :
>
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be
> preloaded: ignored.

this error is fine.. just a 64bit system using 32bit gcc cross compiler..

> make[1]: *** [deb-pkg] Error 2
> make: *** [deb-pkg] Error 2
>
> Maybe I forgot to do something ?

This shouldn't happen..

But... I hardly ever test the cross "deb" just run:

./build_kernel.sh
(insert debian microSD card into host pc)
./tools/install_kernel.sh

(insert microSD into bbb)

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Angstrom freezing on boot

[Robert Nelson]

On Thu, Apr 17, 2014 at 4:50 PM, João Paulo  wrote:
> Hi,
>
> Suddenly my bealgebone stop booting.
> The log message is:
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
> [1.156059] omap_i2c 44e0b000.i2c: controller timed out
> [1.156104] tps65217 0-0024: Failed to read INT reg
> [1.156123] tps65217 0-0024: Failed to probe pwr_but
> [2.156056] omap_i2c 44e0b000.i2c: controller timed out
> [3.159960] omap_i2c 44e0b000.i2c: controller timed out
> [3.192906] omap2_mbox_probe: platform not supported
> [4.262857] omap_i2c 44e0b000.i2c: controller timed out
> [5.272375] omap_i2c 44e0b000.i2c: controller timed out
> [6.786039] omap_i2c 44e0b000.i2c: controller timed out
> [7.797989] omap_i2c 44e0b000.i2c: controller timed out
> [9.311445] omap_i2c 44e0b000.i2c: controller timed out
> [   10.323312] omap_i2c 44e0b000.i2c: controller timed out
> [   11.836824] omap_i2c 44e0b000.i2c: controller timed out
> [   12.848568] omap_i2c 44e0b000.i2c: controller timed out
> [   14.362226] omap_i2c 44e0b000.i2c: controller timed out
> [   15.373935] omap_i2c 44e0b000.i2c: controller timed out
> [   16.887705] omap_i2c 44e0b000.i2c: controller timed out
> [   17.899350] omap_i2c 44e0b000.i2c: controller timed out
> [   19.413079] omap_i2c 44e0b000.i2c: controller timed out
> [   20.424713] omap_i2c 44e0b000.i2c: controller timed out
> [   21.938389] omap_i2c 44e0b000.i2c: controller timed out
> [   22.950188] omap_i2c 44e0b000.i2c: controller timed out
> [   24.463792] omap_i2c 44e0b000.i2c: controller timed out
> [   25.475572] omap_i2c 44e0b000.i2c: controller timed out
> [   26.989170] omap_i2c 44e0b000.i2c: controller timed out
> [   28.000916] omap_i2c 44e0b000.i2c: controller timed out
> [   28.514549] bone-capemgr bone_capemgr.8: Failed to scan baseboard eeprom
> [   28.539322] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset'
> failed
> [   28.575588] pinctrl-single 44e10800.pinmux: pin 44e10854 already
> requested by 44e10800.pinmux; cannot claim for gpio-leds.7
> [   28.587309] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status
> -22
> [   28.594619] pinctrl-single 44e10800.pinmux: could not request pin 21 on
> device pinctrl-single
> [   28.672322] cpufreq_cpu0: failed to scale voltage up: -22
> [   28.678238] cpufreq_cpu0: failed to scale voltage up: -22
> [   28.971626] hub 1-0:1.0: unable to enumerate USB device on port 1
>
>
> I dont have any device connected in the USB.

I'm left to wonder what you were doing right before it "failed".. It
looks like the i2c bus is at-least shorting out..

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Custom built Debian with RealTime kernel

[Charles Steinkuehler]

On 4/17/2014 12:35 PM, Robert Nelson wrote:
> This should make it easy to get started..
> 
> https://github.com/RobertCNelson/linux-dev/commit/bd69ecb7570865a29dd24fd779fa8568ffa39e5d
> 
> Just fork the linux-dev repo,
> 
> checkout the am33x-v3.14 branch and un-comment the rt line at the
> bottom of patch.sh

Nice one, Robert!

Is that kernel stable?  Depending on the latency figures, it may work
for the Machinekit images I'm doing, which would mean no waiting for
Xenomai to make a 3.12/3.14 patch set.

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Custom built Debian with RealTime kernel

[Robert Nelson]

On Thu, Apr 17, 2014 at 6:40 PM, Charles Steinkuehler
 wrote:
> On 4/17/2014 12:35 PM, Robert Nelson wrote:
>> This should make it easy to get started..
>>
>> https://github.com/RobertCNelson/linux-dev/commit/bd69ecb7570865a29dd24fd779fa8568ffa39e5d
>>
>> Just fork the linux-dev repo,
>>
>> checkout the am33x-v3.14 branch and un-comment the rt line at the
>> bottom of patch.sh
>
> Nice one, Robert!
>
> Is that kernel stable?  Depending on the latency figures, it may work
> for the Machinekit images I'm doing, which would mean no waiting for
> Xenomai to make a 3.12/3.14 patch set.

I'm not even sure if the rt-patchset will still boot.  But with how
small our v3.14.x patchset is, it's atleast worth a test.

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Angstrom freezing on boot

[João Paulo]

I flashed the board and the problem persist. I dont have any board attached 
it.

The boot loader appear some problems related to the i2c:

-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
timed out in wait_for_pin: I2C_STAT=0
Could not probe the EEPROM; something fundamentally wrong on the I2C bus.
Could not get board ID.
Unknown board, assuming Beaglebone LT/Black.musb-hdrc: ConfigData=0xde 
(UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0 
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, 
SoftConn)
musb-hdrc: MHDRC RTL version 2.0 
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)

I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
timed out in wait_for_pin: I2C_STAT=0
Could not probe the EEPROM; something fundamentally wrong on the I2C bus.
Could not get board ID.
NAND:  No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1


Any ideia?

Regards

On Thursday, April 17, 2014 6:50:50 PM UTC-3, João Paulo wrote:
>
> Hi,
>
> Suddenly my bealgebone stop booting.
> The log message is:
>
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
> [1.156059] omap_i2c 44e0b000.i2c: controller timed out
> [1.156104] tps65217 0-0024: Failed to read INT reg
> [1.156123] tps65217 0-0024: Failed to probe pwr_but
> [2.156056] omap_i2c 44e0b000.i2c: controller timed out
> [3.159960] omap_i2c 44e0b000.i2c: controller timed out
> [3.192906] omap2_mbox_probe: platform not supported
> [4.262857] omap_i2c 44e0b000.i2c: controller timed out
> [5.272375] omap_i2c 44e0b000.i2c: controller timed out
> [6.786039] omap_i2c 44e0b000.i2c: controller timed out
> [7.797989] omap_i2c 44e0b000.i2c: controller timed out
> [9.311445] omap_i2c 44e0b000.i2c: controller timed out
> [   10.323312] omap_i2c 44e0b000.i2c: controller timed out
> [   11.836824] omap_i2c 44e0b000.i2c: controller timed out
> [   12.848568] omap_i2c 44e0b000.i2c: controller timed out
> [   14.362226] omap_i2c 44e0b000.i2c: controller timed out
> [   15.373935] omap_i2c 44e0b000.i2c: controller timed out
> [   16.887705] omap_i2c 44e0b000.i2c: controller timed out
> [   17.899350] omap_i2c 44e0b000.i2c: controller timed out
> [   19.413079] omap_i2c 44e0b000.i2c: controller timed out
> [   20.424713] omap_i2c 44e0b000.i2c: controller timed out
> [   21.938389] omap_i2c 44e0b000.i2c: controller timed out
> [   22.950188] omap_i2c 44e0b000.i2c: controller timed out
> [   24.463792] omap_i2c 44e0b000.i2c: controller timed out
> [   25.475572] omap_i2c 44e0b000.i2c: controller timed out
> [   26.989170] omap_i2c 44e0b000.i2c: controller timed out
> [   28.000916] omap_i2c 44e0b000.i2c: controller timed out
> [   28.514549] bone-capemgr bone_capemgr.8: Failed to scan baseboard eeprom
> [   28.539322] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' 
> failed
> [   28.575588] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
> requested by 44e10800.pinmux; cannot claim for gpio-leds.7
> [   28.587309] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status 
> -22
> [   28.594619] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
> device pinctrl-single
> [   28.672322] cpufreq_cpu0: failed to scale voltage up: -22
> [   28.678238] cpufreq_cpu0: failed to scale voltage up: -22
> [   28.971626] hub 1-0:1.0: unable to enumerate USB device on port 1
>
>
> I dont have any device connected in the USB.
>
> any idea?
>
> Thanks
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] ome problem when I get update

[Yanlong Mu]

Dear William

Thank you so much for your help

I just confusing one thing which are couple of sentences:
(

All of these steps will be described in more detail below. All of the
options below also require the same set of materials.

   - BeagleBone Black
   - Display to connect BeagleBone Black to
   - Mouse and Keyboard (as well as a USB hub if they have separate
   dongles/cables)
   - Micro SD card 4 GB or more in size (8 GB is recommended but not
   neccessary)
   - Ethernet cable with working connection
   - Separate computer with internet connection to download and flash an
   image to micro SD

)

These from
http://elinux.org/Beagleboard:Desktops_On_Ubuntu/Debian#Ubuntu_Precise_On_A_microSD_With_Ubuntu_Desktop

My project is about to achieve the Object or facial detection and tracking
with Pan/Tilt using OpenCV

If I would like to make it, should I prepare those equipment as shown as
above (mouse, display, keyboard and powered usb hub)?

If it is yes, how to connect with Beaglebone Black, cause as we know about
the feature of it, it just has a little HDMI connect plug can be used.
Using the transfer or similar like that?

Thank your patient

I am really looking forward your reply

Your sincerely

Yanlong Mu(Ian)


On Thu, Apr 17, 2014 at 6:14 AM, William Hermans  wrote:

> *dpkg-reconfigure locales *as root, or using sudo. Assuming the package
> is installed properly.
>
>
> On Wed, Apr 16, 2014 at 9:56 PM, Sungjin Chun wrote:
>
>> Did you generate locale data? For example, in arch linux (which I'm
>> using),
>> after configuration of /etc/locale.conf I should execute
>>
>> locale-gen
>>
>> so that configured locale data be generated.
>>
>>
>>
>> On Thu, Apr 17, 2014 at 12:57 PM, Yanlong Mu  wrote:
>>
>>> Hi Everybody
>>>
>>> I just get the new image boot on the BBB 12.04.2 LTS
>>>
>>> When I put the sudo apt-get update and upgrade, it showed some warning
>>> as below
>>>
>>> locale: Cannot set LC_CTYPE to default locale: No such file or directory
>>> locale: Cannot set LC_MESSAGES to default locale: No such file or
>>> directory
>>> locale: Cannot set LC_ALL to default locale: No such file or directory
>>>
>>>
>>> And When I was going to install a desktops (xface)
>>>
>>> it showed
>>>
>>> perl: warning: Falling back to the standard locale ("C").
>>> perl: warning: Setting locale failed.
>>> perl: warning: Please check that your locale settings:
>>> LANGUAGE = (unset),
>>> LC_ALL = (unset),
>>> LC_TIME = "en_GB.UTF-8",
>>> LC_MONETARY = "en_GB.UTF-8",
>>> LC_ADDRESS = "en_GB.UTF-8",
>>> LC_TELEPHONE = "en_GB.UTF-8",
>>> LC_NAME = "en_GB.UTF-8",
>>> LC_MEASUREMENT = "en_GB.UTF-8",
>>> LC_IDENTIFICATION = "en_GB.UTF-8",
>>> LC_NUMERIC = "en_GB.UTF-8",
>>> LC_PAPER = "en_GB.UTF-8",
>>> LANG = "en_GB.UTF-8"
>>> perl: warning: Falling back to the standard locale ("C").
>>>
>>> Anyone can help me to solve that problem?
>>>
>>> Kind Regards
>>>
>>> Ian
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/ufeNqBNCnqs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] ome problem when I get update

[Yanlong Mu]

Dear Sungjin

Thank you so much for your help

I just confusing one thing which are couple of sentences:
(

All of these steps will be described in more detail below. All of the
options below also require the same set of materials.

   - BeagleBone Black
   - Display to connect BeagleBone Black to
   - Mouse and Keyboard (as well as a USB hub if they have separate
   dongles/cables)
   - Micro SD card 4 GB or more in size (8 GB is recommended but not
   neccessary)
   - Ethernet cable with working connection
   - Separate computer with internet connection to download and flash an
   image to micro SD

)

These from
http://elinux.org/Beagleboard:Desktops_On_Ubuntu/Debian#Ubuntu_Precise_On_A_microSD_With_Ubuntu_Desktop

My project is about to achieve the Object or facial detection and tracking
with Pan/Tilt using OpenCV

If I would like to make it, should I prepare those equipment as shown as
above (mouse, display, keyboard and powered usb hub)?

If it is yes, how to connect with Beaglebone Black, cause as we know about
the feature of it, it just has a little HDMI connect plug can be used.
Using the transfer or similar like that?

Thank your patient

I am really looking forward your reply

Your sincerely

Yanlong Mu(Ian)


On Thu, Apr 17, 2014 at 5:56 AM, Sungjin Chun wrote:

> Did you generate locale data? For example, in arch linux (which I'm using),
> after configuration of /etc/locale.conf I should execute
>
> locale-gen
>
> so that configured locale data be generated.
>
>
>
> On Thu, Apr 17, 2014 at 12:57 PM, Yanlong Mu  wrote:
>
>> Hi Everybody
>>
>> I just get the new image boot on the BBB 12.04.2 LTS
>>
>> When I put the sudo apt-get update and upgrade, it showed some warning as
>> below
>>
>> locale: Cannot set LC_CTYPE to default locale: No such file or directory
>> locale: Cannot set LC_MESSAGES to default locale: No such file or
>> directory
>> locale: Cannot set LC_ALL to default locale: No such file or directory
>>
>>
>> And When I was going to install a desktops (xface)
>>
>> it showed
>>
>> perl: warning: Falling back to the standard locale ("C").
>> perl: warning: Setting locale failed.
>> perl: warning: Please check that your locale settings:
>> LANGUAGE = (unset),
>> LC_ALL = (unset),
>> LC_TIME = "en_GB.UTF-8",
>> LC_MONETARY = "en_GB.UTF-8",
>> LC_ADDRESS = "en_GB.UTF-8",
>> LC_TELEPHONE = "en_GB.UTF-8",
>> LC_NAME = "en_GB.UTF-8",
>> LC_MEASUREMENT = "en_GB.UTF-8",
>> LC_IDENTIFICATION = "en_GB.UTF-8",
>> LC_NUMERIC = "en_GB.UTF-8",
>> LC_PAPER = "en_GB.UTF-8",
>> LANG = "en_GB.UTF-8"
>> perl: warning: Falling back to the standard locale ("C").
>>
>> Anyone can help me to solve that problem?
>>
>> Kind Regards
>>
>> Ian
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/ufeNqBNCnqs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] ome problem when I get update

[Yanlong Mu]

Hi

sorry for bothering you

one more question which is

when I use dpkg-reconfigure locales as root

it showed

root@ubuntu-armhf:/home/ubuntu# dpkg-reconfigure locales
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_GB.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Generating locales...
  en_US.UTF-8... up-to-date
Generation complete.

is that normall? or not

Thanks a lot

Ian


On Thu, Apr 17, 2014 at 6:14 AM, William Hermans  wrote:

> *dpkg-reconfigure locales *as root, or using sudo. Assuming the package
> is installed properly.
>
>
> On Wed, Apr 16, 2014 at 9:56 PM, Sungjin Chun wrote:
>
>> Did you generate locale data? For example, in arch linux (which I'm
>> using),
>> after configuration of /etc/locale.conf I should execute
>>
>> locale-gen
>>
>> so that configured locale data be generated.
>>
>>
>>
>> On Thu, Apr 17, 2014 at 12:57 PM, Yanlong Mu  wrote:
>>
>>> Hi Everybody
>>>
>>> I just get the new image boot on the BBB 12.04.2 LTS
>>>
>>> When I put the sudo apt-get update and upgrade, it showed some warning
>>> as below
>>>
>>> locale: Cannot set LC_CTYPE to default locale: No such file or directory
>>> locale: Cannot set LC_MESSAGES to default locale: No such file or
>>> directory
>>> locale: Cannot set LC_ALL to default locale: No such file or directory
>>>
>>>
>>> And When I was going to install a desktops (xface)
>>>
>>> it showed
>>>
>>> perl: warning: Falling back to the standard locale ("C").
>>> perl: warning: Setting locale failed.
>>> perl: warning: Please check that your locale settings:
>>> LANGUAGE = (unset),
>>> LC_ALL = (unset),
>>> LC_TIME = "en_GB.UTF-8",
>>> LC_MONETARY = "en_GB.UTF-8",
>>> LC_ADDRESS = "en_GB.UTF-8",
>>> LC_TELEPHONE = "en_GB.UTF-8",
>>> LC_NAME = "en_GB.UTF-8",
>>> LC_MEASUREMENT = "en_GB.UTF-8",
>>> LC_IDENTIFICATION = "en_GB.UTF-8",
>>> LC_NUMERIC = "en_GB.UTF-8",
>>> LC_PAPER = "en_GB.UTF-8",
>>> LANG = "en_GB.UTF-8"
>>> perl: warning: Falling back to the standard locale ("C").
>>>
>>> Anyone can help me to solve that problem?
>>>
>>> Kind Regards
>>>
>>> Ian
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/ufeNqBNCnqs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Implementation Board?

[BBQTrader .]

Thanks Tom!


On Wed, Apr 16, 2014 at 8:37 PM, Tom Davies  wrote:

> BBQ -- depending on your volume, you could desolder the headers, or get a
> quote from CircuitCo for a run of BBBs without the headers installed, then
> use male headers on your board soldered to the header holes on the BBB.
>
> Perhaps there would be other people interested in that -- if the fixed
> costs of CircuitCo doing a special run are high you could run a Kickstarter
> campaign and try to get more buyers.
>
> --
> 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/CZkJyj29Gv8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB PRU example project creating and Compiling

[Eren Basturk]

Hi All,

I would like to say my problem, I would like to write some code for PRU 
units for that reason I enabled PRU on BBB and I run prepared examples on 
BBB.

But I don't know how can I create a project and compile.

for example there is a software below but I don't know how can I complie it 
and how can I run it?


#define GPIO1 0x4804c000 #define GPIO_CLEARDATAOUT 0x190 #define 
GPIO_SETDATAOUT 0x194 MOV r1, 10 BLINK: MOV r2, 7<<22 MOV r3, GPIO1 | 
GPIO_SETDATAOUT SBBO r2, r3, 0, 4 MOV r0, 0x00a0 DELAY: SUB r0, r0, 1 
QBNE DELAY, r0, 0 MOV r2, 7<<22 MOV r3, GPIO1 | GPIO_CLEARDATAOUT SBBO r2, 
r3, 0, 4 MOV r0, 0x00a0 DELAY2: SUB r0, r0, 1 QBNE DELAY2, r0, 0 SUB r1, 
r1, 1 QBNE BLINK, r1, 0



It is possible could you give some information about it?

Best Regards,
Eren Basturk

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Change default state of GPIO pin

[r van dam]

Thanks for the reply! The beeper is controlled by a transistor (limited 
with a resistor) so the current is within the margins.

I found a script to check the state of a pin:  findGPIO.js The output is;
P9_12 (gpio 60) mode: 7 (gpio1_28) 0x078 *pullup* Receiver Active

I checked other pins with this script, and P9_16 has this output;
P9_16 (gpio 51) mode: 7 (gpio1_19) 0x04c* pulldown* Receiver Active

I temporarely connected the base of the transistor to P9_16, and with this 
pin everything works perfectly. I however prefer to use pin P9_12 because 
of my circuit.

Is there a way to solve this by software, or will a simple pull down 
resistor do the trick?

Rob


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Official eQEP driver Support

[Giuseppe Iellamo]

I'm using it but in order to be fast ( I know it's not very linux style ... 
but )

Set up

#ifdef __arm__

#define MAP_SIZE 4096UL //< Constant used for the memory mapping of the eqep
#define MAP_MASK (MAP_SIZE - 1)

// mmaping device register in order to speed up things
if((fd = open("/dev/mem", O_RDWR | O_SYNC)) == -1)
{
LOG(logFATAL) << " Unable to open /dev/mem";
exit(-1);
}

map_base = mmap(0, MAP_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED, fd,
(eqepMap.at(channel).phAddress) & ~MAP_MASK );
if(map_base == (void *) -1) {
LOG(logFATAL) << " Unable to mmap eqep";
exit(-1);
}

virt_addr = map_base + ((eqepMap.at(channel).phAddress) & MAP_MASK);
#endif

Read Position

inline int32_t get_position_fast() { return *((int32_t *) virt_addr); } ///< 
not really clean but performing






Il giorno giovedì 17 aprile 2014 20:46:32 UTC+2, William Hermans ha scritto:
>
> Strawson, best thing I personally can think of, would be to use two or 
> more pointers to the same file, and rotate between them. Closing one down 
> while the other continues operating.
>
>
> On Thu, Apr 17, 2014 at 11:09 AM, Robert Nelson 
> 
> > wrote:
>
>> On Thu, Apr 17, 2014 at 12:30 PM, Strawson > 
>> wrote:
>> > Hello all,
>> >
>> > In an effort to make use of the eQEP modules on the beaglebone black we
>> > stumbled across the following encoder patch and were able to compile a
>> > loadable kernel module with the help of TI. Hopefully this will make 
>> its way
>> > to the "thirdparty" script in the debian build farm so the community 
>> can use
>> > this without recompiling
>> >
>> > https://github.com/Teknoman117/beaglebot/tree/master/encoders
>>
>> It looks pretty self-contained, i have no problem adding to the
>> current kernel patches..
>>
>> > I would like to make known a bug we ran into with reading the eQEP 
>> module
>> > that resulted in position values not updating after exactly 1020 reads
>> > without closing the file pointer. If the file pointer is closed and
>> > re-opened for every read, the behavior is normal, but opening/closing 
>> the
>> > file is painfully slow. I unfortunately don't really know where to begin
>> > with finding and fixing this problem, but any insight would be 
>> appreciated.
>>
>>
>> yikes, it still needs a little work then..
>>
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.