[beagleboard] Re: 4.4-lts plans (4.1-lts not going away)

[Robert Nelson]

On Mon, Jan 4, 2016 at 9:48 AM, Robert Nelson  wrote:
> Everyone,
>
> We are about a week away from, 4.4.0 lts being released.  (4.4.0-rc8
> is still being built for every distro on the farm)..
>
> I just want to ping and remind everyone with my plans.
>
> I'd like to keep "4.1.x" going till the 4.(4+next) lts release...
>
> Goals:
>
> 1:
> If it worked in "4.1.x-bone" it "should (i need to fix sgx
> (5.01.01.02))" work in "4.4.x-bone"  (4.4.x-bone will use uio_pruss as
> remoteproc_pruss is still not in mainline)
>
> (please test and report things broken in 4.4.x-bone)
>
> 2:
> New features/drivers/etc of course will be in "4.4.x-bone"  (i'm not
> planning to backport other drivers, instead recommend users upgrade to
> 4.4.x-bone)
>
> 3:
> "bb.org-overlays" needs to work with both "4.1.x-bone" & "4.4.x-bone"
>
> https://github.com/beagleboard/bb.org-overlays
>
> 4:
> RT: they'll be an "rt" variant of "4.4.x-bone" just like "4.1.x-bone"
> but currently there are build issues, so not released..

RT boots with external patches:

https://github.com/RobertCNelson/bb-kernel/commits/am33x-rt-v4.4

https://github.com/RobertCNelson/bb-kernel/commit/3259af1e75835a14a686c8887a7dc2aedf26181a

pushed out to the arm builder farm.

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

[beagleboard] Re: 4.4-lts plans (4.1-lts not going away)

[Robert Nelson]

On Mon, Jan 4, 2016 at 9:48 AM, Robert Nelson  wrote:
> Everyone,
>
> We are about a week away from, 4.4.0 lts being released.  (4.4.0-rc8
> is still being built for every distro on the farm)..
>
> I just want to ping and remind everyone with my plans.
>
> I'd like to keep "4.1.x" going till the 4.(4+next) lts release...
>
> Goals:
>
> 1:
> If it worked in "4.1.x-bone" it "should (i need to fix sgx
> (5.01.01.02))" work in "4.4.x-bone"  (4.4.x-bone will use uio_pruss as
> remoteproc_pruss is still not in mainline)
>
> (please test and report things broken in 4.4.x-bone)

i "think" sgx will work now:

https://github.com/RobertCNelson/bb-kernel/commit/a9924d79a6c8caa357dfc57873ddf3ef9bd078ef

Remember this the older "5.01.01.02" sgx lib's..  (aka if you where
using it and had it working in v4.1.x-bone..)

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Re: 4.4-lts plans (4.1-lts not going away)

[Lee Armstrong]

Understood. Very clear. Thank you
On Mon, 4 Jan 2016 at 20:17, Robert Nelson  wrote:

> On Mon, Jan 4, 2016 at 2:08 PM, Lee Armstrong  wrote:
> > Thanks Robert,
> >
> > I'll admit I stuck to the ti release as this was part of the Jessie
> console
> > image. Would you recommend staying with that?
>
> We use the "4.1.x-ti" release as the default..
>
> As it has very good support for both the BeagleBone's (am335x's) and
> BeagleBoard-X15 (am57xx)
>
> While the 'bone' branch is a little more tuned for the "am335x" (no
> smp, pcie, etc).
>
> Since with "bone" we track mainline, (v4.1.x-bone, v4.2.x-bone,
> v4.3.x-bone, etc..)  it's easy to push out "v4.4.x-bone" today, while
> the "4.4.x-ti" branch is going to take a few weeks to rebase it's
> v4.1.x-ti patchset.
>
> All the kernel images are in the apt repo, so you are free to install
> anything you want, via either the "update_kernel.sh" script or via
> "apt-get install"
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/T3lx6CQ4cXY/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] 4.4-lts plans (4.1-lts not going away)

[Robert Nelson]

On Mon, Jan 4, 2016 at 3:00 PM, John Syne  wrote:
> HI Robert,
>
> I think you said that TI are pushing everything to mainline so after 4.4/4.5, 
> there shouldn’t be that many patches remaining.

yeah for am335x that delta is very small.. (remoteproc_m3 should hit
4.5)  (hdmi audio is the big question.. )

Still lots for am57x. ;)

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] How to force boot from SD Card??

[John Syne]

Or if you are a hardware guy and you can work with small SMD components, you 
can also change the SYS_BOOT configuration as shown on Page 6 of the BBB 
schematics. In essence, move R68 to R93. This will be the equivalent to 
pressing the boot button.

Regards,
John




> On Jan 4, 2016, at 8:51 AM, Steve Moser  wrote:
> 
> Thanks
> 
> On Monday, January 4, 2016 at 11:24:20 AM UTC-5, Steve Moser wrote:
> OK, first let me apologize if this has been answered several times before.
> 
> I have a stripped beaglebone black that boots from SD card.  When I mean 
> stripped it does NOT have eMMC, USB Client, reset button, HDMI Framer, boot 
> button, micro HDMI, USB Host and more missing.  Like I said it boots from SD 
> card.  It is running Angstrom GNU/Linux v2013.06 (Core edition) version 3.8.13
> 
> So I have another Full blown BBB with nothing missing.  It is running 
> Angstrom GNU/Linux version 3.8.13-00726-gbe46145-dirty from the eMMC.
> 
> What I want to do is take the SD card from the stripped BBB and boot from it 
> in the Full BBB, When I try this, it still boots from the eMMC and not the SD 
> card.
> 
> Any suggestions/Ideas to try??  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 
> .

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] 2015-09-06 machinekit image not picking up mouse/keyboard on powered USB hub.

[John Syne]

I have also used both Logitech and Microsoft wireless Keyboard/Mouse combos 
with a powered USB hub and they work fine with the BBB.

Regards,
John




> On Jan 4, 2016, at 9:18 AM, Charles Steinkuehler  
> wrote:
> 
> Make sure the hub and all USB devices are connected at power-on,
> otherwise, try a different hub.
> 
> I have used the Logitech mouse/keyboard combos (various ones with a
> single USB receiver) as well as powered USB hubs successfully.  The
> hub I typically use is built-in to various Dell monitors I picked up
> at surplus for use with the BBB.  I honestly haven't seen much trouble
> with the USB ports (as long as you're not trying to hot-plug), but
> maybe I've just been lucky.
> 
> Regardless, the Machinekit 3.8.13-xenomai kernel should support the
> same USB devices as the standard 3.8.13 kernel, so any USB tips or
> debugging help (for the 3.8.13 kernel) should apply.
> 
> ...or if you're feeling particularly adventurous, you could work on
> trying to port to the 4.x kernel series (different cape manager and
> PRU support).
> 
> On 1/4/2016 2:25 AM, gfunky...@googlemail.com wrote:
>> Hello Guys,
>> is ther any solution for this usb hub issue?
>> 
>> I have the same probleme.
>> 
>> best regards
>> Gerhard
>> 
>> Am Freitag, 11. September 2015 21:03:41 UTC+2 schrieb Wally Bkg:
>>> 
>>> Just installed the 2015-09-06 Machinekit image and when booted it doesn't 
>>> pick up my USB mouse or keyboard attached to a powered hub.
>>> I get the X display on my monitor and a mouse cursor which doesn't move.  
>>> I can login over ssh.  While I realize ssh -X is generally better 
>>> performance, especially if using the 192.168.7.2 usb connection, but I need 
>>> a local mouse/keyboard and HDMI display for some things I'm working on.
>>> 
>>> The bone-debian-8.1-lxqt-4gb-armhf-2015-08-16-4gb.img. works fine with 
>>> this exact setup.
>>> 
>>> If I unplug the hub, plug in my Logitech USB wireless  touchpad/keyboard 
>>> dongle and press the reset button I get a working mouse/keyboard after it 
>>> boots.
>>> If I then hot unplug the dongle and plug in the hub, the USB 
>>> mouse/keyboard then work,  If I also plug the dongle into the hub both 
>>> mouse and touchpad work as does both keyboards.
>>> What gives?
>>> 
>>> I need the hub because I need a mouse, keyboard, and webcam.  Re-booting 
>>> with the dongle attached to the hub again yields no working mouse/keyboard.
>>> 
>>> 
>> 
> 
> 
> -- 
> Charles Steinkuehler
> char...@steinkuehler.net
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

Re: [beagleboard] Re: 4.4-lts plans (4.1-lts not going away)

[Robert Nelson]

On Mon, Jan 4, 2016 at 1:57 PM, Lee Armstrong  wrote:
> Robert,
>
> What is the difference between the bone and ti releases please?

bone = mainline + cape manager + git cherry picks from ti's kernel branch..

ti = ti's kernel branch  + cape manager...

Almost everything ti develops, ends up in their ti kernel branch
before mainline..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] blank flasher

[tim . limon]

Thank you, Robert.

I stumbled a bit getting the SD card to accept the image file.  I ended up 
formatting my 8 GB card as NTFS with a 1024 block size prior to writing the 
image via Win32DiskImager.  The card became unreadable in windows once the 
image was written.  I took a chance and installed it in the BBB anyway. 
 When I applied power, the board began reflashing.  I'm up and running now. 
Thank you for the pointer.


Does anyone know why the card becomes unreadable once the .img file is 
written?  Is this normal behavior?

 

On Monday, January 4, 2016 at 6:04:57 AM UTC-8, RobertCNelson wrote:
>
> On Sun, Jan 3, 2016 at 12:29 AM,   
> wrote: 
> > I'm new at this so I beg your forgiveness. 
> > 
> > Which files go on the USB stick and which go on the MicroSD card? 
> > 
> > I have a A5C board that stalls on booting and won't allow me to boot 
> from 
> > the SD card.  I'm hoping the USB flasher will help. 
> > 
> > Thanks on advance for the guidance 
>
> Use any image market with '2gb' here: 
>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots
>  
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

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

