Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

[Reshmi Chandran]

Still no luck .

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh 

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

[sudo] password for debian: 
git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
eeprom:[A335BNLT00C05315BBBK1677]
dogtag:[BeagleBoard.org Debian Image 2017-08-31]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
2017.09-rc2-2-g7c9353]
kernel:[4.9.45-ti-r57]
nodejs:[v6.11.2]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

debian@beaglebone:~$ iwconfig 
eth0  no wireless extensions.

usb0  no wireless extensions.

usb1  no wireless extensions.

lono wireless extensions.

can0  no wireless extensions.

can1  no wireless extensions.

I downloaded the Debain image Debian 9.1 2017-08-31 4GB SD LXQT (Stretch)
debian@beaglebone:~$ connmanctl 
connmanctl> tether wifi off
Error disabling wifi tethering: Method "SetProperty" with signature "sv" on 
interface "net.connman.Technology" doesn't exist

connmanctl> enable wifi
Error wifi: Method "SetProperty" with signature "sv" on interface 
"net.connman.Technology" doesn't exist

connmanctl> scan wifi
Error /net/connman/technology/wifi: Method "Scan" with signature "" on 
interface "net.connman.Technology" doesn't exist

connmanctl> agent on
Agent registered
connmanctl> services

connmanctl> quit


On Monday, November 13, 2017 at 8:17:53 PM UTC+5:30, RobertCNelson wrote:
>
> On Sun, Nov 12, 2017 at 11:02 PM,   
> wrote: 
> > Hi All, 
> > Same problem here. Which is TP1. I could not find it on the header 
> > information . 
>
> Look at the pcb, it's on the silkscreen.. 
>
> 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/8818767a-5471-48fc-9afd-1314db6667bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Rose-Hulman Embedded Linux Project Demos

[Ryan Evans]

My project was to create a pinball machine, controlled by the BeagleBone.  
Here  is the wiki page.

-Ryan Evans

On Monday, November 13, 2017 at 4:01:18 PM UTC-5, Mark A. Yoder wrote:
>
> Tomorrow my embedded linux students are demoing their projects.  
>
> I'm having them reply to this message with a link the a wiki describing 
> the project.  You can also look under P here[1].
>
> Take a look at what they have done.
>
> --Mark
>
> [1] https://elinux.org/index.php?title=Category:ECE497 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/96c325c7-a6f6-4674-a0d9-12ad6272efd7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Rose-Hulman Embedded Linux Project Demos

[joey.p via BeagleBoard]

We used our beagle bone to capture an image of a Sudoku puzzle, detect the 
numbers using the Google Vision API, and solve the puzzle. Here is our wiki 
page: https://elinux.org/ECE497_Project_Sudoku_Solver

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/d1785d48-7c8b-41b1-81ff-8ab2e9e6c23a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Connecting two Beaglebone Blacks

[briselec]

No you don't need a crossover cable. I can't remember the last time I used 
one. Ethernet ports have automatically handled that for some time now.

As for the original question, if you can program I would go with using a 
udp socket.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/7e659fa5-a4c5-46a9-a994-4da6b4b8debd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Unnecessary network data traffic

[William B]

Good idea! I'll try this and post again if I can observe something 
suspicious.
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/6490002d-5d66-4c9a-80be-e793610eeb5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

[Jeff Andich]

Hi,

Will the 8250 driver still allow "manual" control of the RTS line for a 
given UART from an application like Python or C# (where the application 
toggles the state of the RTS line, rather than driver, after sending a 
request message in order to toggle the 485 XCVR), or is the OMAP driver (in 
place of the 8250 driver) needed for this as well?

I've attempted to associate the RTS line for UART5 with GPIO5_8 (which is 
connected to the DE toggle on a 485 chip) via the device tree (kernel 
4.4.y), followed by calling setRTS(True/False) from Python, but that 
doesn't appear to be switching the 485 XCVR.  However, I can still use 
sysfs commands to toggle the GPIO5_8 connected to the 485 chip to control 
the direction of transmission.

