Re: [beagleboard] Support for BBB kernel

[Greg Wilson-Lindberg]

Yeah, I thought about that, but that means that once you do the 
build_kernel, you have to restore the old .config and then rebuild with 
tools/rebuild.sh taking potentially twice as long.

I seem to be having bigger issues right now, so this isn't as big a deal as 
I thought.

Thanks,

On Thursday, June 30, 2016 at 4:54:43 PM UTC-7, William Hermans wrote:
>
> $ cp /path/to/.config /save/path/.config.old /* Or .config., or 
> .config.*/
>   
> ;)
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/df3d7acd-e0da-461e-ac1d-b02f1091a78d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Support for BBB kernel

[Greg Wilson-Lindberg]

Ok, I've got a confusion. 

I found a backup is the ti-linux-kernel-dev tree that I used to create the 
3.14.49-ti-r62 kernel that I've been using. It dates to 20150827. When I 
rebuild with tools/rebuild.sh everything gets recompiled. I have rebuilt my 
development system with Kubuntu 1204 64 bit, but that doesn't seem like it 
should force a recompile of everything.

Any idea what is happening?

On Thursday, June 30, 2016 at 1:56:38 PM UTC-7, RobertCNelson wrote:
>
> On Thu, Jun 30, 2016 at 3:55 PM, Greg Wilson-Lindberg 
>  wrote: 
> > Robert, 
> > How do I force a make clean on yakbuild? 
>
> ./build_kernel.sh 
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/b41c6b37-4336-4d5a-aea6-ab00ca0a6114%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW console packages?

[Robert Nelson]

On Thu, Jun 30, 2016 at 6:04 PM, Mark Grosen  wrote:
> Ok, I cloned that and copied into /lib/firmware and now the WiFi works (have
> not tried BT). So, after you fix the firmware package, I think the list of
> packages needed is:
> * wireless-tools
> * iw
> * wpasupplicant
> * bb-wl18xx-firmware
> * firmware-ti-connectivity
> I am not using connman, etc.

and "ti-wlconf", i need to add a hard dependicy to bb-wl18xx-firmware for that.

As it's used to program, /lib/firmware/ti-connectivity/wl1271-nvs.bin
with your wlan0 mac address

https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-wlan0


> I also changed uEnv.txt to use dtb=am335x-bonegreen-wireless.dtb - is this
> required?

That shouldn't be required, u-boot is patched to pick the correct dtb..

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYh%3DV%2BA44gOv54KmqGiZskSC-K0qMhic2i7RuaKzzcUKDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Support for BBB kernel

[William Hermans]

$ cp /path/to/.config /save/path/.config.old /* Or .config., or
.config.*/

;)

On Thu, Jun 30, 2016 at 4:10 PM, Greg Wilson-Lindberg 
wrote:

> I thought about that, I just wanted to make sure it wouldn't blow away and
> .config file that already existed.
>
> On Thursday, June 30, 2016 at 1:56:38 PM UTC-7, RobertCNelson wrote:
>>
>> On Thu, Jun 30, 2016 at 3:55 PM, Greg Wilson-Lindberg
>>
>> ./build_kernel.sh
>>
>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/9467100e-0e49-416d-a65f-d56e55a2ec36%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORqNZphsBN45PzuMpRhJB9%3D51cE40rHymD8pcHkYbMXHDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Support for BBB kernel

[Greg Wilson-Lindberg]

I thought about that, I just wanted to make sure it wouldn't blow away and 
.config file that already existed.

On Thursday, June 30, 2016 at 1:56:38 PM UTC-7, RobertCNelson wrote:
>
> On Thu, Jun 30, 2016 at 3:55 PM, Greg Wilson-Lindberg 
>
> ./build_kernel.sh 
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9467100e-0e49-416d-a65f-d56e55a2ec36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW console packages?

[Mark Grosen]

Ok, I cloned that and copied into /lib/firmware and now the WiFi works
(have not tried BT). So, after you fix the firmware package, I think the
list of packages needed is:
* wireless-tools
* iw
* wpasupplicant
* bb-wl18xx-firmware
* firmware-ti-connectivity
I am not using connman, etc.

I also changed uEnv.txt to use dtb=am335x-bonegreen-wireless.dtb - is this
required?

Mark


On Thu, Jun 30, 2016 at 2:58 PM Robert Nelson 
wrote:

> On Thu, Jun 30, 2016 at 4:54 PM, Mark Grosen  wrote:
> > Thanks, Robert. That got me the conf.bin file so that error is gone, but
> it
> > is still looking for wl18xx-fw-4.bin which does not exist. It seems like
> I
> > do need firmware-ti-connectivity otherwise there are no .bin files in
> > /lib/firmware/ti-connecivity. Is there a different firmware package?
>
> Yeah, that comes from the mainline tree, i need to update the
> firmware-ti-connectivty package..
>
>
> https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ti-connectivity
>
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYgh%3D3unJ3jcNWV4UDw6q3SpiPdCnkZXjM2LvJKZQiJTyA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAL8ugEeXGGTze5PMEBfhBbWGYVowCSf8AD%2B8TU5WL3NogviNew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW console packages?

[Robert Nelson]

On Thu, Jun 30, 2016 at 4:54 PM, Mark Grosen  wrote:
> Thanks, Robert. That got me the conf.bin file so that error is gone, but it
> is still looking for wl18xx-fw-4.bin which does not exist. It seems like I
> do need firmware-ti-connectivity otherwise there are no .bin files in
> /lib/firmware/ti-connecivity. Is there a different firmware package?

Yeah, that comes from the mainline tree, i need to update the
firmware-ti-connectivty package..

https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ti-connectivity

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgh%3D3unJ3jcNWV4UDw6q3SpiPdCnkZXjM2LvJKZQiJTyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW console packages?

[Mark Grosen]

Thanks, Robert. That got me the conf.bin file so that error is gone, but it
is still looking for wl18xx-fw-4.bin which does not exist. It seems like I
do need firmware-ti-connectivity otherwise there are no .bin files in
/lib/firmware/ti-connecivity. Is there a different firmware package?

Mark

On Thu, Jun 30, 2016 at 2:32 PM Robert Nelson 
wrote:

> Hi Mark,
>
> On Thu, Jun 30, 2016 at 4:26 PM, Mark Grosen  wrote:
> > I got a new BB Green Wireless. I prefer the smaller console Debian image,
> > but it appears to not ship WL8 support. What packages do I need to add to
> > get the WL8 WiFi to work? WL8 Bluetooth? I tried adding the following:
> > * wireless-tools
> > * firmware-ti-connectivity
> > * ti-wlconf
> > While booting, the firmware for WL8 cannot be found:
> > [   12.330260] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> > ti-connectivity/wl18xx-conf.bin failed with error -2
> > [   20.786201] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> > ti-connectivity/wl18xx-fw-4.bin failed with error -2
> > There are various wl128x-fw-5*.bin files in
> /lib/firmware/ti-connectivity. I
> > thought the defaults should work without the wl18xx-conf.bin file.
> >
> > debian@beaglebone:/lib/firmware/ti-connectivity$ uname -a
> > Linux beaglebone 4.4.12-ti-r31 #1 SMP Thu Jun 16 18:48:27 UTC 2016 armv7l
> > GNU/Linux
> > debian@beaglebone:/lib/firmware/ti-connectivity$ cat /etc/dogtag
> > BeagleBoard.org Debian Image 2016-06-19
>
> bb-wl18xx-firmware
>
> details:
>
> firmware for both the wifi/bluetooth:
>
>
> https://github.com/rcn-ee/repos/tree/master/bb-wl18xx-firmware/suite/jessie/debian
>
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYihAWVKkxY8i25ft1Yy548xA4FebSZVHk2kENTC7yHwxQ%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAL8ugEeYP_%2BPViEKrKpkKYEUQ017SMheqdDeAG7Hc%3DoKMjHe3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone crashing during thunderstorms!

[Graham Haddock]

The PMIC in the BeagleBone will go into shutdown, if the DC supply voltage
goes below 4.5 Volts, or above 5.5 Volts, even for a few milliseconds.

In use it should be held between 4.75 and 5.25, so you have some margin.

If the "lights flickered" then the power supply for the BBB did not have to
shut down or loose power, just loose regulation enough to go below 4.5 or
above 5.5.
The BBB is more sensitive than a lot of devices in that respect.

--- Graham

==

On Thu, Jun 30, 2016 at 3:54 PM, William Hermans  wrote:

> But yeah have a look at this:
> https://plus.google.com/106867156582775247949/posts/gFPzDcwyWCs The
> second image on that post is a really good close up, of what happens to
> equipment out here once in a while ;)
>
> On Thu, Jun 30, 2016 at 1:40 PM, William Hermans 
> wrote:
>
>> Wally, why don't you put shielding around your beaglebone, and see if it
>> happens next time.
>>
>> We've seen very similar reset situations here with PTP WIFI routers ( WDS
>> ), from very close lightning strikes we get here every year this time of
>> year. Yet, none of our beaglebone's have been affected.
>>
>> So what's the difference between you, and us ? We live inside a 80' x
>> 100' steel building. In other words, all our equipment is shielded, except
>> the PTP routers which are outside of the building . . .
>>
>> On Thu, Jun 30, 2016 at 1:30 PM, Gerald Coley 
>> wrote:
>>
>>> So, on this crashDoes it basically reset or just stop? How do you
>>> recover?
>>>
>>> Gerald
>>>
>>>
>>> On Thu, Jun 30, 2016 at 3:14 PM, Wally Bkg 
>>> wrote:
>>>
 "Well, I don't know where to start. A detailed diagram of the entire
 system hookup would help.

 Gerald"

 Being in active use for ~25 years and hooked to a variety of computers
 as the years have passed, its never been a problem, but the best I could do
 would be a scan of the diagrams I've built it from.  Its very repetitive,
 four basic interface circuit designs repeated 2, 4, 8, 16 times.  But I may
 get desperate enough to do this, eventually.

 But it acted as if the power button had been held down and just shut
 off, and there was minimal disturbance to lights (mix of incandescent, CF,
 and LED) and the various USPes around the house, so I'm thinking maybe EMP
 sensitivity in the power controller chip.  Its an old house (built circa
 1950), but this outlet is one that I ran a 12ga stranded wire straight from
 the outlet to the grounding rod at the service entrance when we first moved
 in to give me a good ground back in the days I did a lot of hardware work
 -- remember the days of wire-wrapped S-100 bus prototypes :)

 OTOH, as I've upgraded the security cameras to HD I've reused the SD
 camera wiring to add additional PIR motion detectors, and I just discovered
 (after posting this thread) I'd one added PIR unintentionally powered from
 a different UPS (but they are all on the same breaker and safety ground
 connection), so I'll see if it happens again.  This had been the case for
 the first thunderstorm crash a few months ago as well.

 --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to beagleboard+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/beagleboard/6cc15654-ade8-4aea-821b-c7bed75f5575%40googlegroups.com
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> --
>>> Gerald
>>>
>>> ger...@beagleboard.org
>>> http://beagleboard.org/
>>> gcol...@emprodesign.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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Be95AW5w7o5gwcyvnULgy_3cvVqOVMOmj30g-P5tJF3Ag%40mail.gmail.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/l8hri0SzSKE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> 

[beagleboard] USB ACM device problem

[mark . vinson22]

I am having problems porting a Linux C++ program to the Beaglebone Black 
(BBB) Debian platform (uname -r shows 3.8.13-bone47) from an old Linux 
Intel laptop running Debian (uname -r shows 3.16.0-4-686-pae). The program 
polls a custom analog to digital conversion board over a USB CDC data link, 
moving about 230K bytes per second. The custom board provides an interface 
via a PIC CDC RS-232 emulator (Microchip Technology). The C++ program uses 
simple Linux open(2), read(2), and write(2) for data retrieval. The custom 
board shows up as in dmesg as "ttyACM0: USB ACM device" on both the BBB and 
the old Debian laptop.

The program runs very well on the old Debian laptop. But, just a few 
hundred bytes trickle in before a .3 second timeout from the BBB after a 
very slow start. It acts as it there is an interrupt problem.

I am early in the troubleshooting process and want to see if anyone has 
ideas about where I should look first. I have duplicated the problem on 
several BBBs. I have spend some time on web searches and see similar 
problems with solutions, but have found nothing that helps so far.

I am new to Linux, the BBB platform, and have never posted a request for 
help before, so please don't underestimate my ignorance.

Thoughts??

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/78a9dbff-ad2f-4390-a643-67faa1886e0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW console packages?

[Robert Nelson]

Hi Mark,

On Thu, Jun 30, 2016 at 4:26 PM, Mark Grosen  wrote:
> I got a new BB Green Wireless. I prefer the smaller console Debian image,
> but it appears to not ship WL8 support. What packages do I need to add to
> get the WL8 WiFi to work? WL8 Bluetooth? I tried adding the following:
> * wireless-tools
> * firmware-ti-connectivity
> * ti-wlconf
> While booting, the firmware for WL8 cannot be found:
> [   12.330260] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl18xx-conf.bin failed with error -2
> [   20.786201] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> There are various wl128x-fw-5*.bin files in /lib/firmware/ti-connectivity. I
> thought the defaults should work without the wl18xx-conf.bin file.
>
> debian@beaglebone:/lib/firmware/ti-connectivity$ uname -a
> Linux beaglebone 4.4.12-ti-r31 #1 SMP Thu Jun 16 18:48:27 UTC 2016 armv7l
> GNU/Linux
> debian@beaglebone:/lib/firmware/ti-connectivity$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2016-06-19

bb-wl18xx-firmware

details:

firmware for both the wifi/bluetooth:

https://github.com/rcn-ee/repos/tree/master/bb-wl18xx-firmware/suite/jessie/debian

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYihAWVKkxY8i25ft1Yy548xA4FebSZVHk2kENTC7yHwxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBGW console packages?

[Mark Grosen]

I got a new BB Green Wireless. I prefer the smaller console Debian image,
but it appears to not ship WL8 support. What packages do I need to add to
get the WL8 WiFi to work? WL8 Bluetooth? I tried adding the following:
* wireless-tools
* firmware-ti-connectivity
* ti-wlconf
While booting, the firmware for WL8 cannot be found:
[   12.330260] wl18xx_driver wl18xx.2.auto: Direct firmware load for
ti-connectivity/wl18xx-conf.bin failed with error -2
[   20.786201] wl18xx_driver wl18xx.2.auto: Direct firmware load for
ti-connectivity/wl18xx-fw-4.bin failed with error -2
There are various wl128x-fw-5*.bin files in /lib/firmware/ti-connectivity.
I thought the defaults should work without the wl18xx-conf.bin file.