Re: [beagleboard] Newb need some help with lcd touchscreen

[bestouff]

Hi,

Did you make any progress on that ? I have the same cape and would also 
like to use it with a standard kernel.

Regards,
Xav

Le lundi 24 août 2015 04:53:24 UTC+2, Ridemywideglide a écrit :
>
> I'll read-up on copying my kernel config (greek at this point), but my 
> main issue is the setup of the database, the web front end and all the 
> related stuff with temp measuring and liquid levels that report to the 
> webserver that's setup, that I'm worried about... I'm not "friendly" with 
> this OS, so that has been a ton of work for me to piece together from 
> others workings..
>
> I looked at the uEnv on the waveshare image and did see tons of 
> differences, know enough to know that copying them into mine isn't going to 
> make things just work. I really need to get a "linux for dummies" book.. 
> I'm very far behind the curve with this...
>
> Thanks for the help.
> Brad
>
> On Sunday, August 23, 2015 at 6:45:19 PM UTC-6, RobertCNelson wrote:
>>
>> On Sun, Aug 23, 2015 at 6:37 PM, Ridemywideglide  
>> wrote: 
>> > I'm needing some help, as I have very limited experience with linux. 
>> I've 
>> > had a BBB for a few months now, and managed to cobble together many 
>> > different items from google searches and sites like this one, and am 
>> working 
>> > towards a functional touch screen beer brewing controller. 
>> > After getting to where I am now, I purchased a 7in touchscreen from 
>> ebay 
>> > (china) that is a waveshare cape/lcd package. 
>> > Waveshare has a debian image that I have downloaded, and it boots right 
>> up 
>> > to a working screen, but only runs from the card, no flasher. Trouble 
>> is, I 
>> > have lots of hours into the BBB setup I'm running now, and would of 
>> course, 
>> > rather not start over. I'm needing to get the LCD to work on my 
>> existing 
>> > system. 
>> > 
>> > Running wheezy, kernal 3.8.13-bone74, 
>>
>> So i'd start with copying your "working" kernel config and copy it to 
>> the "working" debian setup.. 
>>
>> http://www.waveshare.com/wiki/BB_Black_XXX_CAPE_Source_Code 
>>
>> I don't see that anyone has submited support for that lcd for the 
>> commuinty.. 
>>
>> https://github.com/beagleboard/linux/tree/3.8/firmware/capes 
>>
>> Looking at the schematic, it would be a pretty simplistic compared to 
>> other capes for new users to port. ;) 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>

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

Re: [beagleboard] blank flasher

[Robert Nelson]

On Mon, Jan 4, 2016 at 11:35 AM,   wrote:
> Thank you, Robert.
>
> I stumbled a bit getting the SD card to accept the image file.  I ended up
> formatting my 8 GB card as NTFS with a 1024 block size prior to writing the
> image via Win32DiskImager.  The card became unreadable in windows once the
> image was written.  I took a chance and installed it in the BBB anyway.
> When I applied power, the board began reflashing.  I'm up and running now.
> Thank you for the pointer.
>
>
> Does anyone know why the card becomes unreadable once the .img file is
> written?  Is this normal behavior?

Windows can't read extX partitions without a 3rd party driver..

(and i nuked the fat "boot/drivers" partition in all images, so even
that doesn't show up anymore)

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] 2015-09-06 machinekit image not picking up mouse/keyboard on powered USB hub.

[gfunkyboy]

Hello,
this sounds very good.I used a logilink hub with power supply, and it didn't 
work. Now I have to try another one.

Thanks for support.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] 4.4-lts plans (4.1-lts not going away)

[John Syne]

HI Robert,

I think you said that TI are pushing everything to mainline so after 4.4/4.5, 
there shouldn’t be that many patches remaining.

Regards,
John




> On Jan 4, 2016, at 12:16 PM, Robert Nelson  wrote:
> 
> On Mon, Jan 4, 2016 at 2:08 PM, Lee Armstrong  wrote:
>> Thanks Robert,
>> 
>> I'll admit I stuck to the ti release as this was part of the Jessie console
>> image. Would you recommend staying with that?
> 
> We use the "4.1.x-ti" release as the default..
> 
> As it has very good support for both the BeagleBone's (am335x's) and
> BeagleBoard-X15 (am57xx)
> 
> While the 'bone' branch is a little more tuned for the "am335x" (no
> smp, pcie, etc).
> 
> Since with "bone" we track mainline, (v4.1.x-bone, v4.2.x-bone,
> v4.3.x-bone, etc..)  it's easy to push out "v4.4.x-bone" today, while
> the "4.4.x-ti" branch is going to take a few weeks to rebase it's
> v4.1.x-ti patchset.
> 
> All the kernel images are in the apt repo, so you are free to install
> anything you want, via either the "update_kernel.sh" script or via
> "apt-get install"
> 
> Regards,
> 
> -- 
> Robert Nelson
> https://rcn-ee.com/
> 
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard+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: 4.4-lts plans (4.1-lts not going away)

[Lee Armstrong]

Thanks Robert,

I'll admit I stuck to the ti release as this was part of the Jessie console
image. Would you recommend staying with that?

On Mon, 4 Jan 2016 at 20:06, Robert Nelson  wrote:

> On Mon, Jan 4, 2016 at 1:57 PM, Lee Armstrong  wrote:
> > Robert,
> >
> > What is the difference between the bone and ti releases please?
>
> bone = mainline + cape manager + git cherry picks from ti's kernel branch..
>
> ti = ti's kernel branch  + cape manager...
>
> Almost everything ti develops, ends up in their ti kernel branch
> before mainline..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/T3lx6CQ4cXY/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] Re: 4.4-lts plans (4.1-lts not going away)

[Lee Armstrong]

Robert,

What is the difference between the bone and ti releases please?

Lee

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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: 4.4-lts plans (4.1-lts not going away)

[Robert Nelson]

On Mon, Jan 4, 2016 at 2:08 PM, Lee Armstrong  wrote:
> Thanks Robert,
>
> I'll admit I stuck to the ti release as this was part of the Jessie console
> image. Would you recommend staying with that?

We use the "4.1.x-ti" release as the default..

As it has very good support for both the BeagleBone's (am335x's) and
BeagleBoard-X15 (am57xx)

While the 'bone' branch is a little more tuned for the "am335x" (no
smp, pcie, etc).

Since with "bone" we track mainline, (v4.1.x-bone, v4.2.x-bone,
v4.3.x-bone, etc..)  it's easy to push out "v4.4.x-bone" today, while
the "4.4.x-ti" branch is going to take a few weeks to rebase it's
v4.1.x-ti patchset.

All the kernel images are in the apt repo, so you are free to install
anything you want, via either the "update_kernel.sh" script or via
"apt-get install"

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] About generic_buffer.c fail to write the current_trigger

[ThanapatMax]

Thank you so much . but Im struck in I cant find adc mode.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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: USB Hub freeze

[evilwulfie]

Is this a external powered hub ?


On 1/4/2016 2:33 PM, Alessio wrote:
> Hi everyone,
> I have an issue with usb devices such as mouse or touchscreen monitor
> and it seems related to the hub freeze. Sometimes the device stop
> working and the only way to resume it is to restart the system. The
> problem is probably related to an interference in the usb cable from
> the host to the device, I can see usb signals using an oscilloscope
> and the 5V line is not stable and sometimes it drops below 4,5V and
> the AM335x processor detects an over current condition and it removes
> the usb session. The only way I know to resume the usb is to restart
> BBB. I asked to TI Sitara support about the interference and they told
> me that a >=120uF of capacitance is needed on VBUS and better if it is
> near to the usb socket. From the BBB schematic I can see that the
> capacitance is 100uF and it is placed before the usb power switch.
> I have the kernel 3.8.13-bone30 and Ubuntu saucy as OS, I also tried
> Debian and the issue is present too.
> Is there a way to resume the usb session by software without
> restarting BBB?
> Is there a revising of the board in act that could consider the
> revising of the usb host section?
>
> 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.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] PRU "DMA" signalling to Linux Kernel cache issue

[Przemek Klosowski]

On Sun, Jan 3, 2016 at 8:46 AM, Tom Smith  wrote:
> Hello,
>
> I encounter a caching issue with my application. I will describe what I want
> to do, how I planned to do it and what goes wrong:
>
> WHAT:
>
> By using the PRU on my BBB, I want to timestamp a periodic rising edge on
> one input pin in a nanosecond scale and signal it to a Linux Kernel module
> on the ARM.

OK, I think I understand what you want to do.

> HOW:
>
> To receive an interrupt in my kernel module, I bridged the pin with the
> rising edge to a second one (timer4 interrupt).
> This interrupt fires a few microseconds after the event happened.
>
> To read values from the PRU with best determinism and lowest latency, I
> allocated some DDR memory with dma_alloc_coherent() in my kernel module and
> handout the address via debugfs to the PRU.
>
>
> The PRU is in endless loop:
>
> wait for rising edge, read out the PRU cycle counter and write the cycle
> counter to the DDR memory address.
> This works like a charm and I got the event's cycle counter snapshot in my
> kernel module!

That's pretty clever.

> The kernel module interrupt is firing a few microseconds after the event and
> has some jitter I want to avoid.
>
> So I decided it would be best to burst the actual cycle counter to a second
> ram address for a ten thousand times by the PRU so when the Kernel module
> reads this ddr location, It knows the difference from the event's cycle
> counter and the cycle counter now.
>
> This does not work!
>
>
> WRONG:
>
> Initially everything appered to be working. I was reading out for example:
>
> event cycles: 1000
> now cycles: 4300
>
> great!
>
>
> But to test the "now cycles" counter, I added to the kernel module to read
> it thousand times in a loop. Guess what? It is thousand times the same.
>