In order to help differentiate between an incorrect device tree 
configuration vs. needing to recompile the kernel with the OMAP  driver 
instead of the 8250 driver, I'm wondering if you know whether the 8250 
driver will support what we're trying here. Everything I've read (including 
https://groups.google.com/forum/#!msg/beagleboard/nMtRpdWSJu0/EDSXqGpiBAAJ) 
seems to suggest that the 8250 doesn't yet handle toggling the RTS/CTS 
lines on its own based on delays between characters, but I haven't seen 
anything about manual control.


Following is a snippet/fragment from my device tree. ***LATE  DISCLOSURE*** 
>From UART5_8, you can see that this is for the BB-X15, but I believe the 
same issue pertains to both the BBB and the BB-X15: 

 {
pinctrl-names = "default";
pinctrl-0 = <_pins>;
status = "okay";
rts-gpio = < 8 GPIO_ACTIVE_HIGH>;
rs485-rts-active-high;
rs485-rts-delay = <0 0>;
linux,rs485-enabled-at-boot-time;
};

Thanks!!!

On Monday, November 13, 2017 at 3:04:51 PM UTC-6, Rnd Mpt wrote:
>
> We used the rs485 version/branch of the modbus on github. Sorry i meant to 
> say rts instead of cts.
>
> I used my github as notes. Follow readmes and see if it helps. Its been a 
> while since we did this. Let me know if more help is needed
>
> https://github.com/rwdutoit/beaglebone?files=1
>
> On Mon, 13 Nov 2017, 16:33 ,  wrote:
>
>> https://github.com/RobertCNelson/bb-kernel/issues/38
>>
>>
>> 2017. november 10., péntek 20:33:49 UTC+1 időpontban dmezz...@gmail.com 
>> a következőt írta:
>>
>>> Did you ever get this to work 
>>>
>>> I am using the Nelson yakbuild kernel 4.9.45 and disabled the 8250 and 
>>> enabled omap serial in kernel configuration 
>>>
>>> using same rs485 dtso overkay I can not get RTS to work 
>>> and nothing transmits. 
>>>
>>> I can not find anything on web to solve this. 
>>> Do you have a solution procedure? 
>>>
>>>
>>> dennis 
>>>
>> dmezz...@gmail.com
>>
>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/JGIm0Ej6jDI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/702f3cd1-c887-4003-9993-aa70998a5b1a%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/42f6ff20-b4ae-4974-ac8f-7ea33e32dcc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Using PRU with PocketBeagle: remoteproc problems

[Alex Bagehot]

Hi Ken,
Having recently also bought a pocket beagle(my first), I ran through these
steps from Jason, as he suggested in another thread recently, successfully
: https://gist.github.com/jadonk/2ecf864e1b3f250bad82c0eae12b7b64
I thought it would be instructive to work out how to run the example you
tried also though. Basically taking the working gist and resolving issues
with your example as they appear.
Resulting in:

Received 100 messages, closing /dev/rpmsg_pru31
ie. success. It did a thing.
Thanks,
Alex

On Tue, Nov 14, 2017 at 7:10 AM, Ken Shirriff 
wrote:

> I got a PocketBeagle and I want to try out the PRU on it. Everything seems
> different from the PRUSSDRV stuff I'm used to. I can't get remoteproc to
> work, so I wanted to know which kernel and interfaces I should use.
>
> Specifically, I'm running the 2017-10-10 Stretch IoT build from
> http://beagleboard.org/latest-images
>
Yep. which is:

*debian@beaglebone*:*~/hello*$ uname -a

Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l
GNU/Linux


> I tried running the remoteproc "Hello world" from here
> .
> First, I ran into problems with stdint.h not found; I eventually found it
> in /usr/share/ti/cgt-pru/include - is that the right include path to use?
>
Yes based on the gist.

I also got some linking errors:

/usr/bin/clpru -z hello.cmd -o /home/debian/hello/pru0/am335x-pru0-fw
/home/debian/hello/pru0//main0.object
-l/usr/lib/ti/pru-software-support-package/lib/rpmsg_lib.lib

warning: automatic RTS selection:  attempt to automatically link in index
   library "libc.a" failed; file not found
warning: entry-point symbol "_c_int00" undefined
warning: no suitable entry-point found; setting to 0

Adding in another include based on the gist fixed them.

/usr/bin/clpru -z hello.cmd -i/usr/share/ti/cgt-pru/lib -o
/home/debian/hello/pru1/am335x-pru1-fw
/home/debian/hello/pru1//main1.object
-l/usr/lib/ti/pru-software-support-package/lib/rpmsg_lib.lib



Now built it needs to be deployed:

Initially I got an error deploying to pru1 as I just changed 4a334000.pru0
to 4a334000.pru1.
It wasn't hard to find the right ID:

debian@beaglebone:~/hello$ grep pru1 /var/log/messages |head -1
Oct 10 12:07:05 beaglebone kernel: [   11.700167]  remoteproc1:
4a338000.pru1 is available

With this in hand I just wrote a quick sudoable script :

debian@beaglebone:~/hello$ cat a.sh
set -x
dmesg --clear
echo "4a334000.pru0" > /sys/bus/platform/drivers/pru-rproc/unbind
echo "4a334000.pru0" > /sys/bus/platform/drivers/pru-rproc/bind
echo "4a338000.pru1" > /sys/bus/platform/drivers/pru-rproc/unbind
echo "4a338000.pru1" > /sys/bus/platform/drivers/pru-rproc/bind

Which produced:


debian@beaglebone:~/hello$ sudo ./a.sh && dmesg
+ dmesg --clear
+ echo 4a334000.pru0
+ echo 4a334000.pru0
+ echo 4a338000.pru1
+ echo 4a338000.pru1
[ 7750.734933] pru-rproc 4a334000.pru0: pru_rproc_remove: removing rproc
4a334000.pru0
[ 7750.744148] ti-pruss 4a30.pruss: unconfigured system_events =
0x0003 host_intr = 0x0005
[ 7750.744179]  remoteproc2: stopped remote processor 4a334000.pru0
[ 7750.744387]  remoteproc2: releasing 4a334000.pru0
[ 7750.751046]  remoteproc2: 4a334000.pru0 is available
[ 7750.751076]  remoteproc2: Note: remoteproc is still under development
and considered experimental.
[ 7750.751085]  remoteproc2: THE BINARY FORMAT IS NOT YET FINALIZED, and
backward compatibility isn't yet guaranteed.
[ 7750.755059]  remoteproc2: powering up 4a334000.pru0
[ 7750.755101]  remoteproc2: Booting fw image am335x-pru0-fw, size 73588
[ 7750.755362] ti-pruss 4a30.pruss: configured system_events =
0x0003 intr_channels = 0x0005 host_intr = 0x0005
[ 7750.761686]  remoteproc2: remote processor 4a334000.pru0 is now up
[ 7750.762068] virtio_rpmsg_bus virtio0: rpmsg host is online
[ 7750.762127] virtio_rpmsg_bus virtio0: creating channel rpmsg-pru addr
0x1e
[ 7750.763089] rpmsg_pru rpmsg5: new rpmsg_pru device: /dev/rpmsg_pru30
[ 7750.763232]  remoteproc2: registered virtio0 (type 7)
[ 7750.763325] pru-rproc 4a334000.pru0: PRU rproc node /ocp/pruss@4a30
/pru0@4a334000 probed successfully
[ 7750.767206] pru-rproc 4a338000.pru1: pru_rproc_remove: removing rproc
4a338000.pru1
[ 7750.767237] pru-rproc 4a338000.pru1: stopping the manually booted PRU
core
[ 7750.767353] ti-pruss 4a30.pruss: unconfigured system_events =
0x host_intr = 0x0001
[ 7750.767368]  remoteproc1: stopped remote processor 4a338000.pru1
[ 7750.767476]  remoteproc1: releasing 4a338000.pru1
[ 7750.774260]  remoteproc1: 4a338000.pru1 is available
[ 7750.774289]  remoteproc1: Note: remoteproc is still under development
and considered experimental.
[ 7750.774298]  remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and
backward compatibility isn't yet guaranteed.
[ 7750.775770]  remoteproc1: powering up 4a338000.pru1
[ 7750.775800]  remoteproc1: Booting fw image am335x-pru1-fw, size 73588
[ 

[beagleboard] Is there a BeagleBone Black IMU cape?

[Kyle]

Does anyone know of a beaglebone cape with IMU capabilities that is still 
in production? I have found plenty that seem to be end-of-life.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/a22ea56c-9c93-4800-9187-59c063b2157a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Bluetooth on BBBW and BBGW

[ybeagle3]

On Monday, November 13, 2017 11:00:06 Stephane Charette wrote:
> Not familiar with Bluetooth. I own several BBBW and BBGW devices.  Is there
> a way to interconnect the devices using Bluetooth?
> 
> What would that mean -- does Bluetooth provide an IP address?  Is there an
> interface I can access from bash scripts?  An API from C/C++?
> 
> Thanks for pointers in the right direction, as I've obviously not played
> with Bluetooth before today.
> 
> Stéphane

There are a few ways to interconnect them with BT. It is easiest to describe 
things in terms of profiles (and easier to search for). 

- If you need just bare connectivity, i.e. the wireless equivalent of a serial 
port, you can use SPP. (Serial Port Profile). In the BlueZ docs, this is done 
by the rfcomm tool which can be controlled by a bash script. Once the link is 
made, it is for most purposes a serial port.

- If you want IP connectivity, you can run PPP on top of the SPP stuff (this is 
mostly the DUN profile without the AT commands). This is purely a point to 
point link.

-As mentioned in the response, there is the PAN profile. This is almost 
eithernet like. 

It sounds like you are asking for general information but is there a specific 
thing you want to do (share files, share small bits of info, etc)?

--  
Hunyue Yau
http://www.hy-research.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/8353829.FTAJLk9M1N%40acer0.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PWM from BeagleBone Blue to external motor controller.

[Adam Saenz]

Hi Phil,

Q1)  I would suggest looking at rc_pwm.c which is in the 
Robotics_Cape_Installer source code.  A comment in the code says that there 
are 3 PWM subsystems; subsystem (ss) 1 and 2 are used by the built in motor 
drivers but ss 0 can be accessed from UART1; which leads one to believe is 
the the UART for GPS based on the comment from the PinMux online manual. 
 But the online manual for RoboticsCape says that UART2 (not UART1) is for 
GPS so either the code comment is old/wrong or the documentation is wrong. 
 Looks like a bit of experimenting is required to figure out which UART 
port is the correct one, but my guess would be that UART2 is the correct 
one.  You can then look at rc_motors.c to see how the pwm functions are 
used to configure the pwm subsystem and set duty cycle and frequency.  All 
this should be done after a call to the PinMux API to configure the pins 
for PWM. 

Q2)  What is your level of comfort with electronics modifications?  Then 
motor PWM signals are not mapped directly to a connector but you could 
access them via a hardware hack.  Remove the built in motor driver chips 
and solder in wires to the appropriate pads.  You could also try soldering 
directly to the appropriate built in motor driver pins as well.  In either 
case your soldered in wires should be hot glued or RTV'd in place to 
provide some strain relief.  It's a total hardware hack but it would allow 
you to used the robotics cape software as is.  This is assuming your new 
motor driver also uses 2 extra pins to control direction and braking (CW, 
CCW, short-brake, and stop) same as the TB6612FNG chip.  If it does not 
they you'll have to use the GP0 or GP1 IO pins to provide that 
functionality as your new motor driver needs.  Honestly this approach may 
be better suited for the BBBlack as all required I/O is mapped directly to 
and the header pins; but then you would loose all the other built in 
features of the BBBlue/Robotics cape.