debian@beaglebone:/lib/firmware/ti-connectivity$ uname -a
Linux beaglebone 4.4.12-ti-r31 #1 SMP Thu Jun 16 18:48:27 UTC 2016 armv7l
GNU/Linux
debian@beaglebone:/lib/firmware/ti-connectivity$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-06-19


Thanks,
Mark

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

Re: [beagleboard] Support for BBB kernel

[Robert Nelson]

On Thu, Jun 30, 2016 at 3:55 PM, Greg Wilson-Lindberg
 wrote:
> Robert,
> How do I force a make clean on yakbuild?

./build_kernel.sh

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjJ7pWWTmyCUyWL4nvPjztDfJEQ%3DTUkrY1U07ne%3DokzPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Support for BBB kernel

[Greg Wilson-Lindberg]

Robert,
How do I force a make clean on yakbuild?

Regards,

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3359df0c-adee-4d31-a528-111a3525a258%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone crashing during thunderstorms!

[William Hermans]

But yeah have a look at this:
https://plus.google.com/106867156582775247949/posts/gFPzDcwyWCs The second
image on that post is a really good close up, of what happens to equipment
out here once in a while ;)

On Thu, Jun 30, 2016 at 1:40 PM, William Hermans  wrote:

> Wally, why don't you put shielding around your beaglebone, and see if it
> happens next time.
>
> We've seen very similar reset situations here with PTP WIFI routers ( WDS
> ), from very close lightning strikes we get here every year this time of
> year. Yet, none of our beaglebone's have been affected.
>
> So what's the difference between you, and us ? We live inside a 80' x 100'
> steel building. In other words, all our equipment is shielded, except the
> PTP routers which are outside of the building . . .
>
> On Thu, Jun 30, 2016 at 1:30 PM, Gerald Coley 
> wrote:
>
>> So, on this crashDoes it basically reset or just stop? How do you
>> recover?
>>
>> Gerald
>>
>>
>> On Thu, Jun 30, 2016 at 3:14 PM, Wally Bkg  wrote:
>>
>>> "Well, I don't know where to start. A detailed diagram of the entire
>>> system hookup would help.
>>>
>>> Gerald"
>>>
>>> Being in active use for ~25 years and hooked to a variety of computers
>>> as the years have passed, its never been a problem, but the best I could do
>>> would be a scan of the diagrams I've built it from.  Its very repetitive,
>>> four basic interface circuit designs repeated 2, 4, 8, 16 times.  But I may
>>> get desperate enough to do this, eventually.
>>>
>>> But it acted as if the power button had been held down and just shut
>>> off, and there was minimal disturbance to lights (mix of incandescent, CF,
>>> and LED) and the various USPes around the house, so I'm thinking maybe EMP
>>> sensitivity in the power controller chip.  Its an old house (built circa
>>> 1950), but this outlet is one that I ran a 12ga stranded wire straight from
>>> the outlet to the grounding rod at the service entrance when we first moved
>>> in to give me a good ground back in the days I did a lot of hardware work
>>> -- remember the days of wire-wrapped S-100 bus prototypes :)
>>>
>>> OTOH, as I've upgraded the security cameras to HD I've reused the SD
>>> camera wiring to add additional PIR motion detectors, and I just discovered
>>> (after posting this thread) I'd one added PIR unintentionally powered from
>>> a different UPS (but they are all on the same breaker and safety ground
>>> connection), so I'll see if it happens again.  This had been the case for
>>> the first thunderstorm crash a few months ago as well.
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/beagleboard/6cc15654-ade8-4aea-821b-c7bed75f5575%40googlegroups.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Gerald
>>
>> ger...@beagleboard.org
>> http://beagleboard.org/
>> gcol...@emprodesign.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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Be95AW5w7o5gwcyvnULgy_3cvVqOVMOmj30g-P5tJF3Ag%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORrnE%2BbWWhr6soH1S6XOecSCHshoysY9aOO_AajN_S-TEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone crashing during thunderstorms!

[William Hermans]

Wally, why don't you put shielding around your beaglebone, and see if it
happens next time.

We've seen very similar reset situations here with PTP WIFI routers ( WDS
), from very close lightning strikes we get here every year this time of
year. Yet, none of our beaglebone's have been affected.

So what's the difference between you, and us ? We live inside a 80' x 100'
steel building. In other words, all our equipment is shielded, except the
PTP routers which are outside of the building . . .

On Thu, Jun 30, 2016 at 1:30 PM, Gerald Coley 
wrote:

> So, on this crashDoes it basically reset or just stop? How do you
> recover?
>
> Gerald
>
>
> On Thu, Jun 30, 2016 at 3:14 PM, Wally Bkg  wrote:
>
>> "Well, I don't know where to start. A detailed diagram of the entire
>> system hookup would help.
>>
>> Gerald"
>>
>> Being in active use for ~25 years and hooked to a variety of computers as
>> the years have passed, its never been a problem, but the best I could do
>> would be a scan of the diagrams I've built it from.  Its very repetitive,
>> four basic interface circuit designs repeated 2, 4, 8, 16 times.  But I may
>> get desperate enough to do this, eventually.
>>
>> But it acted as if the power button had been held down and just shut off,
>> and there was minimal disturbance to lights (mix of incandescent, CF, and
>> LED) and the various USPes around the house, so I'm thinking maybe EMP
>> sensitivity in the power controller chip.  Its an old house (built circa
>> 1950), but this outlet is one that I ran a 12ga stranded wire straight from
>> the outlet to the grounding rod at the service entrance when we first moved
>> in to give me a good ground back in the days I did a lot of hardware work
>> -- remember the days of wire-wrapped S-100 bus prototypes :)
>>
>> OTOH, as I've upgraded the security cameras to HD I've reused the SD
>> camera wiring to add additional PIR motion detectors, and I just discovered
>> (after posting this thread) I'd one added PIR unintentionally powered from
>> a different UPS (but they are all on the same breaker and safety ground
>> connection), so I'll see if it happens again.  This had been the case for
>> the first thunderstorm crash a few months ago as well.
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/6cc15654-ade8-4aea-821b-c7bed75f5575%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Gerald
>
> ger...@beagleboard.org
> http://beagleboard.org/
> gcol...@emprodesign.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Be95AW5w7o5gwcyvnULgy_3cvVqOVMOmj30g-P5tJF3Ag%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORov82mRyHmSkFCo6O0Pgy154t8mNRgyaLQzvMAo3zRptw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB startup current

[Gerald Coley]

Sounds like you have it figured out.

Gerald

On Thu, Jun 30, 2016 at 3:23 PM,  wrote:

> You are sure "all capacitor"?
> I think TPS has no capability to flow trough more than 1A even in peek,
> therefore capacitor after TPC cannot generate 4A peak!?
> Only capacitor charged directly in this phase is C2.
>
> But only capacitor which can generate 4A peak is C34.
> So TPS can flow trough more than 4A for a milisec?
>
> I think there is missing som kind of FBB from P1 pin 1 beacuse the
> devlopment focused to USB power.
>
>
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/5ae3f095-d55f-49b5-a311-5a1e34c67d23%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Be5qBvCt6G8roNBN%2B5_3LQLVK4%2BJvJtGb%2Btd9HMWc5DQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB startup current

[kzsoltkzsolt]

You are sure "all capacitor"?
I think TPS has no capability to flow trough more than 1A even in peek, 
therefore capacitor after TPC cannot generate 4A peak!?
Only capacitor charged directly in this phase is C2.

But only capacitor which can generate 4A peak is C34. 
So TPS can flow trough more than 4A for a milisec?

I think there is missing som kind of FBB from P1 pin 1 beacuse the 
devlopment focused to USB power. 




-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5ae3f095-d55f-49b5-a311-5a1e34c67d23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone crashing during thunderstorms!

[Gerald Coley]

So, on this crashDoes it basically reset or just stop? How do you
recover?

Gerald


On Thu, Jun 30, 2016 at 3:14 PM, Wally Bkg  wrote:

> "Well, I don't know where to start. A detailed diagram of the entire
> system hookup would help.
>
> Gerald"
>
> Being in active use for ~25 years and hooked to a variety of computers as
> the years have passed, its never been a problem, but the best I could do
> would be a scan of the diagrams I've built it from.  Its very repetitive,
> four basic interface circuit designs repeated 2, 4, 8, 16 times.  But I may
> get desperate enough to do this, eventually.
>
> But it acted as if the power button had been held down and just shut off,
> and there was minimal disturbance to lights (mix of incandescent, CF, and
> LED) and the various USPes around the house, so I'm thinking maybe EMP
> sensitivity in the power controller chip.  Its an old house (built circa
> 1950), but this outlet is one that I ran a 12ga stranded wire straight from
> the outlet to the grounding rod at the service entrance when we first moved
> in to give me a good ground back in the days I did a lot of hardware work
> -- remember the days of wire-wrapped S-100 bus prototypes :)
>
> OTOH, as I've upgraded the security cameras to HD I've reused the SD
> camera wiring to add additional PIR motion detectors, and I just discovered
> (after posting this thread) I'd one added PIR unintentionally powered from
> a different UPS (but they are all on the same breaker and safety ground
> connection), so I'll see if it happens again.  This had been the case for
> the first thunderstorm crash a few months ago as well.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/6cc15654-ade8-4aea-821b-c7bed75f5575%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Be95AW5w7o5gwcyvnULgy_3cvVqOVMOmj30g-P5tJF3Ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Testing usb webcam, out of space during cheese installation

[Wally Bkg]

I would try to dd the eMMC to an 8GB or larger SD card, and then boot it and 
run grow_partition.sh after you boot it.  I think this would be faster that 
starting over unless you've not changed much from the "stock" image.

I've never had much luck with cheese, sounds like you are familiar with it, but 
I find fswebcam more useful.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/691a9422-ec6c-4d7f-b40a-afd438d2b7e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone crashing during thunderstorms!

[Wally Bkg]

"Well, I don't know where to start. A detailed diagram of the entire system 
hookup would help.

Gerald"

Being in active use for ~25 years and hooked to a variety of computers as the 
years have passed, its never been a problem, but the best I could do would be a 
scan of the diagrams I've built it from.  Its very repetitive, four basic 
interface circuit designs repeated 2, 4, 8, 16 times.  But I may get desperate 
enough to do this, eventually.

But it acted as if the power button had been held down and just shut off, and 
there was minimal disturbance to lights (mix of incandescent, CF, and LED) and 
the various USPes around the house, so I'm thinking maybe EMP sensitivity in 
the power controller chip.  Its an old house (built circa 1950), but this 
outlet is one that I ran a 12ga stranded wire straight from the outlet to the 
grounding rod at the service entrance when we first moved in to give me a good 
ground back in the days I did a lot of hardware work -- remember the days of 
wire-wrapped S-100 bus prototypes :)

OTOH, as I've upgraded the security cameras to HD I've reused the SD camera 
wiring to add additional PIR motion detectors, and I just discovered (after 
posting this thread) I'd one added PIR unintentionally powered from a different 
UPS (but they are all on the same breaker and safety ground connection), so 
I'll see if it happens again.  This had been the case for the first 
thunderstorm crash a few months ago as well.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6cc15654-ade8-4aea-821b-c7bed75f5575%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

[Robert Nelson]

On Thu, Jun 30, 2016 at 1:00 PM,   wrote:
> I was actually using 4.4.9-ti-rt-r26 and v5.0 of the pru software package
> when it did not load the rpmsg_pru.
>
> On Friday, July 1, 2016 at 1:46:40 AM UTC+8, john3909 wrote:
>>
>> Wonderful. If you change to the V4.4 kernel, you must update to PRU V5.0
>> examples because there is a change from mailbox to interrupt event.

r31 was the first v4.4.x release with interrupt events, r32 had a fix,
so upgrade to:

4.4.12-ti-r32/4.4.12-ti-rt-r32

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjv%3DekwT7i8%2B0hjWmK3JP8aAR4_0XCGqXkVNKUBE_4Fgw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] wrong date in log file wtmp

[William Hermans]

One could even 'speak' English when posting to the forums heh ;)

fake-hwclock *package* *if* one exists in ubuntu ;)

On Thu, Jun 30, 2016 at 10:43 AM, William Hermans  wrote:

> However, one *could* use the fake-hwclock papckage is one exists in
> Ubuntu. Debian has this package, but not positive about Ubuntu.
>
> On Thu, Jun 30, 2016 at 8:28 AM, Mike  wrote:
>
>> On 06/30/2016 10:43 AM, Henry van Gestel wrote:
>>
>> Running ubuntu on BBB
>> *ubuntu@ubuntu-armhf:/var/log$ uname -a*
>> *Linux ubuntu-armhf 3.14.4.1-bone-armhf.com
>>  #1 SMP Tue Jun 3 12:37:22 UTC 2014 armv7l
>> armv7l armv7l GNU/Linux*
>>
>> when doing a " last -x reboot" I get :
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16964+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16963+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16962+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16961+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16960+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16959+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16958+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16957+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16956+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16955+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16954+05:59*
>> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
>> (16954+05:59*
>>
>> the date of the system is correct:
>>
>>
>> *ubuntu@ubuntu-armhf:/var/log$ date *
>> *Thu Jun 30 16:41:00 CEST 2016*
>>
>> the date filedate of /var/log/wtmp is also correct
>>
>> *-rw-rw-r--  1 utmp 239232 Jun 30 15:42 wtmp*
>>
>> *What could be the reason of getting not the correct output ?*
>>
>>
>> BBB doesn't have a battery backed RTC...
>>
>> Mike
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/a027b4a8-0fb1-a900-f976-46ca505aad93%40gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORp6dkM%2BY685AqmSLgkGPOw7m%2BJm1C_8wmvXppepb2aGkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

[John Syne]

Then I’m wondering if Robert had pulled in these changes from the 
https://git.ti.com/rpmsg  V4.4 repo. If not, then the 
V4.0.2 examples should work fine. 

Regards,
John




> On Jun 30, 2016, at 11:00 AM, engkan2...@gmail.com wrote:
> 
> I was actually using 4.4.9-ti-rt-r26 and v5.0 of the pru software package 
> when it did not load the rpmsg_pru.
> 
> On Friday, July 1, 2016 at 1:46:40 AM UTC+8, john3909 wrote:
> Wonderful. If you change to the V4.4 kernel, you must update to PRU V5.0 
> examples because there is a change from mailbox to interrupt event. 
> 
> Regards,
> John
> 
> 
> 
> 
>> On Jun 30, 2016, at 8:23 AM, engka...@gmail.com  wrote:
>> 
>> Hi John!
>> 
>> It is working now. I tried 4.1 and 4.4.9-ti-rt-r25. The problem was with the 
>> version of the pru software package. I changed to v4.0.2 and it worked. I 
>> have not tested with the 4.4.9-ti-rt-r26 though.
>> 
>> On Thursday, June 30, 2016 at 11:19:45 PM UTC+8, john3909 wrote:
>> What does lsmod show?
>> 
>> Regards,
>> John
>> 
>> 
>> 
>> 
>>> On Jun 28, 2016, at 6:55 AM, engka...@gmail.com <> wrote:
>>> 
>>> I've changed my kernel to the same version as the poster (I'm using ubuntu).
>>> I still don't see the device in /dev.
>>> 
>>> [   17.581262] pru-rproc 4a338000.pru1: sysevt-to-ch[18] -> 3
>>> [   17.581274] pru-rproc 4a338000.pru1: sysevt-to-ch[19] -> 1
>>> [   17.581286] pru-rproc 4a338000.pru1: skip intr mapping for chnl 0
>>> [   17.581297] pru-rproc 4a338000.pru1: chnl-to-host[1] -> 1
>>> [   17.581308] pru-rproc 4a338000.pru1: skip intr mapping for chnl 2
>>> [   17.581319] pru-rproc 4a338000.pru1: chnl-to-host[3] -> 3
>>> [   17.581329] pru-rproc 4a338000.pru1: skip intr mapping for chnl 4
>>> [   17.581340] pru-rproc 4a338000.pru1: skip intr mapping for chnl 5
>>> [   17.581350] pru-rproc 4a338000.pru1: skip intr mapping for chnl 6
>>> [   17.581361] pru-rproc 4a338000.pru1: skip intr mapping for chnl 7
>>> [   17.581371] pru-rproc 4a338000.pru1: skip intr mapping for chnl 8
>>> [   17.581382] pru-rproc 4a338000.pru1: skip intr mapping for chnl 9
>>> [   17.581397] pruss-rproc 4a30.pruss: SYSEV18 -> CH3 (CMR4 0x0003)
>>> [   17.581410] pruss-rproc 4a30.pruss: SYSEV19 -> CH1 (CMR4 0x0103)
>>> [   17.581424] pruss-rproc 4a30.pruss: CH1 -> HOST1 (HMR0 0x0100)
>>> [   17.581436] pruss-rproc 4a30.pruss: CH3 -> HOST3 (HMR0 0x03000100)
>>> [   17.581449] pruss-rproc 4a30.pruss: configured system_events = 
>>> 0x000c intr_channels = 0x000a host_intr = 0x000a
>>> [   17.581461]  remoteproc2: starting PRU1: entry-point = 0x0
>>> [   17.581471]  remoteproc2: remote processor 4a338000.pru1 is now up
>>> [   17.661101]  remoteproc2: kicking vqid 0 on PRU1
>>> [   17.663720] virtio_rpmsg_bus virtio0: rpmsg host is online
>>> ubuntu@arm:~$
>>> 
>>> 
>>> 
>>> On Tuesday, March 29, 2016 at 2:40:57 AM UTC+8, john3909 wrote:
>>> Hi Lucas,
>>> 
>>> Good to hear this is working for you. Now for the real work ;-)
>>> 
>>> Regards,
>>> John
>>> 
>>> 
>>> 
>>> 
 On Mar 28, 2016, at 6:10 AM, lucas gmail.com 
 > wrote:
 
 Wow it worked :) Thank you, John! 
 
 Short summary how to get it working: 
 
 1.) Compile PRU_RPMsg_LED0 project in CCS
 2.) Transfer PRU_RPMsg_LED0.out onto beaglebone into the /lib/firmware 
 directory 
 3.) Set symbolic link: sudo ln -s PRU_RPMsg_LED0.out am335x-pru0-fw
 4.) restart
 5.) modprobe virtio_rpmsg_bus
 6.) modprobe rpmsg_pru
 7.) check if /dev/rpmsg_pru30 exists
 8.) echo "r" > /dev/rpmsg_pru30
 9.) Observe red LED light up on PRU_cape :) 
 
 
 On Wednesday, March 23, 2016 at 8:42:50 PM UTC+1, john3909 wrote:
 Don’t include the .ko extension when using modprobe.
 
 Regards,
 John
 
 
 
 
> On Mar 23, 2016, at 9:32 AM, lucas gmail.com 
> > wrote:
> 
> Sorry forgot to copy the error message for the modprobe command: 
> 
> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
> modprobe virtio_rpmsg_bus.ko
> modprobe: FATAL: Module virtio_rpmsg_bus.ko not found.
> 
> On Wednesday, March 23, 2016 at 5:27:12 PM UTC+1, lucas wrote:
> Hi John, 
> 
> thank you very much for your answer. 
> 
> I am using the 4.1.15-ti-rt-r43 kernel. It's the kernel that came with 
> the debian image from the beaglebone website.  
> 
> Only the pruss_remoteproc module seems to be loaded on boot:
> 
> # lsmod
> Module  Size  Used by
> 8021q  17336  0
> garp5975  1 8021q
> mrp 7322  1 8021q
> stp 1911  1 garp
> llc 5257  2 stp,garp
> pruss_remoteproc   15296  2
> omap_rng4358  0
> rng_core7437  1 omap_rng
> 

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

[engkan2kit]

I was actually using 4.4.9-ti-rt-r26 and v5.0 of the pru software package 
when it did not load the rpmsg_pru.

On Friday, July 1, 2016 at 1:46:40 AM UTC+8, john3909 wrote:
>
> Wonderful. If you change to the V4.4 kernel, you must update to PRU V5.0 
> examples because there is a change from mailbox to interrupt event. 
>
> Regards,
> John
>
>
>
>
> On Jun 30, 2016, at 8:23 AM, engka...@gmail.com  wrote:
>
> Hi John!
>
> It is working now. I tried 4.1 and 4.4.9-ti-rt-r25. The problem was with 
> the version of the pru software package. I changed to v4.0.2 and it worked. 
> I have not tested with the 4.4.9-ti-rt-r26 though.
>
> On Thursday, June 30, 2016 at 11:19:45 PM UTC+8, john3909 wrote:
>>
>> What does lsmod show?
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Jun 28, 2016, at 6:55 AM, engka...@gmail.com wrote:
>>
>> I've changed my kernel to the same version as the poster (I'm using 
>> ubuntu).
>> I still don't see the device in /dev.
>>
>> [   17.581262] pru-rproc 4a338000.pru1: sysevt-to-ch[18] -> 3
>> [   17.581274] pru-rproc 4a338000.pru1: sysevt-to-ch[19] -> 1
>> [   17.581286] pru-rproc 4a338000.pru1: skip intr mapping for chnl 0
>> [   17.581297] pru-rproc 4a338000.pru1: chnl-to-host[1] -> 1
>> [   17.581308] pru-rproc 4a338000.pru1: skip intr mapping for chnl 2
>> [   17.581319] pru-rproc 4a338000.pru1: chnl-to-host[3] -> 3
>> [   17.581329] pru-rproc 4a338000.pru1: skip intr mapping for chnl 4
>> [   17.581340] pru-rproc 4a338000.pru1: skip intr mapping for chnl 5
>> [   17.581350] pru-rproc 4a338000.pru1: skip intr mapping for chnl 6
>> [   17.581361] pru-rproc 4a338000.pru1: skip intr mapping for chnl 7
>> [   17.581371] pru-rproc 4a338000.pru1: skip intr mapping for chnl 8
>> [   17.581382] pru-rproc 4a338000.pru1: skip intr mapping for chnl 9
>> [   17.581397] pruss-rproc 4a30.pruss: SYSEV18 -> CH3 (CMR4 
>> 0x0003)
>> [   17.581410] pruss-rproc 4a30.pruss: SYSEV19 -> CH1 (CMR4 
>> 0x0103)
>> [   17.581424] pruss-rproc 4a30.pruss: CH1 -> HOST1 (HMR0 0x0100)
>> [   17.581436] pruss-rproc 4a30.pruss: CH3 -> HOST3 (HMR0 0x03000100)
>> [   17.581449] pruss-rproc 4a30.pruss: configured system_events = 
>> 0x000c intr_channels = 0x000a host_intr = 0x000a
>> [   17.581461]  remoteproc2: starting PRU1: entry-point = 0x0
>> [   17.581471]  remoteproc2: remote processor 4a338000.pru1 is now up
>> [   17.661101]  remoteproc2: kicking vqid 0 on PRU1
>> [   17.663720] virtio_rpmsg_bus virtio0: rpmsg host is online
>> ubuntu@arm:~$
>>
>>
>>
>> On Tuesday, March 29, 2016 at 2:40:57 AM UTC+8, john3909 wrote:
>>>
>>> Hi Lucas,
>>>
>>> Good to hear this is working for you. Now for the real work ;-)
>>>
>>> Regards,
>>> John
>>>
>>>
>>>
>>>
>>> On Mar 28, 2016, at 6:10 AM, lucas  wrote:
>>>
>>> Wow it worked :) Thank you, John! 
>>>
>>> Short summary how to get it working: 
>>>
>>> 1.) Compile PRU_RPMsg_LED0 project in CCS
>>> 2.) Transfer PRU_RPMsg_LED0.out onto beaglebone into the /lib/firmware 
>>> directory 
>>> 3.) Set symbolic link: sudo ln -s PRU_RPMsg_LED0.out am335x-pru0-fw
>>> 4.) restart
>>> 5.) modprobe virtio_rpmsg_bus
>>> 6.) modprobe rpmsg_pru
>>> 7.) check if /dev/rpmsg_pru30 exists
>>> 8.) echo "r" > /dev/rpmsg_pru30
>>> 9.) Observe red LED light up on PRU_cape :) 
>>>
>>>
>>> On Wednesday, March 23, 2016 at 8:42:50 PM UTC+1, john3909 wrote:

 Don’t include the .ko extension when using modprobe.

 Regards,
 John




 On Mar 23, 2016, at 9:32 AM, lucas  wrote:

 Sorry forgot to copy the error message for the modprobe command: 

 root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
 modprobe virtio_rpmsg_bus.ko
 modprobe: FATAL: Module virtio_rpmsg_bus.ko not found.

 On Wednesday, March 23, 2016 at 5:27:12 PM UTC+1, lucas wrote:
>
> Hi John, 
>
> thank you very much for your answer. 
>
> I am using the 4.1.15-ti-rt-r43 kernel. It's the kernel that came with 
> the debian image from the beaglebone website.  
>
> Only the pruss_remoteproc module seems to be loaded on boot:
>
> # lsmod
> Module  Size  Used by
> 8021q  17336  0
> garp5975  1 8021q
> mrp 7322  1 8021q
> stp 1911  1 garp
> llc 5257  2 stp,garp
> pruss_remoteproc   15296  2
> omap_rng4358  0
> rng_core7437  1 omap_rng
> usb_f_acm   7180  1
> u_serial   10596  3 usb_f_acm
> usb_f_rndis22734  1
> g_multi 5316  0
> usb_f_mass_storage 42745  2 g_multi
> u_ether12028  2 usb_f_rndis,g_multi
> libcomposite   43810  4 
> usb_f_acm,usb_f_rndis,g_multi,usb_f_mass_storage
> snd_soc_davinci_mcasp17266  0
> snd_soc_edma  

Re: [beagleboard] Original BeagleBone Dimensions. Anybody Know?!?!!?!

[Walter King]

Fantastic. Just what I needed. 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/41e145f4-42c9-439f-8151-70c81818613b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

[John Syne]

Wonderful. If you change to the V4.4 kernel, you must update to PRU V5.0 
examples because there is a change from mailbox to interrupt event. 

Regards,
John