Just to make sure, did you declare the variables as volatile? If you
forgot, the compiler could be playing tricks on you by not reloading
them.

So, I am a little suspicious of the numbers, both of their magnitude
and of the relative difference. If the interrupt latency is few us,
then the cycle count difference should be few hundred:
PRU runs at 200MHz and your code presumably does the cycle count read,
DDR write and a loop/backward jump.

To check the exact timing, you'd have to provide the actual code,
either the relevant loop snippet or put the whole thing on pastebin.

Are you sure that you're using the correct word size?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] Cannot Fully Disable HDMI device tree overlay, HDMI Okay/HDMIN to be specific.

[dean . bate]

On Wednesday, December 9, 2015 at 8:19:06 PM UTC-7, Dean Bate wrote:
>
> Thanks for the reply. In the link that you sent me 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03 Is the 
> procedure as listed in section 3.2 (i.e.flash the eMMC) all that is 
> required to update my BB image or is there more to it ? I am very new at 
> this and I am trying to decipher all that is relevant in getting the 
> following command to work ...
>
> $ sudo sh -c "echo BB-SPIDEV1 > $SLOTS
>
> Regards,
>
> Dean
>
> On Wed, Dec 9, 2015 at 3:04 PM, Robert Nelson  
> wrote:
>
>> >
>> > I am using Ubuntu 15.04 and the BB Debian image on my BBB is 
>> 2014-04-23. I
>> > have been trying for some days now to disable my HDMI and HDMIN 
>> overlays so
>>
>> It would have been faster to first upgrade to "2015-11-03
>>
>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03
>>
>> > that I can access my BB-SPIDEV1 with limited success. One command in
>> > particular (i.e. optargs=quiet
>> > capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN) does indeed 
>> disable
>> > HDMI yet with that said it will not allow me to enable SPIDEV1. I have
>> > boldface highlighted the commands that were used as well as the o/p for
>> > presentation purposes. Any insight into resolving this problem would be
>> > helpful and much appreciated. Further note: I also tried
>> > optargs=capemgr.disable_partno=BB-BONELT-HDMI and all to no avail.
>>
>> optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>> optargs=capemgr.enable_partno=BB-SPIDEV1
>>
>> Then that would have worked out of the box..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> 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/FsKmr7hUksg/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 those that might benefit from my findings. Initially I could not flash 
the BBB. Why ? The driver for my card reader is not supported under Linux. 
I have yet to determine if I will now be able to disable the HDMI with this 
latest image
 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] Major errors reading multiple AIN from the Beaglebone using C++.

[ss70]

Hi friends, 

I'm trying to read the voltage inputs from two analog IR distance sensors 
plugged into AIN0 and AIN1 using C++ code. 

I used Derek Molloy's code which can successfully read voltage values from 
one Analog pin. However, whenever I modify the code and try to read more 
than one analog pin, *I receive this error: *

terminate called after throwing an instance of 'std::ios_base::failure'
  what():  basic_filebuf::underflow error reading the file
Aborted 

I'm not really sure what this error is or why I'm getting it. Please let me 
know if you have knowledge on this matter:

*Code is as follows: *

#include
#include
#include
#include
#include
using namespace std;

#define LDR_PATH "/sys/bus/iio/devices/iio:device0/in_voltage"

int readAnalog(int number){  
   
   stringstream ss; 
   
   ss << LDR_PATH << number << "_raw"; 
   
   fstream fs; 
   
   fs.open(ss.str().c_str(), fstream::in); 
   
   fs >> number; 
   
   fs.close(); 
   
   return number;
   
}

int main(int argc, char* argv[]){
   
   cout << "Starting the IR distance sensor program:" << endl;
   
   while(1) {
   
  int value0 = readAnalog(0);
  int value1 = readAnalog(1);
  float V0 = ((float)value0 / 4096) * 1.8;
  float V1 = ((float)value1 / 4096) * 1.8; 
  
  cout << "Sensor0 is: " << V0 << " Sensor1 is: " << V1 << '\r' << 
flush;
  
  usleep(10); 
  
   }
   
   return 0;
}

I know this is some sort of access error, and there is a workaround for the 
python libraries 
(see: 
https://github.com/adafruit/adafruit-beaglebone-io-python/blob/master/source/c_adc.c
 
). But I am unsure as to how I can use this information in the context of 
C++ code. 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] Bizarre BBB LAN USB Host problem

[injunear]

 

Bizarre BBB LAN USB Host problem


It seems the USB connection from my BBB to my Ubuntu host trashes my host 
internet connection.


Ubuntu uname -a

Linux ubuntu1 3.16.0-44-generic #59~14.04.1-Ubuntu SMP …


BBB uname -a

Linux beaglebone 3.8.13-bone79 #1 SMP ...


Network configuration:

Cable modem (192.168.100.1) connected to:

Router (192.168.1.1) connected to:

Ubuntu host (192.168.1.10)

and

BBB (192.168.1.15)


BBB (192.168.7.2) is also connected to host (192.168.7.1) via USB and Putty.


On initial startup, everything seems to work fine. I have full terminal 
access from my host to the BBB via Putty. I can ping both my router and my 
modem from both the BBB terminal and a terminal window in my host. I can 
access the internet with my host browser.


When I restart or reboot the BBB with the USB cable connected to the host, 
I can still connect to my BBB with Putty on the host. I can also ping both 
my router and modem from the BBB. 


HOWEVER, I cannot ping either the router or the modem from my host 
terminal. 

BUT, if I reboot the BBB again, my host can now ping the router, but not 
the cable modem. 

AND the BBB can ping both the router and the modem.


This condition is maintained no matter how I reset, power on/off, or just 
plain disconnect the BBB from everything. Until I reboot my host computer, 
I cannot ping (or browse to) the modem (or internet), but I can ping and 
browse to my router.


With the BBB powered and connected to the router, but not the host USB, it 
has no effect on how my host connects to the modem and internet.


How is the BBB USB connection to my host computer causing my host computer 
to not connect to the cable modem even though my host connects to the 
router? And why does it only happen after I reset the BBB when it is 
connected to my host via USB?


More importantly, how might one fix it, please?


Thank you for your time and consideration.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] Bizarre BBB LAN USB Host problem

[injunear]

 

Bizarre BBB LAN USB Host problem


It seems the USB connection from my BBB to my Ubuntu host trashes my host 
internet connection.


Ubuntu uname -a

Linux ubuntu1 3.16.0-44-generic #59~14.04.1-Ubuntu SMP …


BBB uname -a

Linux beaglebone 3.8.13-bone79 #1 SMP ...


Network configuration:

Cable modem (192.168.100.1) connected to:

Router (192.168.1.1) connected to:

Ubuntu host (192.168.1.10)

and

BBB (192.168.1.15)


BBB (192.168.7.2) is also connected to host (192.168.7.1) via USB and Putty.


On initial startup, everything seems to work fine. I have full terminal 
access from my host to the BBB via Putty. I can ping both my router and my 
modem from both the BBB terminal and a terminal window in my host. I can 
access the internet with my host browser.


When I restart or reboot the BBB with the USB cable connected to the host, 
I can still connect to my BBB with Putty on the host. I can also ping both 
my router and modem from the BBB. 


HOWEVER, I cannot ping either the router or the modem from my host 
terminal. 

BUT, if I reboot the BBB again, my host can now ping the router, but not 
the cable modem. 

AND the BBB can ping both the router and the modem.


This condition is maintained no matter how I reset, power on/off, or just 
plain disconnect the BBB from everything. Until I reboot my host computer, 
I cannot ping (or browse to) the modem (or internet), but I can ping and 
browse to my router.


With the BBB powered and connected to the router, but not the host USB, it 
has no effect on how my host connects to the modem and internet.


How is the BBB USB connection to my host computer causing my host computer 
to not connect to the cable modem even though my host connects to the 
router? And why does it only happen after I reset the BBB when it is 
connected to my host via USB?


More importantly, how might one fix it, please?


Thank you for your time and consideration.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] ./update_kernel.sh unable to locate package mt7601u-modules-4.1.13-ti-r38, ti-sgx-es8-modules-4.1.13

[zentojamorn]

I tried to run the sudo ./update_kernel.sh from /opt/scripts/tools. 
However, it is unable to locate package mt7601u-modules-4.1.13-ti-r38, 
ti-sgx-es8-modules-4.1.13.

Here's is the full output.

debian@beaglebone:/opt/scripts/tools$ sudo ./update_kernel.sh   
 
info: checking archive 
  
2016-01-02 07:29:50 
URL:https://rcn-ee.com/repos/latest/jessie-armhf/LATEST-ti [90/90] -> "LA
-   
 
Kernel Options: 
 
ABI:1 STABLE 4.1.13-ti-r38 
  
ABI:1 TESTING 4.1.13-ti-r33 
 
ABI:1 EXPERIMENTAL 4.4.0-rc4-ti-r3 
  
-   
 