If it were me I would go with the first approach and configure GPS UART2 
for PWM output.  Let me know if you have any question with this approach 
and I can look at the code a bit closer.

Adam




On Sunday, November 12, 2017 at 8:31:03 PM UTC-8, Phillip Glau wrote:
>
> I'm trying to build a differential drive robot using some 6v motors with 
> encoders from Pololu. Their amperage exceeds the capabilities of the built 
> in motor controllers on the BB Blue.
>
> I've got a larger separate motor controller that will accept PWM signal 
> for control.
>
> Question 1: Which physical connector on the BeagleBone Blue do I connect 
> to in order to access 2 channels of PWM? I'm not clear how PinMux 
>  works as described in the 
> manual. I'm assuming it means that once I figure out which physical 
> connector to attach to, that I can then change the functionality to PWM. 
> (Seems like perhaps the GPS connector is the correct one??) Unfortunately 
> the online manual doesn't seem to give practical example code of this 
> functionality.
>
> Question 2: Is it possible to access the PWM signal of the built in motor 
> controllers? This would be ideal as then the external motor controller 
> would be functionally transparent to the roboticscape software that 
> already exists. Again, I can't figure out if this is possible or which 
> connectors to tie into to access the PWM signal that drives Motor Channels 
> 1 to 4
>
> Thanks in advance for any help you can provide.
>
> - Phil
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/31d88d85-80a8-44fc-8c62-abafec5fb083%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Unnecessary network data traffic