> On Jun 30, 2016, at 8:23 AM, engkan2...@gmail.com wrote:
> 
> Hi John!
> 
> It is working now. I tried 4.1 and 4.4.9-ti-rt-r25. The problem was with the 
> version of the pru software package. I changed to v4.0.2 and it worked. I 
> have not tested with the 4.4.9-ti-rt-r26 though.
> 
> On Thursday, June 30, 2016 at 11:19:45 PM UTC+8, john3909 wrote:
> What does lsmod show?
> 
> Regards,
> John
> 
> 
> 
> 
>> On Jun 28, 2016, at 6:55 AM, engka...@gmail.com  wrote:
>> 
>> I've changed my kernel to the same version as the poster (I'm using ubuntu).
>> I still don't see the device in /dev.
>> 
>> [   17.581262] pru-rproc 4a338000.pru1: sysevt-to-ch[18] -> 3
>> [   17.581274] pru-rproc 4a338000.pru1: sysevt-to-ch[19] -> 1
>> [   17.581286] pru-rproc 4a338000.pru1: skip intr mapping for chnl 0
>> [   17.581297] pru-rproc 4a338000.pru1: chnl-to-host[1] -> 1
>> [   17.581308] pru-rproc 4a338000.pru1: skip intr mapping for chnl 2
>> [   17.581319] pru-rproc 4a338000.pru1: chnl-to-host[3] -> 3
>> [   17.581329] pru-rproc 4a338000.pru1: skip intr mapping for chnl 4
>> [   17.581340] pru-rproc 4a338000.pru1: skip intr mapping for chnl 5
>> [   17.581350] pru-rproc 4a338000.pru1: skip intr mapping for chnl 6
>> [   17.581361] pru-rproc 4a338000.pru1: skip intr mapping for chnl 7
>> [   17.581371] pru-rproc 4a338000.pru1: skip intr mapping for chnl 8
>> [   17.581382] pru-rproc 4a338000.pru1: skip intr mapping for chnl 9
>> [   17.581397] pruss-rproc 4a30.pruss: SYSEV18 -> CH3 (CMR4 0x0003)
>> [   17.581410] pruss-rproc 4a30.pruss: SYSEV19 -> CH1 (CMR4 0x0103)
>> [   17.581424] pruss-rproc 4a30.pruss: CH1 -> HOST1 (HMR0 0x0100)
>> [   17.581436] pruss-rproc 4a30.pruss: CH3 -> HOST3 (HMR0 0x03000100)
>> [   17.581449] pruss-rproc 4a30.pruss: configured system_events = 
>> 0x000c intr_channels = 0x000a host_intr = 0x000a
>> [   17.581461]  remoteproc2: starting PRU1: entry-point = 0x0
>> [   17.581471]  remoteproc2: remote processor 4a338000.pru1 is now up
>> [   17.661101]  remoteproc2: kicking vqid 0 on PRU1
>> [   17.663720] virtio_rpmsg_bus virtio0: rpmsg host is online
>> ubuntu@arm:~$
>> 
>> 
>> 
>> On Tuesday, March 29, 2016 at 2:40:57 AM UTC+8, john3909 wrote:
>> Hi Lucas,
>> 
>> Good to hear this is working for you. Now for the real work ;-)
>> 
>> Regards,
>> John
>> 
>> 
>> 
>> 
>>> On Mar 28, 2016, at 6:10 AM, lucas gmail.com 
>>> > wrote:
>>> 
>>> Wow it worked :) Thank you, John! 
>>> 
>>> Short summary how to get it working: 
>>> 
>>> 1.) Compile PRU_RPMsg_LED0 project in CCS
>>> 2.) Transfer PRU_RPMsg_LED0.out onto beaglebone into the /lib/firmware 
>>> directory 
>>> 3.) Set symbolic link: sudo ln -s PRU_RPMsg_LED0.out am335x-pru0-fw
>>> 4.) restart
>>> 5.) modprobe virtio_rpmsg_bus
>>> 6.) modprobe rpmsg_pru
>>> 7.) check if /dev/rpmsg_pru30 exists
>>> 8.) echo "r" > /dev/rpmsg_pru30
>>> 9.) Observe red LED light up on PRU_cape :) 
>>> 
>>> 
>>> On Wednesday, March 23, 2016 at 8:42:50 PM UTC+1, john3909 wrote:
>>> Don’t include the .ko extension when using modprobe.
>>> 
>>> Regards,
>>> John
>>> 
>>> 
>>> 
>>> 
 On Mar 23, 2016, at 9:32 AM, lucas gmail.com 
 > wrote:
 
 Sorry forgot to copy the error message for the modprobe command: 
 
 root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
 modprobe virtio_rpmsg_bus.ko
 modprobe: FATAL: Module virtio_rpmsg_bus.ko not found.
 
 On Wednesday, March 23, 2016 at 5:27:12 PM UTC+1, lucas wrote:
 Hi John, 
 
 thank you very much for your answer. 
 
 I am using the 4.1.15-ti-rt-r43 kernel. It's the kernel that came with the 
 debian image from the beaglebone website.  
 
 Only the pruss_remoteproc module seems to be loaded on boot:
 
 # lsmod
 Module  Size  Used by
 8021q  17336  0
 garp5975  1 8021q
 mrp 7322  1 8021q
 stp 1911  1 garp
 llc 5257  2 stp,garp
 pruss_remoteproc   15296  2
 omap_rng4358  0
 rng_core7437  1 omap_rng
 usb_f_acm   7180  1
 u_serial   10596  3 usb_f_acm
 usb_f_rndis22734  1
 g_multi 5316  0
 usb_f_mass_storage 42745  2 g_multi
 u_ether12028  2 usb_f_rndis,g_multi
 libcomposite   43810  4 
 usb_f_acm,usb_f_rndis,g_multi,usb_f_mass_storage
 snd_soc_davinci_mcasp17266  0
 snd_soc_edma1150  1 snd_soc_davinci_mcasp
 spi_omap2_mcspi10681  0
 uio_pdrv_genirq 3521  0
 
 Although the other modules do exist in the driver 

[beagleboard] Original BeagleBone Dimensions. Anybody Know?!?!!?!

[Walter King]

Hello all!

I need to create a mounting plate for an original BeagleBone (the white one 
that has been discontinued). However, I cannot find mechanical drawings for 
it anywhere and will not have access to the board until after the mount has 
been fabricated. Does anyone know what the diameter of the mounting holes 
are and the distances between them? Is it the same as on the BeagleBone 
Blacks? Thank you in Advance!!

Walter 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/96c4648c-18c1-4779-8f2d-7634c28033a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] wrong date in log file wtmp

[William Hermans]

However, one *could* use the fake-hwclock papckage is one exists in Ubuntu.
Debian has this package, but not positive about Ubuntu.

On Thu, Jun 30, 2016 at 8:28 AM, Mike  wrote:

> On 06/30/2016 10:43 AM, Henry van Gestel wrote:
>
> Running ubuntu on BBB
> *ubuntu@ubuntu-armhf:/var/log$ uname -a*
> *Linux ubuntu-armhf 3.14.4.1-bone-armhf.com
>  #1 SMP Tue Jun 3 12:37:22 UTC 2014 armv7l
> armv7l armv7l GNU/Linux*
>
> when doing a " last -x reboot" I get :
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16964+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16963+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16962+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16961+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16960+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16959+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16958+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16957+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16956+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16955+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16954+05:59*
> *reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00
> (16954+05:59*
>
> the date of the system is correct:
>
>
> *ubuntu@ubuntu-armhf:/var/log$ date *
> *Thu Jun 30 16:41:00 CEST 2016*
>
> the date filedate of /var/log/wtmp is also correct
>
> *-rw-rw-r--  1 utmp 239232 Jun 30 15:42 wtmp*
>
> *What could be the reason of getting not the correct output ?*
>
>
> BBB doesn't have a battery backed RTC...
>
> Mike
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/a027b4a8-0fb1-a900-f976-46ca505aad93%40gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORrY_w0uz4fosKjUgWQKEKfyb7Xx%3DWgXQ5B-p8-KKe-iNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Original Beagle Bone Dimensions. Anybody Know?!?!?!

[Gerald Coley]

And it is the same size as the BeagleBone Black.

Gerald


On Thu, Jun 30, 2016 at 12:30 PM,  wrote:

> Hello all!
>
> I need to create a mounting plate for an original BeagleBone (the
> discontinued white boards). Does anyone know the diameter of the mounting
> holes and the distance between them? Are they the same dimensions as on the
> BeagleBone Black? I can't find mechanical drawings for the original
> BeagleBone anywhere. Thank you in advance!!!
>
> Walter
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/ce5c996f-fc24-4f4b-bbfc-c82e13ead317%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK_S%2BcpMaOE8qgqcKtMmLD30W5h_0Fh78EYGN4WAAxCvoKEqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Original Beagle Bone Dimensions. Anybody Know?!?!?!

[walterking103]

Hello all!

I need to create a mounting plate for an original BeagleBone (the 
discontinued white boards). Does anyone know the diameter of the mounting 
holes and the distance between them? Are they the same dimensions as on the 
BeagleBone Black? I can't find mechanical drawings for the original 
BeagleBone anywhere. Thank you in advance!!!

Walter

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ce5c996f-fc24-4f4b-bbfc-c82e13ead317%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Original BeagleBone Dimensions. Anybody Know?!?!!?!

[Gerald Coley]

It is in the System Reference Manual.

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


Gerald


On Thu, Jun 30, 2016 at 12:40 PM, Walter King 
wrote:

> Hello all!
>
> I need to create a mounting plate for an original BeagleBone (the white
> one that has been discontinued). However, I cannot find mechanical drawings
> for it anywhere and will not have access to the board until after the mount
> has been fabricated. Does anyone know what the diameter of the mounting
> holes are and the distances between them? Is it the same as on the
> BeagleBone Blacks? Thank you in Advance!!
>
> Walter
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/96c4648c-18c1-4779-8f2d-7634c28033a6%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Bfzb2GoPAuG2zUvOyOQNuxcpw86wqrLM0AB_yvAzReZOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Trouble enabling DCAN1 on BeagleBone, think I'm close but missing something.

[William Hermans]

Also for Logisupply CAN / Serial cape, you do not load the overlay file
manually. It's done automatically at boot. The same goes for many premade
capes, I'm sure.

On Thu, Jun 30, 2016 at 6:48 AM, Robert Nelson 
wrote:

> On Fri, Jun 24, 2016 at 12:09 PM,  
> wrote:
> > Not sure if you solved this yet...
> >
> > Try this, it worked for me:
> >
> > 1. disable the default overlay on slot 4:
> > sudo sh -c "echo '-4' > /sys/devices/platform/bone_capemgr/slots"
>
> you can just remove cape_universal=enable from /boot/uEnv.txt
>
> >
> > 2. add the CAN cape device
> > sudo sh -c "echo 'BB-CAN1' >
> /sys/devices/platform/bone_capemgr/slots"
> >
> > otherwise, you may get the following error:
> > root@beaglebone:/# sudo sh -c "echo 'BB-CAN1' >
> > /sys/devices/platform/bone_capemgr/slots"
> > [  494.986203] bone_capemgr bone_capemgr: slot #6: BB-CAN1 conflict
> > P9.24 (#4:cape-universaln)
> > [  494.995099] bone_capemgr bone_capemgr: slot #6: Failed
> verification
> > sh: echo: I/O error
>
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOCHtYgMREM%3DsgDPpxEa8HvRcwFN1uBOSjwT%2BZ6_02-Po11Hyg%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORrdH05vXoFaps_v69gi-73x4aWNfOj0TS%2Bd38YE3P1X6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Incorrect device overlay selected during boot

[William Hermans]

Yeah, you're modifying the wrong file.

debian@beaglebone:~/nfs$ cat /boot/uEnv.txt
#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.4.12-ti-r31
#uuid=
#dtb=

##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)



*##BeagleBone Black: HDMI (Audio/Video)
disabled:dtb=am335x-boneblack-emmc-overlay.dtb*
. . .

*dtb=am335x-boneblack-emmc-overlay.dtb *is the line you're after, and it
probably is proceeded by a pound( # ) symbol. So it's commented out. SImply
remove the # to uncomment, and then reboot the board.


On Mon, Jun 27, 2016 at 1:20 PM, richatnstar via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Hi,
>
> My BBB stack has a 4.3" LCD cape -- powerup diagnostics (dmesg) indicated
> the cape was found OK & brightness worked Ok. I was unable to view
> (startup) text on the display. (Ver 4.4.1-bone11). After a few days of
> debug, I found that the MuxPins were not properly updated and were still
> accessing HDMI (not modified as expected). I added an 'echo' into /uEnv.txt
> & discovered that the 'overlay file' was not right - it was the default
> chosen at power-up.
>
> /boot/uEnv.txt has the lines (amongst others)
>
>  dtb=am335x-boneblack-overlay.dtb
>  Disable: HDMI
>
> /uEnv.txt was modified - *fdtfile* was replaced by *dtb*
>
> #loadxfdt=load mmc 0:1 ${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
> loadxfdt=load mmc 0:1 ${fdtaddr} /boot/dtbs/${uname_r}/*${dtb}*
>
> Possibly modifying fdtfile is the appropriate method -- Is there a better
> solution?
>
> thx
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/0da49087-4271-4df2-81f4-e66b763c2ebf%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORpXrYRpqWYD20U5SCGsp6MaA0ig2%2B-LQOAWDXmAwN9aEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: bbb ubuntu displays wrong log date

[Graham]

A BBB does not know what time it actually is, until it has booted to the 
point that it can go out on the Internet and get the actual time.
--- Graham

==

On Thursday, June 30, 2016 at 10:16:31 AM UTC-5, Henry van Gestel wrote:
>
> running Ubuntu on my BBB:
> ubuntu@ubuntu-armhf:/var/log$ uname -a
> Linux ubuntu-armhf 3.14.4.1-bone-armhf.com #1 SMP Tue Jun 3 12:37:22 UTC 
> 2014 armv7l armv7l armv7l GNU/Linux
>
> When I do last I get following output:
> ubuntu@ubuntu-armhf:/var/log$ last -x reboot
> reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 16:49 
> (16982+14:49
> reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
> (16982+05:59
> reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
> (16981+05:59
> reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
> (16981+05:59
> reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
> (16980+05:59
> reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
> (16980+05:59
> reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
> (16979+05:59
> reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
> (16979+05:59
>
> thats not what I expect.
>
> The filedate of /var/log/wtmp is correct:
>
> ubuntu@ubuntu-armhf:/var/log$ ls -algtr wtmp
> -rw-rw-r-- 1 utmp 239232 Jun 30 15:42 wtmp
>
> The date of the system is also correct:
> ubuntu@ubuntu-armhf:/var/log$ date
> Thu Jun 30 16:51:43 CEST 2016
>
>
> What could be the reason of having this output?
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/af697cce-69f9-4a29-a326-b51023d05d40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ti's RPMsg Examples Significantly Changed

[William Hermans]

Personally, I could care less how many people use remoteproc, and I do not
think it's all that important either. I do not recall ever seeing anyone
ask how many people use uio_pruss either. But again, I think it's a moot
point. The better software should win out, and for those who do not agree,
they will use what they want anyhow. No one can stop them.

So who is this person that needs to stop fighting and conform to someone
elses wishes ? Sorry pal, others beliefs aren't a dictatorship, *and* whose
fighting ? Sounds like someone has built this up as something in their own
mind, that it's not.

Also, it does not matter what is mainline, and what isn't. At least in this
context to me it does not. I know that remoteproc really, has nothing to do
specifically with TI hardware. I've seen really cool usages of remoteproc
on multi core applications processors where 1 or more additional cores were
used as bare metal cores. While 1 or more cores were running Linux.
Personally, in my mind that's what remteproc is all about. But what doe
this have to do with a specific bit of hardware that only one company has
in their processors ? Nothing . . .

On Thu, Jun 30, 2016 at 2:11 AM, TJF  wrote:

> Good morning John!
>
> Am Mittwoch, 29. Juni 2016 17:07:05 UTC+2 schrieb john3909:
>>
>> What a silly argument. It is well known that when you don’t have physical
>> security, you don’t have any security. Once you can replace the storage
>> media, you can make the hardware do whatever you want. This is true of your
>> laptop and your servers. Clearly by your argument, you haven’t even begun
>> to understand security.
>>
>
> You're correct, I don't know much about the Linux terminologie and
> definitions. From the Linux point of view, this was evidently a silly
> argument. Do not fred. You're still leading by a two-digit score in this
> discipline.
>
> Does that change much? No, there're still other ways to get firmware on
> the PRUSS. As a matter of fact there are solutions to use the PRUSS from
> user space. No example, because I don't want to continue in publishing "how
> to make a virus" tutorials here. If you don't believe that, just check out
> the libpruio examples. Most of them work with user privilegues, root
> permission is necessary for pinmuxing only.
>
>
>> In addition, you should reframe from impugning a person's motivations or
>> intentions.
>>
>
> It's confusing when you talk to yourself.
>
>
>> If you didn’t know, for stability reasons, Linux do not remove fameworks
>> unless they have been replaced by something better and in most cases the
>> new framework is backward compatible with the new framework.
>>
>
> Obviously there're exceptions. The PRU support is neither better nor
> backward compatible to previous solutions. Oh sorry, not entirely correct:
> indeed it has better support for PRU virus activities, targeting the kernel
> space directly.
>
>
>> No one knows how many developers are using RemoteProc/RPMSG ...
>>
>
> This is an important point! Just a few unquantifiable developers will use
> it, but in the current configuration it endangers all BB systems by default.
>
>
>> so there is no ways that Linus or his deputies would permit the removal
>> of this framework.
>>
>
> Is it mainline? I thought it's a TI feature. Anyhow, mainline isn't
> affected. This safety issue concerns boards with PRUSS, only.
>
>
>> All you can do is attempt to make it better ...
>>
>
> This is making it optional, or at least making PRUSS support optional in
> that framework and disable it by default.
>
>
>> so stop fighting a loosing battle and join me in fixing what you don’t
>> like.
>>
>
> That's a damed good idea. Since here we've to wait for a management
> decision, why don't you use that time for fixing the issue from our March
> discussion? Or at least answer the still open question
> .
>
> BR
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/ee04b094-812b-43d8-b25a-5985a5fba148%40googlegroups.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.
To view this discussion on the web visit 

Re: [beagleboard] wrong date in log file wtmp

[Mike]

On 06/30/2016 10:43 AM, Henry van Gestel wrote:

Running ubuntu on BBB
/ubuntu@ubuntu-armhf:/var/log$ uname -a/
/Linux ubuntu-armhf 3.14.4.1-bone-armhf.com #1 SMP Tue Jun 3 12:37:22 
UTC 2014 armv7l armv7l armv7l GNU/Linux/


when doing a " last -x reboot" I get :
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16964+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16963+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16962+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16961+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16960+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16959+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16958+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16957+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16956+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16955+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16954+05:59/
/reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16954+05:59/


the date of the system is correct:

/ubuntu@ubuntu-armhf:/var/log$ date
/
/Thu Jun 30 16:41:00 CEST 2016/

the date filedate of /var/log/wtmp is also correct

/-rw-rw-r--  1 utmp 239232 Jun 30 15:42 wtmp/
/
/
*What could be the reason of getting not the correct output ?*



BBB doesn't have a battery backed RTC...

Mike

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

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a027b4a8-0fb1-a900-f976-46ca505aad93%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW First Impressions

[jonatan . magnusson]

I have solved it, using hci_uart instead of btwilink. The thread on that 
forum is updated.

Den torsdag 30 juni 2016 kl. 15:25:03 UTC+2 skrev jon...@cmteknik.se:
>
>
> Hi 
>
> The ti-st driver is junk and not required for bluetooth only. 
>> Sorry but that's really all I can say about it. 
>>
>
> I currently have ti-st related problems. I've written about it here: 
> https://e2e.ti.com/support/wireless_connectivity/wilink_wifi_bluetooth/f/307/t/524599
>
> Can you share some information about how to use bluetooth on  BBGW 
> *without* using ti-st?
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2530e19e-9719-42f4-860e-32106f09d76c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

[John Syne]

What does lsmod show?

Regards,
John




> On Jun 28, 2016, at 6:55 AM, engkan2...@gmail.com wrote:
> 
> I've changed my kernel to the same version as the poster (I'm using ubuntu).
> I still don't see the device in /dev.
> 
> [   17.581262] pru-rproc 4a338000.pru1: sysevt-to-ch[18] -> 3
> [   17.581274] pru-rproc 4a338000.pru1: sysevt-to-ch[19] -> 1
> [   17.581286] pru-rproc 4a338000.pru1: skip intr mapping for chnl 0
> [   17.581297] pru-rproc 4a338000.pru1: chnl-to-host[1] -> 1
> [   17.581308] pru-rproc 4a338000.pru1: skip intr mapping for chnl 2
> [   17.581319] pru-rproc 4a338000.pru1: chnl-to-host[3] -> 3
> [   17.581329] pru-rproc 4a338000.pru1: skip intr mapping for chnl 4
> [   17.581340] pru-rproc 4a338000.pru1: skip intr mapping for chnl 5
> [   17.581350] pru-rproc 4a338000.pru1: skip intr mapping for chnl 6
> [   17.581361] pru-rproc 4a338000.pru1: skip intr mapping for chnl 7
> [   17.581371] pru-rproc 4a338000.pru1: skip intr mapping for chnl 8
> [   17.581382] pru-rproc 4a338000.pru1: skip intr mapping for chnl 9
> [   17.581397] pruss-rproc 4a30.pruss: SYSEV18 -> CH3 (CMR4 0x0003)
> [   17.581410] pruss-rproc 4a30.pruss: SYSEV19 -> CH1 (CMR4 0x0103)
> [   17.581424] pruss-rproc 4a30.pruss: CH1 -> HOST1 (HMR0 0x0100)
> [   17.581436] pruss-rproc 4a30.pruss: CH3 -> HOST3 (HMR0 0x03000100)
> [   17.581449] pruss-rproc 4a30.pruss: configured system_events = 
> 0x000c intr_channels = 0x000a host_intr = 0x000a
> [   17.581461]  remoteproc2: starting PRU1: entry-point = 0x0
> [   17.581471]  remoteproc2: remote processor 4a338000.pru1 is now up
> [   17.661101]  remoteproc2: kicking vqid 0 on PRU1
> [   17.663720] virtio_rpmsg_bus virtio0: rpmsg host is online
> ubuntu@arm:~$
> 
> 
> 
> On Tuesday, March 29, 2016 at 2:40:57 AM UTC+8, john3909 wrote:
> Hi Lucas,
> 
> Good to hear this is working for you. Now for the real work ;-)
> 
> Regards,
> John
> 
> 
> 
> 
>> On Mar 28, 2016, at 6:10 AM, lucas gmail.com 
>> > wrote:
>> 
>> Wow it worked :) Thank you, John! 
>> 
>> Short summary how to get it working: 
>> 
>> 1.) Compile PRU_RPMsg_LED0 project in CCS
>> 2.) Transfer PRU_RPMsg_LED0.out onto beaglebone into the /lib/firmware 
>> directory 
>> 3.) Set symbolic link: sudo ln -s PRU_RPMsg_LED0.out am335x-pru0-fw
>> 4.) restart
>> 5.) modprobe virtio_rpmsg_bus
>> 6.) modprobe rpmsg_pru
>> 7.) check if /dev/rpmsg_pru30 exists
>> 8.) echo "r" > /dev/rpmsg_pru30
>> 9.) Observe red LED light up on PRU_cape :) 
>> 
>> 
>> On Wednesday, March 23, 2016 at 8:42:50 PM UTC+1, john3909 wrote:
>> Don’t include the .ko extension when using modprobe.
>> 
>> Regards,
>> John
>> 
>> 
>> 
>> 
>>> On Mar 23, 2016, at 9:32 AM, lucas gmail.com 
>>> > wrote:
>>> 
>>> Sorry forgot to copy the error message for the modprobe command: 
>>> 
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
>>> modprobe virtio_rpmsg_bus.ko
>>> modprobe: FATAL: Module virtio_rpmsg_bus.ko not found.
>>> 
>>> On Wednesday, March 23, 2016 at 5:27:12 PM UTC+1, lucas wrote:
>>> Hi John, 
>>> 
>>> thank you very much for your answer. 
>>> 
>>> I am using the 4.1.15-ti-rt-r43 kernel. It's the kernel that came with the 
>>> debian image from the beaglebone website.  
>>> 
>>> Only the pruss_remoteproc module seems to be loaded on boot:
>>> 
>>> # lsmod
>>> Module  Size  Used by
>>> 8021q  17336  0
>>> garp5975  1 8021q
>>> mrp 7322  1 8021q
>>> stp 1911  1 garp
>>> llc 5257  2 stp,garp
>>> pruss_remoteproc   15296  2
>>> omap_rng4358  0
>>> rng_core7437  1 omap_rng
>>> usb_f_acm   7180  1
>>> u_serial   10596  3 usb_f_acm
>>> usb_f_rndis22734  1
>>> g_multi 5316  0
>>> usb_f_mass_storage 42745  2 g_multi
>>> u_ether12028  2 usb_f_rndis,g_multi
>>> libcomposite   43810  4 
>>> usb_f_acm,usb_f_rndis,g_multi,usb_f_mass_storage
>>> snd_soc_davinci_mcasp17266  0
>>> snd_soc_edma1150  1 snd_soc_davinci_mcasp
>>> spi_omap2_mcspi10681  0
>>> uio_pdrv_genirq 3521  0
>>> 
>>> Although the other modules do exist in the driver directory.
>>> 
>>> ls /lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg
>>> rpmsg_pru.ko  rpmsg-rpc.ko  virtio_rpmsg_bus.ko
>>> 
>>> I cannot modprob the modules:
>>> 
>>> # modprobe virtio_rpmsg_bus.ko
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
>>> modprobe virtio_rpmsg_bus.ko
>>> 
>>> 
>>> But I can use insmod 
>>> 
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# insmod 
>>> virtio_rpmsg_bus.ko
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# lsmod
>>> Module  Size  Used by
>>> virtio_rpmsg_bus   13437  0
>>> 8021q  17336  0

Re: [beagleboard] BBB hangs at Starting Kernel

[Ratan Yadav]

On Wednesday, June 29, 2016 at 8:03:55 PM UTC+5:30, RobertCNelson wrote:
>
> On Wed, Jun 29, 2016 at 9:31 AM, Ratan Yadav  > wrote: 
> > Hi All , 
> > 
> > 
> > After doing a lot of googling , I am turning to this forum . 
> > 
> > I am newbie in Linux and BBB , I am sure this topic might have come 
> multiple 
> > times in this forum but unfortunately those could not resolve my issue . 
> > 
> > I am facing problem while booting from TFTP . 
> > 
> > My kernel is loaded but as soon as it reaches to "Starting kernel" it 
> hangs 
> > up completely . 
> > 
> > Details shown on terminal is as below . 
> > 
> > 
> > U-Boot# setenv serverip 192.168.1.5 
> > U-Boot# tftp 0x8020 uImage-BBB 
> > link up on port 0, speed 100, full duplex 
> > Using cpsw device 
> > TFTP from server 192.168.1.5; our IP address is 192.168.1.7 
> > Filename 'uImage-BBB'. 
> > Load address: 0x8020 
> > Loading: T 
> # 
> > 
>  # 
> > 
>  # 
> > 
>  # 
> > 
>  # 
> > 
>  # 
> > 
>  # 
> > 
>  # 
> >  # 
> >  281.3 KiB/s 
> > done 
> > Bytes transferred = 7810336 (772d20 hex) 
> > U-Boot# bootm 0x8020 
> > ## Booting kernel from Legacy Image at 8020 ... 
> >Image Name:   Linux-4.1.24+ 
> >Image Type:   ARM Linux Kernel Image (uncompressed) 
> >Data Size:7810272 Bytes = 7.4 MiB 
> >Load Address: 80008000 
> >Entry Point:  80008000 
> >Verifying Checksum ... OK 
> >Loading Kernel Image ... OK 
> > OK 
> > 
> > Starting kernel ... 
>
> So... "bootm 0x8020" where's your device tree binary? 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/





First of all thanks for your time regarding my issue . 

Actually I tried , alot of things and above given thing was on of it .

I also tried below process where I had provided dtb as well.


But result was same hanged up at "starting Kernel"  , complete log is as 
below 


U-Boot# setenv ipaddr 192.168.1.7
U-Boot# setenv serverip 192.168.1.5
U-Boot# tftpboot 0x80F8 am335x-boneblack.dtb
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.1.5; our IP address is 192.168.1.7
Filename 'am335x-boneblack.dtb'.
Load address: 0x80f8
Loading: T 
 9.8 KiB/s
done
Bytes transferred = 58133 (e315 hex)
U-Boot# tftpboot 0x80007fc0 uImage-BBB
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.1.5; our IP address is 192.168.1.7
Filename 'uImage-BBB'.
Load address: 0x80007fc0
Loading: T 
TFTP error: 'File not found' (1)
Not retrying...
U-Boot# tftpboot 0x80007FC0 uImage-BBB
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.1.5; our IP address is 192.168.1.7
Filename 'uImage-BBB'.
Load address: 0x80007fc0
Loading: T #
 #
 #
 #
 #
 #
 #
 #
 #
 307.6 KiB/s
done
Bytes transferred = 7810336 (772d20 hex)
U-Boot# setenv bootags console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro 
rootfstype=ext4 rootwait 
U-Boot# bootm 0x80007fc0 - 0x80f8
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-4.1.24+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:7810272 Bytes = 7.4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f8
   Booting using the fdt blob at 0x80f8
   XIP Kernel Image ... OK
OK
   Using Device Tree in place at 80f8, end 80f91314

Starting kernel ... 

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

[beagleboard] wrong date in log file wtmp

[Henry van Gestel]

Running ubuntu on BBB
*ubuntu@ubuntu-armhf:/var/log$ uname -a*
*Linux ubuntu-armhf 3.14.4.1-bone-armhf.com #1 SMP Tue Jun 3 12:37:22 UTC 
2014 armv7l armv7l armv7l GNU/Linux*

when doing a " last -x reboot" I get :
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16964+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16963+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16962+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16961+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16960+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16959+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16958+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16957+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16956+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16955+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16954+05:59*
*reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 
(16954+05:59*

the date of the system is correct:


*ubuntu@ubuntu-armhf:/var/log$ date*
*Thu Jun 30 16:41:00 CEST 2016*

the date filedate of /var/log/wtmp is also correct

*-rw-rw-r--  1 utmp 239232 Jun 30 15:42 wtmp*

*What could be the reason of getting not the correct output ?*

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c6346a96-e3d8-4644-9aca-b56e4cb96522%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] bbb ubuntu displays wrong log date

[Henry van Gestel]

running Ubuntu on my BBB:
ubuntu@ubuntu-armhf:/var/log$ uname -a
Linux ubuntu-armhf 3.14.4.1-bone-armhf.com #1 SMP Tue Jun 3 12:37:22 UTC 
2014 armv7l armv7l armv7l GNU/Linux

When I do last I get following output:
ubuntu@ubuntu-armhf:/var/log$ last -x reboot
reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 16:49 (16982+14:49
reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 (16982+05:59
reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 (16981+05:59
reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 (16981+05:59
reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 (16980+05:59
reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 (16980+05:59
reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 (16979+05:59
reboot   system boot  3.14.4.1-bone-ar Thu Jan  1 01:00 - 08:00 (16979+05:59

thats not what I expect.

The filedate of /var/log/wtmp is correct:

ubuntu@ubuntu-armhf:/var/log$ ls -algtr wtmp
-rw-rw-r-- 1 utmp 239232 Jun 30 15:42 wtmp

The date of the system is also correct:
ubuntu@ubuntu-armhf:/var/log$ date
Thu Jun 30 16:51:43 CEST 2016


What could be the reason of having this output?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ec660a05-ca69-497b-9872-fd8991e326e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ti's RPMsg Examples Significantly Changed

[John Syne]

> On Jun 30, 2016, at 2:11 AM, TJF  wrote:
> 
> Good morning John!
> 
> Am Mittwoch, 29. Juni 2016 17:07:05 UTC+2 schrieb john3909:
> What a silly argument. It is well known that when you don’t have physical 
> security, you don’t have any security. Once you can replace the storage 
> media, you can make the hardware do whatever you want. This is true of your 
> laptop and your servers. Clearly by your argument, you haven’t even begun to 
> understand security.
> 
> You're correct, I don't know much about the Linux terminologie and 
> definitions. From the Linux point of view, this was evidently a silly 
> argument. Do not fred. You're still leading by a two-digit score in this 
> discipline.
> 
> Does that change much? No, there're still other ways to get firmware on the 
> PRUSS. As a matter of fact there are solutions to use the PRUSS from user 
> space. No example, because I don't want to continue in publishing "how to 
> make a virus" tutorials here. If you don't believe that, just check out the 
> libpruio examples. Most of them work with user privilegues, root permission 
> is necessary for pinmuxing only.
The only reason you can do this from userspace is because of uio_pruss. It is 
the UIO driver that exposes the PRU memory to user space that creates this 
security hole. With RPMSG/RemoteProc, there is no uio_pruss and so you cannot 
install custom code to the PRU without root permission. 
>  
> In addition, you should reframe from impugning a person's motivations or 
> intentions.
> 
> It's confusing when you talk to yourself.
>  
> If you didn’t know, for stability reasons, Linux do not remove fameworks 
> unless they have been replaced by something better and in most cases the new 
> framework is backward compatible with the new framework.
> 
> Obviously there're exceptions. The PRU support is neither better nor backward 
> compatible to previous solutions. Oh sorry, not entirely correct: indeed it 
> has better support for PRU virus activities, targeting the kernel space 
> directly.
You still haven’t explained how to load custom code onto PRU using RemoteProc 
without root permission. Looking in /lib/firmware, user and group permissions 
are always root. There are only two ways to load PRU firmware and that is at 
boot time because of DT PRUSS driver definition or via sysfs and this requires 
root permission. 
>  
> No one knows how many developers are using RemoteProc/RPMSG ...
> 
> This is an important point! Just a few unquantifiable developers will use it, 
> but in the current configuration it endangers all BB systems by default.
I accept that you may have a way to do this that I have not thought of, but I 
have yet to see you prove this. 
>  
> so there is no ways that Linus or his deputies would permit the removal of 
> this framework.
> 
> Is it mainline? I thought it's a TI feature. Anyhow, mainline isn't affected. 
> This safety issue concerns boards with PRUSS, only.
As I said before, on the BeagleBoard-x15, the DSP, CortexM4 and PRU all have 
access to the entire memory map, so loading firmware on any of these cores must 
be secure. It isn’t a PRUSS issue only. 
>  
> All you can do is attempt to make it better ...
> 
> This is making it optional, or at least making PRUSS support optional in that 
> framework and disable it by default.
Why, because your argument would apply to any processor, namely DSP, CortexM4, 
other ARM cores running a different OS or perhaps barebones, etc. As long as 
you need root access to load firmware onto these other cores, there is no 
security issue. 
>  
> so stop fighting a loosing battle and join me in fixing what you don’t like. 
> 
> That's a damed good idea. Since here we've to wait for a management decision, 
> why don't you use that time for fixing the issue from our March discussion? 
> Or at least answer the still open question 
> .
> 
> BR 
Anyway, this discussion is not productive as we are not going to find a 
solution if you do not want to propose solutions. Your proposed solution of 
making RPMSG/RemoteProc optional isn’t a solution. However, perhaps there is a 
way to move the DT PRUSS definition into an DT overlay and not include the 
PRUSS definition in the base DT tree. This would allow both uio_pruss and 
RemoteProc to live side by side. Perhaps this is what you should be working on. 
I’m sure Robert Nelson would be open to a solution like this if you found a way 
to make this work. 

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

Re: [beagleboard] Re: Trouble enabling DCAN1 on BeagleBone, think I'm close but missing something.

[Robert Nelson]

On Fri, Jun 24, 2016 at 12:09 PM,   wrote:
> Not sure if you solved this yet...
>
> Try this, it worked for me:
>
> 1. disable the default overlay on slot 4:
> sudo sh -c "echo '-4' > /sys/devices/platform/bone_capemgr/slots"

you can just remove cape_universal=enable from /boot/uEnv.txt

>
> 2. add the CAN cape device
> sudo sh -c "echo 'BB-CAN1' > /sys/devices/platform/bone_capemgr/slots"
>
> otherwise, you may get the following error:
> root@beaglebone:/# sudo sh -c "echo 'BB-CAN1' >
> /sys/devices/platform/bone_capemgr/slots"
> [  494.986203] bone_capemgr bone_capemgr: slot #6: BB-CAN1 conflict
> P9.24 (#4:cape-universaln)
> [  494.995099] bone_capemgr bone_capemgr: slot #6: Failed verification
> sh: echo: I/O error

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgMREM%3DsgDPpxEa8HvRcwFN1uBOSjwT%2BZ6_02-Po11Hyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ddr3 length matching

[evilwulfie]

http://referencedesigner.com/books/si/time-and-distance.php

this can explain to you your issues



On 6/30/2016 6:28 AM, Gerald Coley wrote:
> You use the PCB SW tools to give you the lengths of each trace. The
> distance from one layer to the next is not that significant and is
> well within the needed tolerance.
>
> Gerald
>
>
> On Sat, Jun 25, 2016 at 6:16 PM,  > wrote:
>
> Hello,
>
>   I am designing my own board based on the am3358 and one ddr3
> chip. I looked at the bbb project to have a example of layout and
> i have a question about length matching for the ddr3 interface.
> How the length matching has been done if different layers are
> used? The signal on the outer layers doesnt travel at the same
> speed as the inner layers.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to beagleboard+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> 
> https://groups.google.com/d/msgid/beagleboard/0f800b4e-6e8d-4e20-962d-7efb1d709ec2%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> -- 
> Gerald
>  
> ger...@beagleboard.org 
> http://beagleboard.org/
> gcol...@emprodesign.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
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Be0PNUqUP1v48RB0NYGMapggiESACpxC5-jg9uKH34HcA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/84582216-992a-946f-2547-d0a093e0e3fe%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ddr3 length matching

[Gerald Coley]

You use the PCB SW tools to give you the lengths of each trace. The
distance from one layer to the next is not that significant and is well
within the needed tolerance.

Gerald


On Sat, Jun 25, 2016 at 6:16 PM,  wrote:

> Hello,
>
>   I am designing my own board based on the am3358 and one ddr3 chip. I
> looked at the bbb project to have a example of layout and i have a question
> about length matching for the ddr3 interface. How the length matching has
> been done if different layers are used? The signal on the outer layers
> doesnt travel at the same speed as the inner layers.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/0f800b4e-6e8d-4e20-962d-7efb1d709ec2%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Be0PNUqUP1v48RB0NYGMapggiESACpxC5-jg9uKH34HcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB startup current

[Gerald Coley]

All capacitors look like a short when they are discharged. What you are
seeing is the capacitors on the board charging up. The board is not even
powered up after .1ms.

Gerald

On Sat, Jun 25, 2016 at 9:19 AM,  wrote:

>
> According our mesurment BBB has over 2A startup power peek just for 0,1ms.
>
> This make it incompatible with some powersupply has advanced overquerrnet
> protection.
>
> This power peek is normal?
> There is any way to change startup current "policy" of board?
>
> Thanks fo any advise.
>
>
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/767a0185-6fc7-40b8-bba3-3f064ee300e5%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK_S%2BexPLcOAwhd5U6tHfGpqSKMrAcE2uLg2i_ax8HsTBUbGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Should I bitbang i2c ?

[emrekayaer]

I've always read a 0 value. Device beagleboneblack.I want to read data from 
i2c. i2c pins P9_17, P9_18, P9_19, P9_20. How can I do it. I would be glad 
if you can help. Thank you..

2 Eylül 2013 Pazartesi 09:57:29 UTC+3 tarihinde Roy Bellingan yazdı:
>
> Ben buldum https://github.com/ / am335x_pru_ BeagleBoard paketi / leke / 
> master / am335xPruReferenceGuide.pdf 
> 
>  
> i2c2 Sabit tablo 25 de Referans, ama tek Bir kod Örneği buldum Değil A.Ş. 
> sayfa i2c1 nasıl Ettik. Onunla çalışmak Için , Ben 0x4802_A000 adresinde 
> beyaz biraz veri yazma 0x4802_A000 gelen i2c köle yanıtı geri Ettik 
> okudunuz mu? meli Veya Tüm bu Almak İçin sadece sadece sadece sadece 
> sadece sadece sadece sadece bitbang Ettik GPIO A.Ş. trow?
>
>
>
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9acf9bbc-54d8-4d52-aa27-b546fb6d23e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Share network connection to BeagleBone Black through USB, OSX?

[max.millrose via BeagleBoard]

Actually this article explains it very well.
http://makezine.com/2012/07/16/use-your-mac-laptop-as-a-wireless-proxy-for-raspberry-pi/

Good article on how to configure single applications to use this proxy can 
be found here:
http://geekly-yours.blogspot.de/2012/11/setting-proxy-for-bash-in-debian.html

I guess that you could use IPTABLES to set it up globally, but my knowledge 
there is.let's say "not up to date" ;)

Am Mittwoch, 15. Juni 2016 17:23:33 UTC+2 schrieb vinayak...@gmail.com:
>
> after running command dhclient or dhclient usb0 it shows ii
>
> " PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
>
>
> --- 192.168.2.1 ping statistics ---
>
> 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
>
>
> packet_write_wait: Connection to 192.168.7.2: Broken pipe "
>
>
> what seems to be the problem?
>
> On Wednesday, June 18, 2014 at 7:23:47 AM UTC+5:30, jo...@joeynguyen.com 
> wrote:
>>
>> I'm on Beaglebone Black Rev. C with Debian Wheezy and this worked for me:
>>
>>
>>   1. Install Mac drivers from - http://beagleboard.org/Getting%20Started
>>   2. Connect BBB to Mac through USB
>>   3. On Mac, System Preferences > Sharing > Internet Sharing > Beaglebone 
>> Black
>>   4. System Preferences > Network, make sure BBB is in the left hand side 
>> and shows “Connected”
>>   5. After SSH’ing into the BBB, run “dhclient” (or "dhclient usb0” if 
>> that doesn’t work) and then try “ping google.com”.
>>
>> Hope that works for you.
>>
>> On Tuesday, December 10, 2013 3:57:21 PM UTC-6, caseys...@gmail.com 
>> wrote:
>>>
>>> Hello,
>>> I'm looking to connect my BeagleBone to the net by sharing my connection 
>>> from my mac through USB. 
>>> I know that this is possible and I've read many badly written 
>>> explanations for it online, but none of them really laid it out in a step 
>>> by step manner for someone who is relatively inexperienced with coding.
>>> Could anybody explain how to do this?
>>>
>>> Thank you
>>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/44c0176d-fabe-4096-be86-cab2fec11cc6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Share network connection to BeagleBone Black through USB, OSX?

[max.millrose via BeagleBoard]

The Problem is, that you destroy your own connection whilst being connected 
over it.

You start of by connecting to the BBB via USB and SSH?
root@192.168.7.2 <-- this is the IP of the BBB when the session begins
Then you run the command to ask for a NEW IP for that interface via DHCP 
and your router answers.
The router has different DHCP-range gives the interface a new IP. That new 
IP is NOT THE SAME as your current IP. Hence the IP changes and therefore 
destroys your connection.

I hope I could help you.
I am currently looking for a way to keep the IP on USB0 and still have 
internet access with my BBB.
Should I find something, I will let you know :)

Kind regards
Max

Am Mittwoch, 15. Juni 2016 17:23:33 UTC+2 schrieb vinayak...@gmail.com:
>
> after running command dhclient or dhclient usb0 it shows ii
>
> " PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
>
>
> --- 192.168.2.1 ping statistics ---
>
> 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
>
>
> packet_write_wait: Connection to 192.168.7.2: Broken pipe "
>
>
> what seems to be the problem?
>
> On Wednesday, June 18, 2014 at 7:23:47 AM UTC+5:30, jo...@joeynguyen.com 
> wrote:
>>
>> I'm on Beaglebone Black Rev. C with Debian Wheezy and this worked for me:
>>
>>
>>   1. Install Mac drivers from - http://beagleboard.org/Getting%20Started
>>   2. Connect BBB to Mac through USB
>>   3. On Mac, System Preferences > Sharing > Internet Sharing > Beaglebone 
>> Black
>>   4. System Preferences > Network, make sure BBB is in the left hand side 
>> and shows “Connected”
>>   5. After SSH’ing into the BBB, run “dhclient” (or "dhclient usb0” if 
>> that doesn’t work) and then try “ping google.com”.
>>
>> Hope that works for you.
>>
>> On Tuesday, December 10, 2013 3:57:21 PM UTC-6, caseys...@gmail.com 
>> wrote:
>>>
>>> Hello,
>>> I'm looking to connect my BeagleBone to the net by sharing my connection 
>>> from my mac through USB. 
>>> I know that this is possible and I've read many badly written 
>>> explanations for it online, but none of them really laid it out in a step 
>>> by step manner for someone who is relatively inexperienced with coding.
>>> Could anybody explain how to do this?
>>>
>>> Thank you
>>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/98bc82d2-54c0-45cd-b2e9-b15081b9f414%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

[engkan2kit]

I've changed my kernel to the same version as the poster (I'm using ubuntu).
I still don't see the device in /dev.

[   17.581262] pru-rproc 4a338000.pru1: sysevt-to-ch[18] -> 3
[   17.581274] pru-rproc 4a338000.pru1: sysevt-to-ch[19] -> 1
[   17.581286] pru-rproc 4a338000.pru1: skip intr mapping for chnl 0
[   17.581297] pru-rproc 4a338000.pru1: chnl-to-host[1] -> 1
[   17.581308] pru-rproc 4a338000.pru1: skip intr mapping for chnl 2
[   17.581319] pru-rproc 4a338000.pru1: chnl-to-host[3] -> 3
[   17.581329] pru-rproc 4a338000.pru1: skip intr mapping for chnl 4
[   17.581340] pru-rproc 4a338000.pru1: skip intr mapping for chnl 5
[   17.581350] pru-rproc 4a338000.pru1: skip intr mapping for chnl 6
[   17.581361] pru-rproc 4a338000.pru1: skip intr mapping for chnl 7
[   17.581371] pru-rproc 4a338000.pru1: skip intr mapping for chnl 8
[   17.581382] pru-rproc 4a338000.pru1: skip intr mapping for chnl 9
[   17.581397] pruss-rproc 4a30.pruss: SYSEV18 -> CH3 (CMR4 0x0003)
[   17.581410] pruss-rproc 4a30.pruss: SYSEV19 -> CH1 (CMR4 0x0103)
[   17.581424] pruss-rproc 4a30.pruss: CH1 -> HOST1 (HMR0 0x0100)
[   17.581436] pruss-rproc 4a30.pruss: CH3 -> HOST3 (HMR0 0x03000100)
[   17.581449] pruss-rproc 4a30.pruss: configured system_events = 
0x000c intr_channels = 0x000a host_intr = 0x000a
[   17.581461]  remoteproc2: starting PRU1: entry-point = 0x0
[   17.581471]  remoteproc2: remote processor 4a338000.pru1 is now up
[   17.661101]  remoteproc2: kicking vqid 0 on PRU1
[   17.663720] virtio_rpmsg_bus virtio0: rpmsg host is online
ubuntu@arm:~$



On Tuesday, March 29, 2016 at 2:40:57 AM UTC+8, john3909 wrote:
>
> Hi Lucas,
>
> Good to hear this is working for you. Now for the real work ;-)
>
> Regards,
> John
>
>
>
>
> On Mar 28, 2016, at 6:10 AM, lucas  
> wrote:
>
> Wow it worked :) Thank you, John! 
>
> Short summary how to get it working: 
>
> 1.) Compile PRU_RPMsg_LED0 project in CCS
> 2.) Transfer PRU_RPMsg_LED0.out onto beaglebone into the /lib/firmware 
> directory 
> 3.) Set symbolic link: sudo ln -s PRU_RPMsg_LED0.out am335x-pru0-fw
> 4.) restart
> 5.) modprobe virtio_rpmsg_bus
> 6.) modprobe rpmsg_pru
> 7.) check if /dev/rpmsg_pru30 exists
> 8.) echo "r" > /dev/rpmsg_pru30
> 9.) Observe red LED light up on PRU_cape :) 
>
>
> On Wednesday, March 23, 2016 at 8:42:50 PM UTC+1, john3909 wrote:
>>
>> Don’t include the .ko extension when using modprobe.
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Mar 23, 2016, at 9:32 AM, lucas  wrote:
>>
>> Sorry forgot to copy the error message for the modprobe command: 
>>
>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
>> modprobe virtio_rpmsg_bus.ko
>> modprobe: FATAL: Module virtio_rpmsg_bus.ko not found.
>>
>> On Wednesday, March 23, 2016 at 5:27:12 PM UTC+1, lucas wrote:
>>>
>>> Hi John, 
>>>
>>> thank you very much for your answer. 
>>>
>>> I am using the 4.1.15-ti-rt-r43 kernel. It's the kernel that came with 
>>> the debian image from the beaglebone website.  
>>>
>>> Only the pruss_remoteproc module seems to be loaded on boot:
>>>
>>> # lsmod
>>> Module  Size  Used by
>>> 8021q  17336  0
>>> garp5975  1 8021q
>>> mrp 7322  1 8021q
>>> stp 1911  1 garp
>>> llc 5257  2 stp,garp
>>> pruss_remoteproc   15296  2
>>> omap_rng4358  0
>>> rng_core7437  1 omap_rng
>>> usb_f_acm   7180  1
>>> u_serial   10596  3 usb_f_acm
>>> usb_f_rndis22734  1
>>> g_multi 5316  0
>>> usb_f_mass_storage 42745  2 g_multi
>>> u_ether12028  2 usb_f_rndis,g_multi
>>> libcomposite   43810  4 
>>> usb_f_acm,usb_f_rndis,g_multi,usb_f_mass_storage
>>> snd_soc_davinci_mcasp17266  0
>>> snd_soc_edma1150  1 snd_soc_davinci_mcasp
>>> spi_omap2_mcspi10681  0
>>> uio_pdrv_genirq 3521  0
>>>
>>> Although the other modules do exist in the driver directory.
>>>
>>> ls /lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg
>>> rpmsg_pru.ko  rpmsg-rpc.ko  virtio_rpmsg_bus.ko
>>>
>>> I cannot modprob the modules:
>>>
>>> # modprobe virtio_rpmsg_bus.ko
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
>>> modprobe virtio_rpmsg_bus.ko
>>>
>>>
>>> But I can use insmod 
>>>
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
>>> insmod virtio_rpmsg_bus.ko
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# lsmod
>>> Module  Size  Used by
>>> virtio_rpmsg_bus   13437  0
>>> 8021q  17336  0
>>> garp5975  1 8021q
>>> ...
>>>
>>>
>>> Should I try to switch to the kernel version you are using? Is there an 
>>> image or should I recompile the kernel? Any other ideas? 
>>>
>>> Lucas
>>>
>>> On Tuesday, March 22, 2016 at 7:40:56 PM 

[beagleboard] Re: omaplfb probing issue

[ajfoster85]

Hi,

I'm having the exact same issue - did you ever manage to resolve this?

Thanks in advance for any help you can give me :-)

Adam

On Thursday, 12 November 2015 01:01:49 UTC, selmi...@gmail.com wrote:
>
> Hello,
>
> I am trying to use Qt for beaglebone black by folowing this tutorial 
> http://hawkkim.dlinkddns.com/?page_id=109
> But I have something wrong in my Kernel because the omaplfb is not probed:
>
> Starting PVR
> [   79.066145] omaplfb: Unknown symbol register_vsync_cb (err 0)
> [   79.072205] omaplfb: Unknown symbol unregister_vsync_cb (err 0)
> modprobe: ERROR: could not insert 'omaplfb': Unknown symbol in module, or 
> unknown parameter (see dmesg)
> [   79.133859] Unable to handle kernel NULL pointer dereference at virtual 
> address 
>
> I am using: Linux beaglebone 4.1.10 #11 PREEMPT Wed Nov 11 23:15:24 CET 
> 2015 armv7l GNU/Linux
>
> I enabled the DA8XX-FB flag in kernel config file but I still have the 
> same issue, I pached the da8xx-fb.c file to add register_vsync_cb and 
> unregister_vsync_cb function but it still not working.
>
> Thank you for your help,
> Adel
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/08ecb433-d7ff-46a6-93a9-1a4584d27909%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] RPMsg from Linux User Space to PRU on Beaglebone Black

[engkan2kit]

I tried what you did but I am using 4.4.9-ti-rt-r26. I am still not seeing 
the /dev/rpmsg_pru*.

Was this changed in recent kernel versions? I have been trying to solve 
this since yesterday.

On Monday, March 28, 2016 at 9:10:11 PM UTC+8, lucas wrote:
>
> Wow it worked :) Thank you, John! 
>
> Short summary how to get it working: 
>
> 1.) Compile PRU_RPMsg_LED0 project in CCS
> 2.) Transfer PRU_RPMsg_LED0.out onto beaglebone into the /lib/firmware 
> directory 
> 3.) Set symbolic link: sudo ln -s PRU_RPMsg_LED0.out am335x-pru0-fw
> 4.) restart
> 5.) modprobe virtio_rpmsg_bus
> 6.) modprobe rpmsg_pru
> 7.) check if /dev/rpmsg_pru30 exists
> 8.) echo "r" > /dev/rpmsg_pru30
> 9.) Observe red LED light up on PRU_cape :) 
>
>
> On Wednesday, March 23, 2016 at 8:42:50 PM UTC+1, john3909 wrote:
>>
>> Don’t include the .ko extension when using modprobe.
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Mar 23, 2016, at 9:32 AM, lucas  wrote:
>>
>> Sorry forgot to copy the error message for the modprobe command: 
>>
>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
>> modprobe virtio_rpmsg_bus.ko
>> modprobe: FATAL: Module virtio_rpmsg_bus.ko not found.
>>
>> On Wednesday, March 23, 2016 at 5:27:12 PM UTC+1, lucas wrote:
>>>
>>> Hi John, 
>>>
>>> thank you very much for your answer. 
>>>
>>> I am using the 4.1.15-ti-rt-r43 kernel. It's the kernel that came with 
>>> the debian image from the beaglebone website.  
>>>
>>> Only the pruss_remoteproc module seems to be loaded on boot:
>>>
>>> # lsmod
>>> Module  Size  Used by
>>> 8021q  17336  0
>>> garp5975  1 8021q
>>> mrp 7322  1 8021q
>>> stp 1911  1 garp
>>> llc 5257  2 stp,garp
>>> pruss_remoteproc   15296  2
>>> omap_rng4358  0
>>> rng_core7437  1 omap_rng
>>> usb_f_acm   7180  1
>>> u_serial   10596  3 usb_f_acm
>>> usb_f_rndis22734  1
>>> g_multi 5316  0
>>> usb_f_mass_storage 42745  2 g_multi
>>> u_ether12028  2 usb_f_rndis,g_multi
>>> libcomposite   43810  4 
>>> usb_f_acm,usb_f_rndis,g_multi,usb_f_mass_storage
>>> snd_soc_davinci_mcasp17266  0
>>> snd_soc_edma1150  1 snd_soc_davinci_mcasp
>>> spi_omap2_mcspi10681  0
>>> uio_pdrv_genirq 3521  0
>>>
>>> Although the other modules do exist in the driver directory.
>>>
>>> ls /lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg
>>> rpmsg_pru.ko  rpmsg-rpc.ko  virtio_rpmsg_bus.ko
>>>
>>> I cannot modprob the modules:
>>>
>>> # modprobe virtio_rpmsg_bus.ko
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
>>> modprobe virtio_rpmsg_bus.ko
>>>
>>>
>>> But I can use insmod 
>>>
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# 
>>> insmod virtio_rpmsg_bus.ko
>>> root@beaglebone:/lib/modules/4.1.15-ti-rt-r43/kernel/drivers/rpmsg# lsmod
>>> Module  Size  Used by
>>> virtio_rpmsg_bus   13437  0
>>> 8021q  17336  0
>>> garp5975  1 8021q
>>> ...
>>>
>>>
>>> Should I try to switch to the kernel version you are using? Is there an 
>>> image or should I recompile the kernel? Any other ideas? 
>>>
>>> Lucas
>>>
>>> On Tuesday, March 22, 2016 at 7:40:56 PM UTC+1, john3909 wrote:

 Hi Lucas,

 This seems to work just fine for me. What kernel version are you using?

 I’m using V4.1.13-ti-r33. As you can see, all remoteproc/rpmsg kernel 
 modules are loaded automatically at boot time.

 [   16.251480] pruss-rproc 4a30.pruss: 8 PRU interrupts parsed 

 [   16.251567] pruss-rproc 4a30.pruss: memorydram0: pa 
 0x4a30 size 0x2000 va e0ca 
 [   16.251595] pruss-rproc 4a30.pruss: memorydram1: pa 
 0x4a302000 size 0x2000 va e0ca4000 
 [   16.251621] pruss-rproc 4a30.pruss: memory shrdram2: pa 
 0x4a31 size 0x3000 va e0ca8000 
 [   16.251644] pruss-rproc 4a30.pruss: memory intc: pa 
 0x4a32 size 0x2000 va e0cac000 
 [   16.251672] pruss-rproc 4a30.pruss: memory  cfg: pa 
 0x4a326000 size 0x2000 va e0cb 
 [   16.252174] pruss-rproc 4a30.pruss: creating platform devices 
 for PRU cores
 [   16.374800] pru-rproc 4a334000.pru0: memory iram: pa 0x4a334000 
 size 0x2000 va e0cb4000
 [   16.374858] pru-rproc 4a334000.pru0: memory  control: pa 0x4a322000 
 size 0x400 va e0876000 
 [   16.374901] pru-rproc 4a334000.pru0: memorydebug: pa 

[beagleboard] Incorrect device overlay selected during boot

[richatnstar via BeagleBoard]

Hi,

My BBB stack has a 4.3" LCD cape -- powerup diagnostics (dmesg) indicated 
the cape was found OK & brightness worked Ok. I was unable to view 
(startup) text on the display. (Ver 4.4.1-bone11). After a few days of 
debug, I found that the MuxPins were not properly updated and were still 
accessing HDMI (not modified as expected). I added an 'echo' into /uEnv.txt 
& discovered that the 'overlay file' was not right - it was the default 
chosen at power-up.

/boot/uEnv.txt has the lines (amongst others)

 dtb=am335x-boneblack-overlay.dtb
 Disable: HDMI

/uEnv.txt was modified - *fdtfile* was replaced by *dtb*

#loadxfdt=load mmc 0:1 ${fdtaddr} /boot/dtbs/${uname_r}/${fdtfile}
loadxfdt=load mmc 0:1 ${fdtaddr} /boot/dtbs/${uname_r}/*${dtb}*

Possibly modifying fdtfile is the appropriate method -- Is there a better 
solution?

thx

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0da49087-4271-4df2-81f4-e66b763c2ebf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Writing a new Image to the BBB Rev. C

[taynautentic]

Hello People,

I've been tried to record a new image on BBB Rev. C, the image is write on 
micro SD-card, but when I start record the boot's process (hold the botton 
S2, conect the BBB at a power cable and wait LEDs flash)  Leds don't blink 
as it should.

Can Anybory help me, please?

Thank you, 
Tayná B.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/3aad60eb-a518-4e55-acbd-cf5e80665306%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] wvdial Time Out

[wilcuttbryan]

I'm using wvdial to keep a USB 3G modem online.  When I bring up the modem, 
it stays up for 25 minutes'ish while I can ping it.  Suddenly pings stop.  
After a fair amount of experimenting, it seems the connection lasts for 
almost exactly 25 minutes each time before something disconnects.

If I restart wvdial, everything goes back to normal... for 25 minutes.

My /etc/wvdial.conf file:

[Dialer Defaults]
Idle Seconds = 0
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0   +FCLASS=0
Modem Type = Analog Modem
Baud = 9600
Phone = #777
Modem = /dev/ttyUSB0
ISDN = 0
Stupid Mode = 1
Username = 
Password = 
New PPPD = yes
Auto Reconnect = on
Idle Seconds = 0


When I looked through the wvdial source code, there didn't seem to be 
anything there to suggest a 25 minute timeout issue.   Has anyone had this 
issue?  Any ideas?

Thanks!

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

[beagleboard] Ddr3 length matching

[larbi . joubala]

Hello,

  I am designing my own board based on the am3358 and one ddr3 chip. I looked 
at the bbb project to have a example of layout and i have a question about 
length matching for the ddr3 interface. How the length matching has been done 
if different layers are used? The signal on the outer layers doesnt travel at 
the same speed as the inner layers.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0f800b4e-6e8d-4e20-962d-7efb1d709ec2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB startup current

[kzsoltkzsolt]

According our mesurment BBB has over 2A startup power peek just for 0,1ms. 

This make it incompatible with some powersupply has advanced overquerrnet 
protection. 

This power peek is normal?
There is any way to change startup current "policy" of board?

Thanks fo any advise.




-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/767a0185-6fc7-40b8-bba3-3f064ee300e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] About BeagleBoard-xM

[mopplayer5]

I have a SBC8530 board (compatible with BeagleBoard-xM).
Does its kernel compile by omap2plus_defconfig for v3.14.y or above v4.x.y?
Is its DTS omap3-beagle-xm.dtb?

Thank a lot!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7935894a-374b-46d0-9542-6db08af4beb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Trouble enabling DCAN1 on BeagleBone, think I'm close but missing something.

[pparis]

Not sure if you solved this yet...

Try this, it worked for me:

1. disable the default overlay on slot 4:
sudo sh -c "echo '-4' > /sys/devices/platform/bone_capemgr/slots"

2. add the CAN cape device
sudo sh -c "echo 'BB-CAN1' > /sys/devices/platform/bone_capemgr/slots"

otherwise, you may get the following error:
root@beaglebone:/# sudo sh -c "echo 'BB-CAN1' > 
/sys/devices/platform/bone_capemgr/slots"
[  494.986203] bone_capemgr bone_capemgr: slot #6: BB-CAN1 conflict 
P9.24 (#4:cape-universaln)
[  494.995099] bone_capemgr bone_capemgr: slot #6: Failed verification
sh: echo: I/O error


On Monday, May 2, 2016 at 1:39:18 PM UTC-7, David Miller Lowe wrote:
>
> Hi Folks,
>
> I am easily able to receive CAN traffic with my Peak USB-CAN interface on 
> my linux workstation.  I know our device is producing regular updates at 
> 25 and it dumps find using candump.
>
> For a couple days I have been trying (without success) to duplicate the 
> behavior on my Element Rev B6 Beaglebone.  I've read many posts and have 
> worked bast a bunch of issues but still get no can traffic.
>
> The results are the same with a WaveShare CAN Cape or a discrete NXP 
> TJA1051 High-speed CAN transceiver that I have connected on a breadboard.  
> If I hook a scope to the input RX signal I can see the external CAN traffic 
> but nothing gets through.
>
> I did modify ~/bb.org-overlays/src/arm/cape-universaln-00A0.dts to remove 
> references to pins P9_24 and P9_26 (UART1 RX/TX)
>
> For clarity's sake here is the script that I run after rebooting the 
> Beaglbone.
>
> set -x
> echo "# make sure, I'm running as root, unmolested 
> bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img image"
> id
> uname -a
>
> echo "# look, can pin muxing for P9_24 and P9_26 are at default (GPIO, 
> mode 7)"
> devmem2 0x44E10980 w
> devmem2 0x44E10984 w
>
> echo "# cat my overlay File, has been built/installed/rebooted 
> successfully"
> cat /hone/debian/bb.org-overlays/src/arm/BB-CAN1-00A0.dts
>
> echo "# install my overlay to setup the CAN pins"
> sh -c "echo 'BB-CAN1' > /sys/devices/platform/bone_capemgr/slots"
>
> echo "# see that the overlay was installed and make sure pins went to 
> mode 2"
> cat /sys/devices/platform/bone_capemgr/slots
> devmem2 0x44E10980 w
> devmem2 0x44E10984 w
>
> echo "#load the can drivers"
> modprobe can
> modprobe can-dev
> modprobe can-raw
>
> echo "# show what's loaded"
> lsmod
>
> echo "# fire up the interface"
> ip link set can0 type can bitrate 25 triple-sampling on
> ip link set can0 up
>
> echo "# see that we're up"
> ifconfig can0
>
> echo "#Shoud receive can data, same as my linux workstation..."
> candump can0
>
>
> Here is the output from the script..
>
> debian@beaglebone:~$ sudo ./canSetup.sh 
> + echo # make sure, I'm running as root, unmolested 
> bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img image
> # make sure, I'm running as root, unmolested 
> bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img image
> + id
> uid=0(root) gid=0(root) groups=0(root)
> + uname -a
> Linux beaglebone 4.1.15-ti-rt-r43 #1 SMP PREEMPT RT Thu Jan 21 20:13:58 
> UTC 2016 armv7l GNU/Linux
> + echo # look, can pins P9_24 and P9_26 are at default (GPIO, mode 7)
> # look, can pins P9_24 and P9_26 are at default (GPIO, mode 7)
> + devmem2 0x44E10980 w
> /dev/mem opened.
> Memory mapped at address 0xb6f93000.
> Value at address 0x44E10980 (0xb6f93980): 0x37
> + devmem2 0x44E10984 w
> /dev/mem opened.
> Memory mapped at address 0xb6f9b000.
> Value at address 0x44E10984 (0xb6f9b984): 0x37
> + echo # cat my overlay File, has been built/installed/rebooted 
> successfully
> # cat my overlay File, has been built/installed/rebooted successfully
> + cat /home/debian/bb.org-overlays/src/arm/BB-CAN1-00A0.dts
> /*
>  * Copyright (C) 2015 Robert Nelson 
>  *
>  * Virtual cape for CAN1 on connector pins P9.24 P9.26
>  *
>  * This program is free software; you can redistribute it and/or modify
>  * it under the terms of the GNU General Public License version 2 as
>  * published by the Free Software Foundation.
>  */
> /dts-v1/;
> /plugin/;
>
> #include 
> #include 
>
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black", 
> "ti,beaglebone-green";
>
> /* identification */
> part-number = "BB-CAN1";
> version = "00A0";
>
> /* state the resources this cape uses */
> exclusive-use =
> /* the pin header uses */
> "P9.24",/* can1_rx */
> "P9.26",/* can1_tx */
> /* the hardware ip uses */
> "dcan1";
>
> fragment@0 {
> target = <_pinmux>;
> __overlay__ {
> bb_dcan1_pins: pinmux_dcan1_pins {
> pinctrl-single,pins = <
> BONE_P9_24 (SLEWCTRL_FAST | PIN_INPUT_PULLUP | 
> MUX_MODE2) /* uart1_txd.d_can1_rx */
> BONE_P9_26 (SLEWCTRL_FAST | PIN_OUTPUT_PULLUP | 
> MUX_MODE2) /* uart1_rxd.d_can1_tx */
> >;
> };
> 

[beagleboard] Quality Analyst With Auto Finance Domain experience@Torrance, CA

[Santosh kumar Nityo]

Hi,

Hope you doing Well !!!

Here is our *Implementing partner **Requirement*, Please go through the
below requirement and send us suitable consultant with their *updated
resume, rates and Contact details ..*



*Role:** Quality Analyst With *
*Auto Finance Domain experience Location: Torrance, CA*

*Work Duration:** 12 months*

*Mandatory: **Auto Finance Domain experience Interview: Phone/ Skype*

*Years of Experience: 8+*

*Note: We need Photo id and visa copy (H1b)*

• At least 7+ years of experience in Testing and Testing Processes
• Good understanding and work experience in big migration projects
• Having good Auto Finance/Finance domain knowledge especially on Loan and
Lease processing
• Good knowledge in HP ALM, UFT/BPT
• Good Analytical skills
• Experience and desire to work in a Global delivery environment



[image: cid:image001.jpg@01D0BE16.B9DD7240]



Nityo Infotech Corp.
666 Plainsboro Road,

Suite 1285

Plainsboro, NJ 08536

*Santosh Kumar *

*Technical Recruiter*

Desk No-609-853-0818 Ext-2170
Fax :   609 799 5746

kuntal.sant...@nityo.com
www.nityo.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAG0Zfz3KHAeUUFpNL%3DT%3D9yvpARLqwb%3D%3DSxuyxU%3DShohLf-H9tA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Unable to flash Debain 7.9 to Beagle bone green

[abhilash h]

Hi Robert,

Thanks for the quick reply. I was just looking into below post
https://groups.google.com/forum/#!category-topic/beagleboard/seeed-beaglebone-green/l1GtJPIRvHU
Thanks for the new release. It really helped me a lot.

On Thursday, 30 June 2016 18:21:17 UTC+5:30, abhilash h wrote:
>
> Dear All,
>
> I am unable to flash Debian 7.9 to new Beaglebone Green from SD card. I 
> have un commented  the line in uEnv.txt.
> I get this write error (mmcblk1 not found). But i am able to flash debian 
> 8.4 to emmc. It would be great if someone could help.
>
> Regards,
> Abhilash H
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c7fbbc07-7bf0-4473-adb1-c1fc6a5f2ea4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unable to flash Debain 7.9 to Beagle bone green

[Robert Nelson]

On Thu, Jun 30, 2016 at 7:51 AM, abhilash h  wrote:
> Dear All,
>
> I am unable to flash Debian 7.9 to new Beaglebone Green from SD card. I have
> un commented  the line in uEnv.txt.
> I get this write error (mmcblk1 not found). But i am able to flash debian
> 8.4 to emmc. It would be great if someone could help.

This was fixed and posted a few weeks back:

https://rcn-ee.net/rootfs/bb.org/release/2016-06-15/

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgxu0zhQ_cizij6%2BQuHBDE7VgdMSPpSQdcsFQkv9GecVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to flash Debain 7.9 to Beagle bone green

[abhilash h]

Dear All,

I am unable to flash Debian 7.9 to new Beaglebone Green from SD card. I 
have un commented  the line in uEnv.txt.
I get this write error (mmcblk1 not found). But i am able to flash debian 
8.4 to emmc. It would be great if someone could help.

Regards,
Abhilash H

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/da10ce17-b30a-4571-8e0a-c89b5009212f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Ti's RPMsg Examples Significantly Changed

[TJF]

Good morning John!

Am Mittwoch, 29. Juni 2016 17:07:05 UTC+2 schrieb john3909:
>
> What a silly argument. It is well known that when you don’t have physical 
> security, you don’t have any security. Once you can replace the storage 
> media, you can make the hardware do whatever you want. This is true of your 
> laptop and your servers. Clearly by your argument, you haven’t even begun 
> to understand security. 
>

You're correct, I don't know much about the Linux terminologie and 
definitions. From the Linux point of view, this was evidently a silly 
argument. Do not fred. You're still leading by a two-digit score in this 
discipline.

Does that change much? No, there're still other ways to get firmware on the 
PRUSS. As a matter of fact there are solutions to use the PRUSS from user 
space. No example, because I don't want to continue in publishing "how to 
make a virus" tutorials here. If you don't believe that, just check out the 
libpruio examples. Most of them work with user privilegues, root permission 
is necessary for pinmuxing only.
 

> In addition, you should reframe from impugning a person's motivations or 
> intentions.
>

It's confusing when you talk to yourself.
 

> If you didn’t know, for stability reasons, Linux do not remove fameworks 
> unless they have been replaced by something better and in most cases the 
> new framework is backward compatible with the new framework. 
>

Obviously there're exceptions. The PRU support is neither better nor 
backward compatible to previous solutions. Oh sorry, not entirely correct: 
indeed it has better support for PRU virus activities, targeting the kernel 
space directly.
 

> No one knows how many developers are using RemoteProc/RPMSG ...
>

This is an important point! Just a few unquantifiable developers will use 
it, but in the current configuration it endangers all BB systems by default.
 

> so there is no ways that Linus or his deputies would permit the removal of 
> this framework. 
>

Is it mainline? I thought it's a TI feature. Anyhow, mainline isn't 
affected. This safety issue concerns boards with PRUSS, only.
 

> All you can do is attempt to make it better ...
>

This is making it optional, or at least making PRUSS support optional in 
that framework and disable it by default.
 

> so stop fighting a loosing battle and join me in fixing what you don’t 
> like. 
>

That's a damed good idea. Since here we've to wait for a management 
decision, why don't you use that time for fixing the issue from our March 
discussion? Or at least answer the still open question 
.

BR 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ee04b094-812b-43d8-b25a-5985a5fba148%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.