info: you are running: [4.1.13-ti-r38], latest is: [4.1.13-ti-r38] 
updating...   
Hit http://repos.rcn-ee.com jessie InRelease
Ign http://ftp.us.debian.org jessie InRelease
Hit http://ftp.us.debian.org jessie-updates InRelease
Get:1 http://repos.rcn-ee.com jessie/main armhf Packages [267 kB]
Hit http://security.debian.org jessie/updates InRelease
Hit http://ftp.us.debian.org jessie Release.gpg
Get:2 http://security.debian.org jessie/updates/main armhf Packages [213 kB]
Get:3 http://ftp.us.debian.org jessie-updates/main armhf Packages [3,589 B]
Get:4 http://ftp.us.debian.org jessie-updates/contrib armhf Packages [20 B]
Get:5 http://ftp.us.debian.org jessie-updates/non-free armhf Packages [20 B]
Get:6 http://ftp.us.debian.org jessie Release [148 kB]
Get:7 http://ftp.us.debian.org jessie/main armhf Packages [8,836 kB]
Get:8 http://security.debian.org jessie/updates/contrib armhf Packages [997 
B]
Get:9 http://security.debian.org jessie/updates/non-free armhf Packages [20 
B]
Get:10 http://ftp.us.debian.org jessie/contrib armhf Packages [44.7 kB]
Get:11 http://ftp.us.debian.org jessie/non-free armhf Packages [74.6 kB]
Fetched 9,588 kB in 3min 25s (46.6 kB/s)
Reading package lists... Done   
 
Checking dpkg...   
  
Checking apt-cache...   
 
debug: reinstalling: [linux-image-4.1.13-ti-r38]   
  
Reading package lists... Done   
 
Building dependency tree   
  
Reading state information... Done   
 
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not 
upgraded.
Need to get 20.9 MB of archives.   
  
After this operation, 0 B of additional disk space will be used.   
  