[William B]

Yes, I changed the default password for debian user and root user, but I 
didn't disable either. Should I enable logging for everything or something 
specific?
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/f33729f8-b247-44d4-815d-8ad33a8a4e99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Rose-Hulman Embedded Linux Project Demos

[adamwiesler]

My project was to monitor data coming in from a CANbus and then display and 
graph the data on a webpage. More information can be found here 
, and a quick YouTube clip of the 
project in action is here .

-Adam

On Monday, November 13, 2017 at 4:01:18 PM UTC-5, Mark A. Yoder wrote:
>
> Tomorrow my embedded linux students are demoing their projects.  
>
> I'm having them reply to this message with a link the a wiki describing 
> the project.  You can also look under P here[1].
>
> Take a look at what they have done.
>
> --Mark
>
> [1] https://elinux.org/index.php?title=Category:ECE497 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/aaab66de-3dc1-45b4-b436-517d270347c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] PRU shared with Node-Red ??

[Michael Dalby]

Hi,


I wondered if there was a way to make a program running in the PRU 
available to a Node-Red implementation running on the same BBB??


For example if I had the PRU doing serial communications, could I 
read/export any data into a Node-Red flow?


Kind regards

Michael

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/cd4207c4-54f5-4abd-b8a9-e68153eb1403%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Using PRU with PocketBeagle: remoteproc problems

[Kumar Abhishek]

Which kernel version are you using? If it's the 4.9 version (most likely as 
it is the Stretch image), some additional steps are required because the 
binary won't start up automatically at boot as it does in kernel version 
4.4. 
This is a change that happened done going from 4.4-4.9.

To boot the binary, once you build and put it into /lib/firmware you would 
have to manually boot it.

   - Go to /sys/class/remoteproc in a root shell
   - There should be 3 directories, remoteproc0, remoteproc1, remoteproc2. 
   To find which is the correct one for PRU0 for example, do: cat 
   /sys/class/remoteproc/remoteproc1/device/of_node/label . It should say 
   "pru0" (at least it does on my board)
   - Once you have found the correct remoteproc directory, cd into it. 
   Let's for example assume for PRU0 the directory is 
   /sys/class/remoteproc/remoteproc1
   - Then you have to set the name for the firmware you have copied into 
   /lib/firmware using: echo am335x-pru0-fw > firmware .
   - Then you have to start the device using: echo start > state . To stop 
   the PRU, do: echo stop > state .

I hope this should get the rpmsg driver to show up. Pastebin your kernel 
logs so that I can take a look.

Resource table is a way of signifying to the remoteproc driver:

   - the PRU interrupts it should configure on PRU boot,
   - virtqueues used for PRU<->Kernel communication

The resource table is placed in an ELF section that the remoteproc kernel 
driver reads before it loads the firmware into the PRUs.

Regards
Abhishek


On Tuesday, November 14, 2017 at 12:40:02 PM UTC+5:30, Ken Shirriff wrote:
>
> I got a PocketBeagle and I want to try out the PRU on it. Everything seems 
> different from the PRUSSDRV stuff I'm used to. I can't get remoteproc to 
> work, so I wanted to know which kernel and interfaces I should use.
>
> Specifically, I'm running the 2017-10-10 Stretch IoT build from 
> http://beagleboard.org/latest-images
> I tried running the remoteproc "Hello world" from here 
> .
> First, I ran into problems with stdint.h not found; I eventually found it 
> in /usr/share/ti/cgt-pru/include - is that the right include path to use?
> When I ran the program, I got a bunch of warnings:
>
> Note: remoteproc is still under development and considered experimental.
> THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't 
> yet guaranteed.
>
> And then the program died with "Failed to open /dev/rpmsg_pru31"
>
> So: is remoteproc what I should be using, or is it still "experimental"? 
> Am I using the right kernel? And what is "resource_table.h"?
>
> Thanks for any suggestions,
> Ken
>
>
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/d8287599-fa69-4c7a-9f53-665fec4d06cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unnecessary network data traffic

[Robert Nelson]

On Tue, Nov 14, 2017 at 7:01 AM, William B  wrote:
> Hello! I've installed a standalone application in a Beaglebone Black and
> apparently the data traffic on the network has increased a lot. My customer
> could not prove that it was the BBB yet, but I believe it's not, since
> everything in it's a simple I/Os control, monitoring by a REST application
> made in NodeJS/Javascript, with the data being stored in MySQL database,
> everything installed in the BBB and without access to other external
> applications. BBB is connected to the network, but in theory, it should not
> be generating traffic.
>
> Is there any reason for BBB to be generating data traffic unnecessarily?

Did you change the default password and atleast disable the root account?

Best to log into it and monitor the BBB to see if it's doing anything
other then what you setup..

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/CAOCHtYhSLbwpC06GY_-WkdGKutfKLanc_gg0s_t1UueW5f8RuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Kernel and uboot source code for Beagle bone green wireless

[drhunter95]