Get:1 http://repos.rcn-ee.com/debian/ jessie/main linux-image-4.1.13-ti-r38 
armhf 1jessie [20
Fetched 20.9 MB in 7min 21s (47.4 kB/s)
(Reading database ... 35547 files and directories currently installed.) 
 
Preparing to unpack .../linux-image-4.1.13-ti-r38_1jessie_armhf.deb ... 
 
Unpacking linux-image-4.1.13-ti-r38 (1jessie) over (1jessie) ...   
  
Setting up linux-image-4.1.13-ti-r38 (1jessie) ... 
  
update-initramfs: Generating /boot/initrd.img-4.1.13-ti-r38 
 
Reading package lists... Done   
 
Building dependency tree   
  
Reading state information... Done   
 
E: Unable to locate package mt7601u-modules-4.1.13-ti-r38   
 
E: Couldn't find any package by regex 'mt7601u-modules-4.1.13-ti-r38'   
 
Reading package lists... Done   
 
Building dependency tree   
  
Reading state information... Done   
 
E: Unable to locate package ti-sgx-es8-modules-4.1.13-ti-r38   
  
E: Couldn't find any package by regex 'ti-sgx-es8-modules-4.1.13-ti-r38'   
  
update-initramfs: Generating /boot/initrd.img-4.1.13-ti-r38 
   

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

[beagleboard] Re: Problem installing cisco vpn client on beaglebone black

[tedkooos]

Did you find a solution to the problem,because I also need to install 
AnyConnect on my beaglebone black. Thank you!


неделя, 14 септември 2014 г., 19:49:39 UTC+2, sanjay ahuja написа:
>
>
> I am newbie to beaglebone black. I tried installing vpn client on my 
> beaglebone black but got following error
>
> Installing Cisco AnyConnect Secure Mobility Client...
> Removing previous installation...
> /opt/cisco/vpn/bin/vpn_uninstall.sh: line 76: 
> /opt/cisco/anyconnect/bin/manifesttool: cannot execute binary file
> mv: cannot stat `/opt/cisco/vpn/*.log': No such file or directory
> Extracting installation files to /tmp/vpn.zfFX5g/vpninst174979895.tgz...
> Unarchiving installation files to /tmp/vpn.zfFX5g...
> Starting Cisco AnyConnect Secure Mobility Client Agent...
> /etc/init.d/vpnagentd: line 41: /opt/cisco/anyconnect/bin/vpnagentd: 
> cannot execute binary file
>
>
>
> Has anyone faced similar issue or tried installing cisco vpn client and 
> was successfully able to use it.?
>
> Any other vpn client installation would also help.
>

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

[beagleboard] Bizarre BBB LAN USB Host problem

[injunear]

 

Bizarre BBB LAN USB Host problem


It seems the USB connection from my BBB to my Ubuntu host trashes my host 
internet connection.


Ubuntu uname -a

Linux ubuntu1 3.16.0-44-generic #59~14.04.1-Ubuntu SMP …


BBB uname -a

Linux beaglebone 3.8.13-bone79 #1 SMP ...


Network configuration:

Cable modem (192.168.100.1) connected to:

Router (192.168.1.1) connected to:

Ubuntu host (192.168.1.10)

and

BBB (192.168.1.15)


BBB (192.168.7.2) is also connected to host (192.168.7.1) via USB and Putty.


On initial startup, everything seems to work fine. I have full terminal 
access from my host to the BBB via Putty. I can ping both my router and my 
modem from both the BBB terminal and a terminal window in my host. I can 
access the internet with my host browser.


When I restart or reboot the BBB with the USB cable connected to the host, 
I can still connect to my BBB with Putty on the host. I can also ping both 
my router and modem from the BBB. 


HOWEVER, I cannot ping either the router or the modem from my host 
terminal. 

BUT, if I reboot the BBB again, my host can now ping the router, but not 
the cable modem. 

AND the BBB can ping both the router and the modem.


This condition is maintained no matter how I reset, power on/off, or just 
plain disconnect the BBB from everything. Until I reboot my host computer, 
I cannot ping (or browse to) the modem (or internet), but I can ping and 
browse to my router.


With the BBB powered and connected to the router, but not the host USB, it 
has no effect on how my host connects to the modem and internet.


How is the BBB USB connection to my host computer causing my host computer 
to not connect to the cable modem even though my host connects to the 
router? And why does it only happen after I reset the BBB when it is 
connected to my host via USB?


More importantly, how might one fix it, please?


Thank you for your time and consideration.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] Can't put eth0 down

[100pedros]

Hello, I just purchased a BeagleBone Green
I'm trying to turn off the functionality of eth0 which keeps coming up as a 
working port using dhcp.
When I try to use ifconfig eth0 down I get no response and the port stays 
connected
When I use ifdown eth0, i get ifdown: eth0 not configured and the port 
stays connected
the /etc/network/interfaces file as shipped does not configure the port, 
the lines to set it as dhcp are commented out
something else is configuring the port. 

How can I disable the port?
 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] Rebooting BBB w/ USB connected trashes host connection to internet.

[injunear]

 

Rebooting BBB w/ USB connected trashes host connection to internet.


Network configuration:

Cable modem (192.168.100.1) to internet connected to:

Router (192.168.1.1) connected to:

Ubuntu host (static 192.168.1.10)

and

BBB (static 192.168.1.15)


BBB (192.168.7.2) is also connected to host (192.168.7.1) via USB and Putty.


Ubuntu uname -a

Linux ubuntu1 3.16.0-44-generic #59~14.04.1-Ubuntu SMP …


BBB uname -a

Linux beaglebone 3.8.13-bone79 #1 SMP ...



On initial startup, everything seems to work fine. I have full terminal 
access from my host to the BBB via Putty. I can ping both my router and my 
cable modem from both the BBB terminal and a terminal window in my host. I 
can access the internet with my host browser.


When I restart or reboot the BBB with the USB cable connected to the host, 
I can still connect to my BBB with Putty on the host. I can also ping both 
my router and modem from the BBB. 


HOWEVER, I cannot ping either the router or the modem from my host 
terminal. 

BUT, if I reboot the BBB again, my host can now ping the router, but not 
the cable modem. 

AND the BBB can still ping both the router and the modem.


This condition is maintained no matter how I reset, power on/off, or just 
plain disconnect the BBB from everything. Until I reboot my host computer, 
it cannot ping the modem or browse to the internet. 


With the BBB powered and connected to the router, but not the host USB, it 
has no effect on how my host connects to the modem and internet.


Question: Why does the BBB USB connection to my host computer cause my host 
computer to not connect to the cable modem even though my host connects to 
the router? And why does it only happen after I reset the BBB when it is 
connected to my host via USB?


More importantly, how might one fix it, please?


Thank you for your time and consideration.


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] PRU "DMA" signalling to Linux Kernel cache issue

[Tom Smith]

Hello,

I encounter a caching issue with my application. I will describe what I 
want to do, how I planned to do it and what goes wrong:

*WHAT:*

By using the PRU on my BBB, I want to timestamp a periodic rising edge on 
one input pin in *a nanosecond scale *and signal it to a Linux Kernel 
module on the ARM.


*HOW:*

To receive an interrupt in my kernel module, I bridged the pin with the 
rising edge to a second one (timer4 interrupt).
This interrupt fires a few microseconds after the event happened.

To read values from the PRU with best determinism and lowest latency, I 
allocated some DDR memory with dma_alloc_coherent() in my kernel module and 
handout the address via debugfs to the PRU.


The PRU is in endless loop:  

wait for rising edge, read out the PRU cycle counter and write the cycle 
counter to the DDR memory address. 
*This works like a charm and I got the event's cycle counter snapshot in my 
kernel module!*


The kernel module interrupt is firing a few microseconds after the event 
and has some jitter I want to avoid.

So I decided it would be best to burst the actual cycle counter to a second 
ram address for a ten thousand times by the PRU so when the Kernel module 
reads this ddr location, It knows the difference from the event's cycle 
counter and the cycle counter now.

*This does not work!*


*WRONG:*

Initially everything appered to be working. I was reading out for example:

event cycles: 1000
now cycles: 4300

great!


But to test the "now cycles" counter, I added to the kernel module to read 
it thousand times in a loop. Guess what?* It is thousand times the same.*

I tried a few options. For example to write and read two alternating 
memaddresses for this "now counter" by kernel and pru but nothing gives the 
results I expected.
It seems like anyone caches the results.



Any help? So many thanks... I hope the problem can be understood.
Tom

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] blank flasher

[tim . limon]

I'm new at this so I beg your forgiveness.  

Which files go on the USB stick and which go on the MicroSD card?  

I have a A5C board that stalls on booting and won't allow me to boot from 
the SD card.  I'm hoping the USB flasher will help.

Thanks on advance for the guidance

--Tim

On Monday, December 21, 2015 at 4:36:59 PM UTC-8, William Hermans wrote:
>
> *Sure, internally, it's just bmaptools/dd...*
>>
>> * and it'll dump errors/directions to the serial console..*
>>
>> * For almost all *.img's i include a *.job.txt file that'll just work.*
>>
>
> Ok, cool. I kind of half expected this to be a Jessie only feature. 
>
> On Mon, Dec 21, 2015 at 5:17 PM, Robert Nelson  > wrote:
>
>> On Mon, Dec 21, 2015 at 5:35 PM, William Hermans > > wrote:
>> > Robert, can this also be used with the "release" images as well ?
>>
>> Sure, internally, it's just bmaptools/dd...
>>
>> and it'll dump errors/directions to the serial console..
>>
>> For almost all *.img's i include a *.job.txt file that'll just work.
>>
>> Regards,
>>
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> 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] REGEN1 pin

[Chandan Kumar]

Hi Sir,

I am designing a PCB using AM5728 processor with TPS659037 PMIC ,i have 
kept Beagle board X15 schematics as reference .
I have a doubt on REGEN1 pin. The datasheet of TPS659037 says the REGEN1 
output is active high but it has been pulled up to 3.3V in the load switch 
(TPS22965DSG)side .Also the default output configuration(OTP) for REGEN1 
output is push-pull.

So please suggest me  how to design VDD_ON_3V3 line such that the 
TPS22965DSG should be ON so that i can configure PMIC for the required 
settings soon after i assemble the board.

Thanks,
Chandan

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] VNC running on Ubuntu

[ja . qb . sz]

Hi all,
I'm having similar problem with BBB (rev A5B).
It's running Debian 8 from official beagle bone black image.
I've installed *x11vnc *package using *apt-get* and it gives me the same 
info as for Vincenzo Cacciatore (...XOpenDisplay failed. No -display or 
DISPLAY...)
*pgrep -l -f -- -auth* command returns nothing.
*x11vnc -findauth* returns *xauth: not found*
I was logged as *root.*

I did never attached external screen (over HDMI) to this board so I'm not 
sure if GUI is there.

Can anyone help please?

regards,
Kuba


W dniu niedziela, 15 września 2013 18:15:07 UTC+2 użytkownik Nuno napisał:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> On 09/15/2013 05:16 AM, Vincenzo Cacciatore wrote: 
> > 15/09/2013 09:15:28 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 
> 2024 
> > 15/09/2013 09:15:28 XOpenDisplay("") failed. 
> > 15/09/2013 09:15:28 Trying again with XAUTHLOCALHOSTNAME=localhost ... 
> > 15/09/2013 09:15:28 
> > 15/09/2013 09:15:28 *** XOpenDisplay failed. No -display or DISPLAY. 
> > 
> > Can someone help me? 
>
> You'll have to run x11vnc with the user that is currently running X, 
> e.g., use sudo -u USERNAME -i for that or you can run x11vnc as root if 
> you prefer. 
> Alternatively you can pass the xauth option or set the XAUTHORITY 
> environment variable and point to the right place 
>
> pgrep -l -f -- -auth 
>
> then 
> x11vnc -auth BLA 
>
> BLA is what the pgrep command will give you, look for the parameter 
> after the X -auth 
>
> You can also use x11vnc -findauth , check the x11vnc manual page for 
> more details: 
>
> man x11vnc 
>
>
> cheers, 
> Nuno 
>
> - -- 
> http://aeminium.org/nuno/ 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1.4.12 (GNU/Linux) 
>
> iQIcBAEBAgAGBQJSNd0LAAoJEPIY6fuKMkz5zqcP/0UJHiRQIy96i8MVpWO4IOva 
> pFrloM9yGLYDEE/8hODfDQYovGF+yrt3CsDRZzgSHSeYknnGTPUQznCQ/XkYuHOQ 
> EklNstK1hDjdSfi1fjSKgh3ySapmIHyUm6fZtddSkibtQcmDtxl+r4ZTj8MRYF02 
> 9KSJsG2895UdgrW5wxUcXsoUtTlSatTmQ0yAMrKsAXASqwvTTUc/KHjTLfgfqvoG 
> GIV0yiAfNL3rEyyliS84bZEBfg4Vmpy0pXeC4+ik0LoWVzsCcjAs/klS3IPjF6sR 
> CbS+r9MFvO/aShWQd8YzRMMh2G+sdxQDGn1XueVJVB0L3ARdKFRNuNFkP4axWFDL 
> ED3rypG+dx2OsD5L6mvh7GC0dZ7cA4zPlUDapNitBNiH+s1UdoNiZ1UKsGSsNtfI 
> Uf/D28GF+RF5HQRnbDwYTT98x0/YSZikvIHesFc969VcEWtRZLva/OkLKbfXgl7X 
> L9kH40xbjzefXbauaNmSUuZOChr/UKIRrLrfk2KogtJXSICtKzlsooUmPlrAVthq 
> hLbZg5sMlTz/VdWLWLUTbcAK5GLBtIx414pWZ4tKtJ2pFBlHQil7lv23tnE0BBQe 
> Aeznu5/P8UmfRqk75XZRj+Q3vwV5P/0vFh8K6NihBSEd3DdZcFgU1kNSZJoabTCQ 
> EoxaB/8VDVZYhHuMVuka 
> =2L+9 
> -END PGP SIGNATURE- 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] Rebooting BBB w/ USB connected trashes host connection to internet.

[injunear]

Rebooting BBB w/ USB connected trashes host connection to internet.


Network configuration:

Cable modem (192.168.100.1) to internet connected to:

Router (192.168.1.1) connected to:

Ubuntu host (static 192.168.1.10)

and

BBB (static 192.168.1.15)


BBB (192.168.7.2) is also connected to host (192.168.7.1) via USB and Putty.


Ubuntu uname -a

Linux ubuntu1 3.16.0-44-generic #59~14.04.1-Ubuntu SMP …


BBB uname -a

Linux beaglebone 3.8.13-bone79 #1 SMP ...



On initial startup, everything seems to work fine. I have full terminal 
access from my host to the BBB via Putty. I can ping both my router and my 
cable modem from both the BBB terminal and a terminal window in my host. I 
can access the internet with my host browser.


When I restart or reboot the BBB with the USB cable connected to the host, 
I can still connect to my BBB with Putty on the host. I can also ping both 
my router and modem from the BBB. 


HOWEVER, I cannot ping either the router or the modem from my host 
terminal. 

BUT, if I reboot the BBB again, my host can now ping the router, but not 
the cable modem. 

AND the BBB can still ping both the router and the modem.


This condition is maintained no matter how I reset, power on/off, or just 
plain disconnect the BBB from everything. Until I reboot my host computer, 
it cannot ping the modem or browse to the internet. 


With the BBB powered and connected to the router, but not the host USB, it 
has no effect on how my host connects to the modem and internet.


Question: Why does the BBB USB connection to my host computer cause my host 
computer to not connect to the cable modem even though my host connects to 
the router? And why does it only happen after I reset the BBB when it is 
connected to my host via USB?


More importantly, how might one fix it, please?


Thank you for your time and consideration.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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: Enabling MMC2 for 4 bit SDIO Wifi Card

[nick]

Hey Danny,

How did you go with this?

I am looking at doing the exact same thing, any results yet?

Cheers

NP

On Tuesday, 8 December 2015 03:41:55 UTC+11, c.danny...@uptake.com wrote:
>
> Hi Ya'll,
>
>
> I am trying to interface a LSR TIWi-BLE wifi card with my Beaglebone 
> Black. I would like to keep the on board eMMC functional so I cannot use 
> MMC1. 
>
> Looking at the Sitara datasheet and the Beaglebone black schematic it 
> seems that all 6 wires needed for 4 bit SDIO SDIO are available on the 
> header.
>
> MMC2_CLK -> 8.18
> MMC2_CMD -> 9.15 (also attached to another input, would need to remove 
> R160?)
> MMC2_DAT0 -> 8.12
> MMC2_DAT1 -> 8.11
> MMC2_DAT2 -> 8.16
> MMC2_DAT3 -> 8.15
>
> Do I just need to write an overlay to enable these pins for mmc function 
> in the cape manager?
>
> I'm currently waiting for the device to begin testing, but I am surprised 
> to see that I could not find any resources or documentation of someone 
> interfacing with a 4 bit SDIO device on MMC2 while maintaining eMMC func on 
> MMC1
>
> Would love to hear if anyone has accomplished this already and how they 
> went about solving this problem.
>
> Cheers,
> Danny Salzman
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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: 2015-09-06 machinekit image not picking up mouse/keyboard on powered USB hub.

[gfunkyboy]

Hello Guys,
is ther any solution for this usb hub issue?

I have the same probleme.

best regards
Gerhard

Am Freitag, 11. September 2015 21:03:41 UTC+2 schrieb Wally Bkg:
>
> Just installed the 2015-09-06 Machinekit image and when booted it doesn't 
> pick up my USB mouse or keyboard attached to a powered hub.
> I get the X display on my monitor and a mouse cursor which doesn't move.  
> I can login over ssh.  While I realize ssh -X is generally better 
> performance, especially if using the 192.168.7.2 usb connection, but I need 
> a local mouse/keyboard and HDMI display for some things I'm working on.
>
> The bone-debian-8.1-lxqt-4gb-armhf-2015-08-16-4gb.img. works fine with 
> this exact setup.
>
> If I unplug the hub, plug in my Logitech USB wireless  touchpad/keyboard 
> dongle and press the reset button I get a working mouse/keyboard after it 
> boots.
> If I then hot unplug the dongle and plug in the hub, the USB 
> mouse/keyboard then work,  If I also plug the dongle into the hub both 
> mouse and touchpad work as does both keyboards.
> What gives?
>
> I need the hub because I need a mouse, keyboard, and webcam.  Re-booting 
> with the dongle attached to the hub again yields no working mouse/keyboard.
>
>

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

[nitinghediya30]

Hi All,
getting following error message while beaglebone strating.
can u pl kind help me how to resolve and one more thing is all four user 
leds are not blinking even after powerup the board

U-Boot SPL 2013.04-dirty (Jun 19 2013 - 
09:57:14)
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
mmc_send_cmd : timeout: No status update
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
NAND:  No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

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
Net:not set. Validating first E-fuse MAC
Phy not found
PHY reset timed out
cpsw, usb_ether
Hit any key to stop autoboot:  0 
U-Boot# 
U-Boot# 
U-Boot# 
U-Boot# U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)
Unknown command 'U-Boot' - try 'help'
U-Boot# 
Unknown command 'U-Boot' - try 'help'
U-Boot# 
Unknown command 'U-Boot' - try 'help'
U-Boot# 
Unknown command 'U-Boot' - try 'help'
U-Boot# I2C:   read1 U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14 
I2C:   read1 U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14 I2C:   
read1 U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14###0
CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.7 | VT102 | Offline | 
ttyUSB0 
 



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

[beagleboard] Re: Using SPI in a kernel module

[bchengcong]

Hello,
I saw your publish question about using SPI in a kernel module. I kind of 
stucking in this problem as well. 
So i wonder if you find a solution? 

 I know it's too late to ask, but i hope i'm lucky to get some feedback 
from you.

Regards,
Cheng

Le lundi 28 juillet 2014 16:00:59 UTC+2, Nils a écrit :
>
> Hello,
>
> I'm currently working on a kernel module which needs to communicate via 
> SPI to an external microchip.
>
> I used the cape manager to enable SPI. The device is accessible through 
> /dev/spidev1.0.
> But since it's a kernel module, I guess it's not recommended to access 
> files via sys_open()?
>
> Another approach I found would be adding a struct to 
> *arch/arm/mach-omap2/board-am335xevm.c 
> *and then use *spi_register_driver()* in my kernel module. But in my 
> kernel sources (3.8.13) this file doesn't exist.
>
> What would be the right way to use SPI in my kernel module?
>
> Regards,
> Nils
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] blank flasher

[Robert Nelson]

On Sun, Jan 3, 2016 at 12:29 AM,   wrote:
> I'm new at this so I beg your forgiveness.
>
> Which files go on the USB stick and which go on the MicroSD card?
>
> I have a A5C board that stalls on booting and won't allow me to boot from
> the SD card.  I'm hoping the USB flasher will help.
>
> Thanks on advance for the guidance

Use any image market with '2gb' here:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] ./update_kernel.sh unable to locate package mt7601u-modules-4.1.13-ti-r38, ti-sgx-es8-modules-4.1.13

[Robert Nelson]

On Sat, Jan 2, 2016 at 1:54 AM,   wrote:
> I tried to run the sudo ./update_kernel.sh from /opt/scripts/tools.
> However, it is unable to locate package mt7601u-modules-4.1.13-ti-r38,
> ti-sgx-es8-modules-4.1.13.
>
> Here's is the full output.
>
> debian@beaglebone:/opt/scripts/tools$ sudo ./update_kernel.sh

debian@beaglebone:/opt/scripts/tools$ git pull

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] REGEN1 pin

[Gerald Coley]

You must use the REGEN1 pin as done on the schematic to guarantee the power
sequencing. The design in the schematic works. If you want to create a new
design and try something else, then you are certainly welcome to do so.


Gerald


On Mon, Jan 4, 2016 at 6:52 AM, Chandan Kumar 
wrote:

> Hi Sir,
>
> I am designing a PCB using AM5728 processor with TPS659037 PMIC ,i have
> kept Beagle board X15 schematics as reference .
> I have a doubt on REGEN1 pin. The datasheet of TPS659037 says the REGEN1
> output is active high but it has been pulled up to 3.3V in the load switch
> (TPS22965DSG)side .Also the default output configuration(OTP) for REGEN1
> output is push-pull.
>
> So please suggest me  how to design VDD_ON_3V3 line such that the
> TPS22965DSG should be ON so that i can configure PMIC for the required
> settings soon after i assemble the board.
>
> Thanks,
> Chandan
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from 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.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] 4.4-lts plans (4.1-lts not going away)

[Jason Kridner]

What do folks think about switching to an -rt as the default? It seems -rt
is a major usage for BeagleBone and the builds seem to be working rather
nicely. Thoughts?

On Mon, Jan 4, 2016 at 4:03 PM Robert Nelson 
wrote:

> On Mon, Jan 4, 2016 at 3:00 PM, John Syne  wrote:
> > HI Robert,
> >
> > I think you said that TI are pushing everything to mainline so after
> 4.4/4.5, there shouldn’t be that many patches remaining.
>
> yeah for am335x that delta is very small.. (remoteproc_m3 should hit
> 4.5)  (hdmi audio is the big question.. )
>
> Still lots for am57x. ;)
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+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: Enabling MMC2 for 4 bit SDIO Wifi Card

[Danny Salzman]

Hi Nick,

Do to lack of resources we have backlogged this for now.

It seems possible, but I have still not found any working example.

-Danny

On Sun, Jan 3, 2016 at 8:38 PM,  wrote:

> Hey Danny,
>
> How did you go with this?
>
> I am looking at doing the exact same thing, any results yet?
>
> Cheers
>
> NP
>
> On Tuesday, 8 December 2015 03:41:55 UTC+11, c.danny...@uptake.com wrote:
>>
>> Hi Ya'll,
>>
>>
>> I am trying to interface a LSR TIWi-BLE wifi card with my Beaglebone
>> Black. I would like to keep the on board eMMC functional so I cannot use
>> MMC1.
>>
>> Looking at the Sitara datasheet and the Beaglebone black schematic it
>> seems that all 6 wires needed for 4 bit SDIO SDIO are available on the
>> header.
>>
>> MMC2_CLK -> 8.18
>> MMC2_CMD -> 9.15 (also attached to another input, would need to remove
>> R160?)
>> MMC2_DAT0 -> 8.12
>> MMC2_DAT1 -> 8.11
>> MMC2_DAT2 -> 8.16
>> MMC2_DAT3 -> 8.15
>>
>> Do I just need to write an overlay to enable these pins for mmc function
>> in the cape manager?
>>
>> I'm currently waiting for the device to begin testing, but I am surprised
>> to see that I could not find any resources or documentation of someone
>> interfacing with a 4 bit SDIO device on MMC2 while maintaining eMMC func on
>> MMC1
>>
>> Would love to hear if anyone has accomplished this already and how they
>> went about solving this problem.
>>
>> Cheers,
>> Danny Salzman
>>
> --
> 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/RjL2gU2EvC0/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] 4.4-lts plans (4.1-lts not going away)

[Robert Nelson]

Everyone,

We are about a week away from, 4.4.0 lts being released.  (4.4.0-rc8
is still being built for every distro on the farm)..

I just want to ping and remind everyone with my plans.

I'd like to keep "4.1.x" going till the 4.(4+next) lts release...

Goals:

1:
If it worked in "4.1.x-bone" it "should (i need to fix sgx
(5.01.01.02))" work in "4.4.x-bone"  (4.4.x-bone will use uio_pruss as
remoteproc_pruss is still not in mainline)

(please test and report things broken in 4.4.x-bone)

2:
New features/drivers/etc of course will be in "4.4.x-bone"  (i'm not
planning to backport other drivers, instead recommend users upgrade to
4.4.x-bone)

3:
"bb.org-overlays" needs to work with both "4.1.x-bone" & "4.4.x-bone"

https://github.com/beagleboard/bb.org-overlays

4:
RT: they'll be an "rt" variant of "4.4.x-bone" just like "4.1.x-bone"
but currently there are build issues, so not released..

5:
"update_kernel.sh" grew an "--lts-4_1" and "--lts-4_4" options, for
users who set this script up as a cron job "--lts" still points to
4.1.x but that will change in the next month..

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh ${options}

Mainline:

4.1.x-bone:

--bone-channel --lts-4_1

4.1.x-rt-bone:

--bone-rt-channel --lts-4_1

4.4.x-bone:

--bone-channel --lts-4_4

4.4.x-rt-bone: (when actually built..)

--bone-rt-channel --lts-4_4

For "4.1.x-ti" users, 4.4.x-ti will be coming, it'll just lag behind
for a few weeks..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

[beagleboard] Re: Bizarre BBB LAN USB Host problem

[Graham]

Stop trying to use the USB connection. That is for very simple systems.
Using the host as a bridge between the USB/BBB and the network can create 
all kinds of problems.
Use Ethernet connection directly to the BBB, if you want it to be on the 
network.
Then everything works, just like Linus wanted it to.
--- Graham

==

On Monday, January 4, 2016 at 6:37:30 AM UTC-6, inju...@mail.com wrote:
>
> Bizarre BBB LAN USB Host problem
>
>
> It seems the USB connection from my BBB to my Ubuntu host trashes my host 
> internet connection.
>
>
> Ubuntu uname -a
>
> Linux ubuntu1 3.16.0-44-generic #59~14.04.1-Ubuntu SMP …
>
>
> BBB uname -a
>
> Linux beaglebone 3.8.13-bone79 #1 SMP ...
>
>
> Network configuration:
>
> Cable modem (192.168.100.1) connected to:
>
> Router (192.168.1.1) connected to:
>
> Ubuntu host (192.168.1.10)
>
> and
>
> BBB (192.168.1.15)
>
>
> BBB (192.168.7.2) is also connected to host (192.168.7.1) via USB and 
> Putty.
>
>
> On initial startup, everything seems to work fine. I have full terminal 
> access from my host to the BBB via Putty. I can ping both my router and my 
> modem from both the BBB terminal and a terminal window in my host. I can 
> access the internet with my host browser.
>
>
> When I restart or reboot the BBB with the USB cable connected to the host, 
> I can still connect to my BBB with Putty on the host. I can also ping both 
> my router and modem from the BBB. 
>
>
> HOWEVER, I cannot ping either the router or the modem from my host 
> terminal. 
>
> BUT, if I reboot the BBB again, my host can now ping the router, but not 
> the cable modem. 
>
> AND the BBB can ping both the router and the modem.
>
>
> This condition is maintained no matter how I reset, power on/off, or just 
> plain disconnect the BBB from everything. Until I reboot my host computer, 
> I cannot ping (or browse to) the modem (or internet), but I can ping and 
> browse to my router.
>
>
> With the BBB powered and connected to the router, but not the host USB, it 
> has no effect on how my host connects to the modem and internet.
>
>
> How is the BBB USB connection to my host computer causing my host computer 
> to not connect to the cable modem even though my host connects to the 
> router? And why does it only happen after I reset the BBB when it is 
> connected to my host via USB?
>
>
> More importantly, how might one fix it, please?
>
>
> Thank you for your time and consideration.
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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] How to force boot from SD Card??

[Steve Moser]

OK, first let me apologize if this has been answered several times before.

I have a stripped beaglebone black that boots from SD card.  When I mean 
stripped it does NOT have eMMC, USB Client, reset button, HDMI Framer, boot 
button, micro HDMI, USB Host and more missing.  Like I said it boots from 
SD card.  It is running Angstrom GNU/Linux v2013.06 (Core edition) version 
3.8.13

So I have another Full blown BBB with nothing missing.  It is 
running Angstrom GNU/Linux version 3.8.13-00726-gbe46145-dirty from the 
eMMC.

What I want to do is take the SD card from the stripped BBB and boot from 
it in the Full BBB, When I try this, it still boots from the eMMC and not 
the SD card.

Any suggestions/Ideas to try??  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: How to force boot from SD Card??

[Gerald Coley]

If the eMMC is not there, it should boot from the SD card by default,
assuming you have left all the boot resistors in their default
configuration..

Gerald


On Mon, Jan 4, 2016 at 10:38 AM, Robert Nelson 
wrote:

> On Mon, Jan 4, 2016 at 10:36 AM, Steve Moser
>  wrote:
> > Great, thank you.  Anyway to make that a permanent solution?
>
> Option a:
> erase eMMC
>
> Option b:
> understand eMMC's u-boot..
>
>
> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-DealingwitholdBootloaderineMMC
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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: How to force boot from SD Card??

[Steve Moser]

Thanks

On Monday, January 4, 2016 at 11:24:20 AM UTC-5, Steve Moser wrote:
>
> OK, first let me apologize if this has been answered several times before.
>
> I have a stripped beaglebone black that boots from SD card.  When I mean 
> stripped it does NOT have eMMC, USB Client, reset button, HDMI Framer, boot 
> button, micro HDMI, USB Host and more missing.  Like I said it boots from 
> SD card.  It is running Angstrom GNU/Linux v2013.06 (Core edition) version 
> 3.8.13
>
> So I have another Full blown BBB with nothing missing.  It is 
> running Angstrom GNU/Linux version 3.8.13-00726-gbe46145-dirty from the 
> eMMC.
>
> What I want to do is take the SD card from the stripped BBB and boot from 
> it in the Full BBB, When I try this, it still boots from the eMMC and not 
> the SD card.
>
> Any suggestions/Ideas to try??  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.

[beagleboard] Can't disable the HDMI Overlay to load new overlays.

[Tyler Turcotte]

I have been at this for many of hours now.  I am running Angstrom with the 
3.8 kernel on BeagleBone Black

I edited the /boot/uEnv.txt file with the appropriate way to disable the 
HDMI.  I have also tried about another half a dozen slightly different 
variations.

optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN


However, after reboot the HDMI is still enabled.

cat /sys/devices/bone_capemgr.8/slots
 0: 54:PF--- 
 1: 55:PF--- 
 2: 56:PF--- 
 3: 57:PF--- 
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI


As can be seen by the L, the HDMI cape is still enabled which prevents me 
from enabling my new cape that will reorganized some pins on the HDMI 
output for GPIO control.  When trying to load the new cape, it claims the 
file already exists.  This is what led me to the HDMI cape not being 
properly disabled. Everything leads me to believe that I am doing this 
correctly but haven't reached a conclusion or had any results.

Thanks,
Tyler


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from 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: 2015-09-06 machinekit image not picking up mouse/keyboard on powered USB hub.

[Charles Steinkuehler]

Make sure the hub and all USB devices are connected at power-on,
otherwise, try a different hub.

I have used the Logitech mouse/keyboard combos (various ones with a
single USB receiver) as well as powered USB hubs successfully.  The
hub I typically use is built-in to various Dell monitors I picked up
at surplus for use with the BBB.  I honestly haven't seen much trouble
with the USB ports (as long as you're not trying to hot-plug), but
maybe I've just been lucky.

Regardless, the Machinekit 3.8.13-xenomai kernel should support the
same USB devices as the standard 3.8.13 kernel, so any USB tips or
debugging help (for the 3.8.13 kernel) should apply.

...or if you're feeling particularly adventurous, you could work on
trying to port to the 4.x kernel series (different cape manager and
PRU support).

On 1/4/2016 2:25 AM, gfunky...@googlemail.com wrote:
> Hello Guys,
> is ther any solution for this usb hub issue?
> 
> I have the same probleme.
> 
> best regards
> Gerhard
> 
> Am Freitag, 11. September 2015 21:03:41 UTC+2 schrieb Wally Bkg:
>>
>> Just installed the 2015-09-06 Machinekit image and when booted it doesn't 
>> pick up my USB mouse or keyboard attached to a powered hub.
>> I get the X display on my monitor and a mouse cursor which doesn't move.  
>> I can login over ssh.  While I realize ssh -X is generally better 
>> performance, especially if using the 192.168.7.2 usb connection, but I need 
>> a local mouse/keyboard and HDMI display for some things I'm working on.
>>
>> The bone-debian-8.1-lxqt-4gb-armhf-2015-08-16-4gb.img. works fine with 
>> this exact setup.
>>
>> If I unplug the hub, plug in my Logitech USB wireless  touchpad/keyboard 
>> dongle and press the reset button I get a working mouse/keyboard after it 
>> boots.
>> If I then hot unplug the dongle and plug in the hub, the USB 
>> mouse/keyboard then work,  If I also plug the dongle into the hub both 
>> mouse and touchpad work as does both keyboards.
>> What gives?
>>
>> I need the hub because I need a mouse, keyboard, and webcam.  Re-booting 
>> with the dongle attached to the hub again yields no working mouse/keyboard.
>>
>>
> 


-- 
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] Re: USB Hub freeze

[Alessio]

Hi everyone,
I have an issue with usb devices such as mouse or touchscreen monitor and 
it seems related to the hub freeze. Sometimes the device stop working and 
the only way to resume it is to restart the system. The problem is probably 
related to an interference in the usb cable from the host to the device, I 
can see usb signals using an oscilloscope and the 5V line is not stable and 
sometimes it drops below 4,5V and the AM335x processor detects an over 
current condition and it removes the usb session. The only way I know to 
resume the usb is to restart BBB. I asked to TI Sitara support about the 
interference and they told me that a >=120uF of capacitance is needed on 
VBUS and better if it is near to the usb socket. From the BBB schematic I 
can see that the capacitance is 100uF and it is placed before the usb power 
switch.
I have the kernel 3.8.13-bone30 and Ubuntu saucy as OS, I also tried Debian 
and the issue is present too.
Is there a way to resume the usb session by software without restarting BBB?
Is there a revising of the board in act that could consider the revising of 
the usb host section?

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] How to force boot from SD Card??

[Robert Nelson]

On Mon, Jan 4, 2016 at 10:24 AM, Steve Moser
 wrote:
> OK, first let me apologize if this has been answered several times before.
>
> I have a stripped beaglebone black that boots from SD card.  When I mean
> stripped it does NOT have eMMC, USB Client, reset button, HDMI Framer, boot
> button, micro HDMI, USB Host and more missing.  Like I said it boots from SD
> card.  It is running Angstrom GNU/Linux v2013.06 (Core edition) version
> 3.8.13
>
> So I have another Full blown BBB with nothing missing.  It is running
> Angstrom GNU/Linux version 3.8.13-00726-gbe46145-dirty from the eMMC.
>
> What I want to do is take the SD card from the stripped BBB and boot from it
> in the Full BBB, When I try this, it still boots from the eMMC and not the
> SD card.
>
> Any suggestions/Ideas to try??  Thanks

Push and hold the "boot" button before you apply power..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

[beagleboard] Re: How to force boot from SD Card??

[Steve Moser]

Great, thank you.  Anyway to make that a permanent solution?

On Monday, January 4, 2016 at 11:24:20 AM UTC-5, Steve Moser wrote:
>
> OK, first let me apologize if this has been answered several times before.
>
> I have a stripped beaglebone black that boots from SD card.  When I mean 
> stripped it does NOT have eMMC, USB Client, reset button, HDMI Framer, boot 
> button, micro HDMI, USB Host and more missing.  Like I said it boots from 
> SD card.  It is running Angstrom GNU/Linux v2013.06 (Core edition) version 
> 3.8.13
>
> So I have another Full blown BBB with nothing missing.  It is 
> running Angstrom GNU/Linux version 3.8.13-00726-gbe46145-dirty from the 
> eMMC.
>
> What I want to do is take the SD card from the stripped BBB and boot from 
> it in the Full BBB, When I try this, it still boots from the eMMC and not 
> the SD card.
>
> Any suggestions/Ideas to try??  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] Can't disable the HDMI Overlay to load new overlays.

[Robert Nelson]

On Mon, Jan 4, 2016 at 10:30 AM, Tyler Turcotte  wrote:
> I have been at this for many of hours now.  I am running Angstrom with the
> 3.8 kernel on BeagleBone Black
>
> I edited the /boot/uEnv.txt file with the appropriate way to disable the
> HDMI.  I have also tried about another half a dozen slightly different
> variations.
>
> optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
>
>
> However, after reboot the HDMI is still enabled.
>
> cat /sys/devices/bone_capemgr.8/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>
>
> As can be seen by the L, the HDMI cape is still enabled which prevents me
> from enabling my new cape that will reorganized some pins on the HDMI output
> for GPIO control.  When trying to load the new cape, it claims the file
> already exists.  This is what led me to the HDMI cape not being properly
> disabled. Everything leads me to believe that I am doing this correctly but
> haven't reached a conclusion or had any results.

Well, "cat /proc/cmdline" and verify you actually told it to disable it..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Re: How to force boot from SD Card??

[Robert Nelson]

On Mon, Jan 4, 2016 at 10:36 AM, Steve Moser
 wrote:
> Great, thank you.  Anyway to make that a permanent solution?

Option a:
erase eMMC

Option b:
understand eMMC's u-boot..

https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-DealingwitholdBootloaderineMMC

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Can't disable the HDMI Overlay to load new overlays.

[Tyler Turcotte]

Thank you for your response.

The resultant output is.

console=ttyO0,115200n8 quiet drm.debug=7 root=/dev/mmcblk0p2 ro rootfstype=ext4 
rootwait


Which leads me to believe that I didn't tell it to disable it.  However, I 
thought at boot the uEnv.txt file would be loaded or can I manually load 
the uEnv.txt file at boot.  Is there something incorrect in my syntax, 
maybe?  Still pretty new with the BeagleBone and there seems to be 
confusion between kernel and distribution release.

Thanks,
Tyler

On Monday, January 4, 2016 at 11:33:35 AM UTC-5, RobertCNelson wrote:
>
> On Mon, Jan 4, 2016 at 10:30 AM, Tyler Turcotte  > wrote: 
> > I have been at this for many of hours now.  I am running Angstrom with 
> the 
> > 3.8 kernel on BeagleBone Black 
> > 
> > I edited the /boot/uEnv.txt file with the appropriate way to disable the 
> > HDMI.  I have also tried about another half a dozen slightly different 
> > variations. 
> > 
> > optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN 
> > 
> > 
> > However, after reboot the HDMI is still enabled. 
> > 
> > cat /sys/devices/bone_capemgr.8/slots 
> >  0: 54:PF--- 
> >  1: 55:PF--- 
> >  2: 56:PF--- 
> >  3: 57:PF--- 
> >  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 
> >  5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 
> > 
> > 
> > As can be seen by the L, the HDMI cape is still enabled which prevents 
> me 
> > from enabling my new cape that will reorganized some pins on the HDMI 
> output 
> > for GPIO control.  When trying to load the new cape, it claims the file 
> > already exists.  This is what led me to the HDMI cape not being properly 
> > disabled. Everything leads me to believe that I am doing this correctly 
> but 
> > haven't reached a conclusion or had any results. 
>
> Well, "cat /proc/cmdline" and verify you actually told it to disable it.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

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

Re: [beagleboard] Can't disable the HDMI Overlay to load new overlays.

[Robert Nelson]

On Mon, Jan 4, 2016 at 10:48 AM, Tyler Turcotte  wrote:
> Thank you for your response.
>
> The resultant output is.
>
> console=ttyO0,115200n8 quiet drm.debug=7 root=/dev/mmcblk0p2 ro
> rootfstype=ext4 rootwait
>
>
> Which leads me to believe that I didn't tell it to disable it.  However, I
> thought at boot the uEnv.txt file would be loaded or can I manually load the
> uEnv.txt file at boot.  Is there something incorrect in my syntax, maybe?
> Still pretty new with the BeagleBone and there seems to be confusion between
> kernel and distribution release.

I don't remember, you'll have to search the archive back to Summer of 2013...

/boot/uEnv.txt is what i setup for all the debian/ubuntu instructions..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Am I on the right lines with where I want to go with bbb?

[John Syne]

This is the perfect platform for what you want to do. If you haven’t done any 
high speed digital design, I would advise that you keep the BBB layout as it is 
and then add your circuitry around the edges of the BBB circuitry. Modifying 
the BBB layout is not advisable unless you understand high speed digital 
design. Also be aware that many PCB manufacturers cannot make this board and 
not many PCB assembly houses can place the components with a low error rate. 
Circuitco who manufacturers the BBB does both PCB and assembly very well. There 
are also several members of the BBB community who would be willing to look at 
your layout and make suggestions on how to make improvements. 

Regards,
John




> On Jan 3, 2016, at 11:47 AM, truni  wrote:
> 
> Hi all
> 
> I am just starting out with the beaglebone (and linux for that matter), I am 
> running through derek molloys fantastic book and getting on OK.
> 
> Can you correct me if I am going in the completely wrong direction here, but 
> my intentions are as follows;
> 
> I have a project in mind (automotive based) (I do not necessarily want to 
> commercialize it, but I want to design my own single PCB which will include 
> the base BBB design and external circuitry.
> 
> My plans are;
> 
> 1. Learn everything I can with the BBB via Derek Molloy and possible other 
> embedded linux books...
> 2. Prototype external circuitry with BBB
> 3. Field test
> 4. After design is verified, integrate external circuitry into a single PCB 
> with BBB
> 5. Package it
> 
> I am an electronic engineer by day, although I will need to make some 
> progress with high speed digital design but hey if you don't try you won't 
> learn anything! No doubt I will make mistakes
> 
> Is this what the BBB was intended for?
> 
> Or is it intended to only really be used with capes?
> 
> Looking at the content of derek molloys book so far, it seems that there is a 
> standard linux distro on the board, with a hardware specific device tree. My 
> plan is to eventually (when I have learn what on earth I am doing) modify the 
> device tree to suit the hardware I integrate...
> 
> Interested to know your thoughts
> 
> I could have gone for major vendors embedded linux/arm development board but 
> I figured my learn curve would be much faster with the support of this 
> fantastic community...
> 
> I plan to document my journey to help others...
> 
> Thanks truni
> 
> -- 
> For more options, visit http://beagleboard.org/discuss 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from 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] Using SPI in a kernel module

[John Syne]

It would be helpful if you explained what it is you are trying to do and then 
we will provide suggestions on how to proceed. 

Regards,
John




> On Jan 4, 2016, at 1:34 AM, bchengc...@gmail.com wrote:
> 
> Hello,
> I saw your publish question about using SPI in a kernel module. I kind of 
> stucking in this problem as well. 
> So i wonder if you find a solution? 
> 
>  I know it's too late to ask, but i hope i'm lucky to get some feedback from 
> you.
> 
> Regards,
> Cheng
> 
> Le lundi 28 juillet 2014 16:00:59 UTC+2, Nils a écrit :
> Hello,
> 
> I'm currently working on a kernel module which needs to communicate via SPI 
> to an external microchip.
> 
> I used the cape manager to enable SPI. The device is accessible through 
> /dev/spidev1.0.
> But since it's a kernel module, I guess it's not recommended to access files 
> via sys_open()?
> 
> Another approach I found would be adding a struct to 
> arch/arm/mach-omap2/board-am335xevm.c and then use spi_register_driver() in 
> my kernel module. But in my kernel sources (3.8.13) this file doesn't exist.
> 
> What would be the right way to use SPI in my kernel module?
> 
> Regards,
> Nils
> 
> -- 
> For more options, visit http://beagleboard.org/discuss 
> 
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from 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] Can't disable the HDMI Overlay to load new overlays.

[Tyler Turcotte]

I finally came across a solution, after several days.  It is very important 
that you don't edit it in the /boot/uEnv.txt of the beaglebone.  You need 
to change the uEnv.txt in the mounted partition.  For me it was as simple 
as connecting via USB to the host computer and just clicking on the mounted 
partition, editing the uEnv.txt file and rebooting.  I ended up deleting 
everything in uEnv.txt and just using this.

optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

Output looked like this.

 0: 54:PF--- 
 1: 55:PF--- 
 2: 56:PF--- 
 3: 57:PF--- 
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 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,bspm_P8_27_d

This then let me upload the new overlay called bspm_P8_27_d.

Thanks for your assistance Robert and hopefully someone find this useful in 
the future.  Hopefully everything looks good when I start writing some new 
code.

Tyler


On Monday, January 4, 2016 at 11:54:59 AM UTC-5, RobertCNelson wrote:
>
> On Mon, Jan 4, 2016 at 10:48 AM, Tyler Turcotte  > wrote: 
> > Thank you for your response. 
> > 
> > The resultant output is. 
> > 
> > console=ttyO0,115200n8 quiet drm.debug=7 root=/dev/mmcblk0p2 ro 
> > rootfstype=ext4 rootwait 
> > 
> > 
> > Which leads me to believe that I didn't tell it to disable it.  However, 
> I 
> > thought at boot the uEnv.txt file would be loaded or can I manually load 
> the 
> > uEnv.txt file at boot.  Is there something incorrect in my syntax, 
> maybe? 
> > Still pretty new with the BeagleBone and there seems to be confusion 
> between 
> > kernel and distribution release. 
>
> I don't remember, you'll have to search the archive back to Summer of 
> 2013... 
>
> /boot/uEnv.txt is what i setup for all the debian/ubuntu instructions.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

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