Hi Trinadh,
This is not actually an ERROR, it should be a warning as the WL18xx driver 
will create a default configuration and use it instead. So it is probably 
not the cause of your failure to boot.

Having said that using the wl18xx-conf.bin that Robert pointed you to in 
your filesystem is the best solution. 
Iain 

On Monday, 13 November 2017 17:51:58 UTC, Trinadh Morla wrote:
>
> Hi,
>
> While porting Linux kernel into beagle bone green wireless board i am 
> getting error "wlcore: ERROR could not get configuration binary 
> ti-connectivity/wl18xx-conf.bin: -2" and then board was not booting up. Can 
> you please help to this issue?
>
> Thanks,
> Trinadh.
>
>
> On Mon, Nov 13, 2017 at 8:16 PM, Robert Nelson  > wrote:
>
>> On Mon, Nov 13, 2017 at 12:55 AM,   
>> wrote:
>> > Hi,
>> >
>> > Could you please help me where can i get u boot and Linux kernel source 
>> code
>> > to support beagle-bone green wireless board?
>>
>> Both are mainline:
>>
>> https://eewiki.net/display/linuxonarm/BeagleBone+Black
>>
>> 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/b98e3642-750c-4d67-842d-94a8cd86d877%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Rose-Hulman Embedded Linux Project Demos

[Daniel Neelappa]

Hi,

I was able to communicate with my car through my beaglebone blue. 

It is still an active project, as I'm trying to decipher what message 
causes a certain action.

https://elinux.org/ECE497_Car_CANBUS#Highlights


Thanks,
Daniel

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/ba3f68dd-e6f3-467d-8f0c-ac2fc4dba0f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Rose-Hulman Embedded Linux Project Demos

[Yvette Weng]

We are building a project to use webcam to capture face and compare with 
the database to identify the person. 
Here is our wiki page. Wiki 


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/576597a3-4489-4c37-b0b2-497751bd9605%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to run programms automatically at boot up in beaglebone black

[William B]

Hello. I used PM2 to do what you described and it worked very well. There's 
also "Forever" that is recommended by the community, but I think PM2 is 
more complete.

PM2 Example:
https://www.digitalocean.com/community/tutorials/how-to-set-up-a-node-js-application-for-production-on-ubuntu-16-04

https://www.digitalocean.com/community/tutorials/how-to-use-pm2-to-setup-a-node-js-production-environment-on-an-ubuntu-vps

FOREVER Example:
https://causeyourestuck.io/2016/04/30/run-node-js-script-startup/


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/28921e7d-0437-4183-a34d-3eaac69e6b45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unnecessary network data traffic

[William B]

Hello! I've installed a standalone application in a Beaglebone Black and 
apparently the data traffic on the network has increased a lot. My customer 
could not prove that it was the BBB yet, but I believe it's not, since 
everything in it's a simple I/Os control, monitoring by a REST application 
made in NodeJS/Javascript, with the data being stored in MySQL database, 
everything installed in the BBB and without access to other external 
applications. BBB is connected to the network, but in theory, it should not 
be generating traffic.

Is there any reason for BBB to be generating data traffic unnecessarily?

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/36a727d7-3d33-466f-84a1-c4597512c3f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Rose-Hulman Embedded Linux Project Demos

[Andrew Mueller]

We created a small scale mobile telepresence robot that we can control 
wirelessly.
Wiki page with more information is available here 
.

On Monday, November 13, 2017 at 4:01:18 PM UTC-5, Mark A. Yoder wrote:
>
> Tomorrow my embedded linux students are demoing their projects.  
>
> I'm having them reply to this message with a link the a wiki describing 
> the project.  You can also look under P here[1].
>
> Take a look at what they have done.
>
> --Mark
>
> [1] https://elinux.org/index.php?title=Category:ECE497 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/8189afce-3771-4d9e-871b-dff7843f0c7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Serial Communication on Beaglebone Black

[wm . bain . jr]

Well, I stumbled across this discussion because I just found out today after 
wasting hours that my Beaglebone appears to have RX and TX mislabeled 
(swapped). Maybe that's the source of some of the confusion that others are 
having, too? I am accustomed to always connecting TX to RX and vice-versa 
between components, but to get the Beaglebone to work with all my other serial 
devices (that work in the usual way with other development boards), I have to 
connect RX to RX and TX to TX! Mind you, this is a brand new PocketBeagle, and 
maybe the developers just got this one board backwards, but maybe all the BBs 
have the same screwy labeling?

-- Will 

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