Re: [beagleboard] TI Processor SDK Linux compatibility?

2019-10-24 Thread Geza Kuhmann 

I'm trying to use the latest Linux Processor SDK for AM57x from here 
 on BBAI.
(I just noticed that they released version 06_01_00_08 today/yesterday, I 
was trying with the previous version 06_01_00_07).

As far as I see now, BBAI is not officially supported by the Processor SDK.
What I tried was to make an SD card using the SDK's create-sdcard script, 
but it does not boot on the BBAI.




On Thursday, October 24, 2019 at 3:40:56 AM UTC+2, lazarman wrote:
>
> Hi
>
> Problem Description not very clear.
>
> What HW failed to boot ?
>
> If I had to guess you used this SDK? 
> https://training.ti.com/node/1138863
>
> and ran it on a BBAI?
>
> You probably have better chance of getting help with details.
>
>
> Sent from Yahoo Mail on Android 
> 
>
> On Wed, Oct 23, 2019 at 10:00 AM, geza@gmail.com 
> > wrote:
> Hi,
>
> I'm wondering if BBAI is compatible with current Processor SDK Linux from 
> TI (or rather vice-versa)?
> The kernel is different there and I was not able to boot from SD card 
> created with the utilities from the SDK.
> I've an application currently running on OMAP L138, Linux + TI RTOS on DSP 
> (using SDK's SysLink/IPC) which I'd like to port to BBAI, to leverage the 
> increased DSP power. I'd like to avoid merging/mixing the Debian and 
> SDK/Arago world if possible...
>
> Any hints?
> Thx,
>
> Geza
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagl...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/f65c6388-0398-4850-85f6-5a5259578f8d%40googlegroups.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/e89be51a-7723-4987-99c1-037ae7ecfa43%40googlegroups.com.

Re: [beagleboard] Re: wher to buy beagleboards X15 ?

2019-10-24 Thread Robert Nelson 
On Thu, Oct 24, 2019 at 1:33 AM  wrote:
>
> Thank you Robert for your answer.
>
> I know SEEED. there is no product available until december-january As I know.

our timeline showed sooner then that..

>
> I wonder why this lack of parts available. is there a real production problem 
> or other problem?

Not that i'm aware of..

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/CAOCHtYiArFVmnSSQMbJ66RxPe36sHc1OL5X6ATpvkif88M0N0g%40mail.gmail.com.

[beagleboard] Notes about Black , Green and Pocketbeagle GamePup and TechLab cape learning

2019-10-24 Thread Lee T. Davy 
Will Beaglebone ever replace Raspberry Pi for learning about computers ?

In 2014 I joined a makerspace in Sommerville, Ma USA Artisans Asylum near 
MIT so there were makers from local tech colleges as mentors.
The in house backgrounds were friendly and knowledgeable.
They readily share their knowledge.
I began in 2014 to want a home CNC based on EMC 
 (later LinuxCNC 
, Machinekit 
) like the Black Foot CNC 


Costs were an obstacle but I could join the makerspace as a volunteer and 
use the tools available.
On Wednesday night there was and still is a public welcome Circuit Hacking 
electronics night among other classes 
.
I learned about Arduino for my first device in three decades since being 
into PDP-11 computers at Digital Equipment Corporation (DEC).
That was the X11 in the 1980's 


I asked where I could replace the large PC with smaller for a smaller CNC 
and was directed to Beaglebone Black  as a 
better choice than
Raspberry Pi on Arduino.

I bought a Black and plugged it in and have never regretted the decision.
Later in 2016 I attended some Meet Up meetings to learn about 3D printers
 and found out about Beaglebone Green  used 
in the Phidias LLC Athena 
 
(<-Notes 
here).

Now in 2019 I want to find a group and take notes on how to make a video 
game.
I plan to use the new Pocket BeagleBone capes with GamePup 
 as a game controller over Wifi and 
Bluetooth with off the shelf devices
 as I am not into designing and building circuits.
The TechLab  is better for learning as it 
is designed to support e-ale classes  already being 
taught.

*I want to start a discussion here about why chose Beaglebone over 
Raspberry Pi or the inverse choice.*


*Also, since I am famous for confusing things with too many topics I want 
to start notations for collaborating on the GamePup controller.*

I have tried to use BBB.io/p for teaching concepts as I learn how to do the 
stuff I want.
I have already run into problems starting and making changes on my  
Hackster.io projects that appear
 on my BBB.io profile so I have created a Slack and Discord approach to do 
the notations.

First thing is to get a fix for the Game Pup frame buffer flipped RED and 
Green colors as was done by others on Adafruit Arduino code.
After that will be adding battery, Wifi, Bluetooth, MP3 and Midi 
capabilities to the cape. 

*I play GAMES as you see in the hidden links in this message and am looking 
for others to become contributors in*
*this decade (or more) project.*

My email is Play at Cool Games dot Net as I am doing business
 as Cool Games Network (since 2000) as it has evolved from Event Video 
Multimedia (since 1990)


Thanks in advance
Lee T. Davy

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/f23eb02c-3cc8-4202-bd7a-4e800cf13810%40googlegroups.com.

[beagleboard] BBAI: Assistance requested with configuring P9_15 as an output gpio

2019-10-24 Thread Jon Morss 
Hi,

I've been trying to configure a header gpio pin such as P9_15 as an output 
port on the BBAI but I am having no luck.  This pin is used with the Cloud9 
Python and JS examples but it is not working so I have tried to enable it 
manually. 

I've added the following in the am5729-beagleboneai.dts file and run make 
and make install and a reboot:

cape_pins: cape_pins {
compatible = "gpio-leds";
pinctrl-names = "default";
gpios = <&gpio3 12 GPIO_ACTIVE_HIGH>;
pinctrl-0 = <&cape_pins_default>;
};



 DRA7XX_CORE_IOPAD(0x3514, PIN_OUTPUT | MUX_MODE14) /* AG4: P9.15: 
vin1a_d8.gpio3_12 - MDIR2A */
 


The config-pins tools shows

debian@beaglebone:~$ sudo config-pin -q p9.15
[sudo] password for debian: 
P9_15 pinmux file not found!
Pin has no cape: P9_15



The show-pins tools shows:

debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl 
Can't locate Inline/Files.pm in @INC (you may need to install the 
Inline::Files module) (@INC contains: /etc/perl 
/usr/local/lib/arm-linux-gnueabihf/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/arm-linux-gnueabihf/perl5/5.24 /usr/share/perl5 
/usr/lib/arm-linux-gnueabihf/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at 
/opt/scripts/device/bone/show-pins.pl line 11.
BEGIN failed--compilation aborted at /opt/scripts/device/bone/show-pins.pl 
line 11.



This is the output of version.sh:

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[b4e40ed94bc1e15bb291d10af48e0e9893864197]
model:[BeagleBoard.org_BeagleBone_AI]
dogtag:[BeagleBoard.org Debian Image 2019-08-03]
UBOOT: Booted Device-Tree:[am5729-beagleboneai.dts]
kernel:[4.19.73-ti-r29]
nodejs:[v6.17.0]
/boot/uEnv.txt Settings:
pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
]
pkg:[bb-cape-overlays]:[4.4.20191017.0-0rcnee0~stretch+20191017]
pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20190227.1-0rcnee0~stretch+20190327]
pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep remoteproc 
admin spi tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyS0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 
rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=80 quiet 
video=HDMI-A-1:1920x1080@60e]
dmesg | grep remote
[1.209487] remoteproc remoteproc0: 4b234000.pru is available
[1.209792] remoteproc remoteproc1: 4b238000.pru is available
[1.210130] remoteproc remoteproc2: 4b2b4000.pru is available
[1.210420] remoteproc remoteproc3: 4b2b8000.pru is available
[1.580068] remoteproc remoteproc4: 5882.ipu is available
[1.580495] remoteproc remoteproc5: 5502.ipu is available
[1.580963] remoteproc remoteproc6: 4080.dsp is available
[1.581450] remoteproc remoteproc7: 4100.dsp is available
[1.582238] remoteproc remoteproc4: Direct firmware load for dra7-ipu1-fw
.xem4 failed with error -2
[1.582247] remoteproc remoteproc4: powering up 5882.ipu
[1.582322] remoteproc remoteproc4: Direct firmware load for dra7-ipu1-fw
.xem4 failed with error -2
[1.582330] remoteproc remoteproc4: request_firmware failed: -2
[1.588375] remoteproc remoteproc5: Direct firmware load for dra7-ipu2-fw
.xem4 failed with error -2
[1.588383] remoteproc remoteproc5: powering up 5502.ipu
[1.588455] remoteproc remoteproc5: Direct firmware load for dra7-ipu2-fw
.xem4 failed with error -2
[1.588463] remoteproc remoteproc5: request_firmware failed: -2
[1.594532] remoteproc remoteproc6: Direct firmware load for dra7-dsp1-fw
.xe66 failed with error -2
[1.594542] remoteproc remoteproc6: powering up 4080.dsp
[1.594630] remoteproc remoteproc6: Direct firmware load for dra7-dsp1-fw
.xe66 failed with error -2
[1.594639] remoteproc remoteproc6: request_firmware failed: -2
[1.600688] remoteproc remoteproc7: Direct firmware load for dra7-dsp2-fw
.xe66 failed with error -2
[1.600697] remoteproc remoteproc7: powering up 4100.dsp
[1.600770] remoteproc remoteproc7: Direct firmware load for dra7-dsp2-fw
.xe66 failed with error -2
[1.600777] remoteproc remoteproc7: request_firmware failed: -2
dmesg | grep pru
[1.209487] remoteproc remoteproc0: 4b234000.pru is available
[1.209560] pru-rproc 4b234000.pru: PRU rproc node pru@4b234000 probed 
successfully
[1.209792] remoteproc remoteproc1: 4b238000.pru is available
[1.209874] pru-rproc 4b238000.pru: PRU rproc node pru@4b238000 probed 
successfully
[1.210130] remoteproc remoteproc2: 4b2b4000.pru is available
[1.210200] pru-rproc 4b2b4000.pru: PRU rproc node pru@4b2b4000 probed 
successfully
[1.210420] remoteproc remoteproc3: 4b2b8000.pru

Re: [beagleboard] BBAI: Assistance requested with configuring P9_15 as an output gpio

2019-10-24 Thread Robert Nelson 
On Thu, Oct 24, 2019 at 10:12 AM Jon Morss  wrote:
>
> Hi,
>
> I've been trying to configure a header gpio pin such as P9_15 as an output 
> port on the BBAI but I am having no luck.  This pin is used with the Cloud9 
> Python and JS examples but it is not working so I have tried to enable it 
> manually.
>
> I've added the following in the am5729-beagleboneai.dts file and run make and 
> make install and a reboot:
>
> cape_pins: cape_pins {
> compatible = "gpio-leds";
> pinctrl-names = "default";
> gpios = <&gpio3 12 GPIO_ACTIVE_HIGH>;
> pinctrl-0 = <&cape_pins_default>;
> };
>
>
>
>  DRA7XX_CORE_IOPAD(0x3514, PIN_OUTPUT | MUX_MODE14) /* AG4: P9.15: 
> vin1a_d8.gpio3_12 - MDIR2A */

^ looks correct..


> The config-pins tools shows
>
> debian@beaglebone:~$ sudo config-pin -q p9.15
> [sudo] password for debian:
> P9_15 pinmux file not found!
> Pin has no cape: P9_15

Don't use config-pin the bbai..

> The show-pins tools shows:
>
> debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl
> Can't locate Inline/Files.pm in @INC (you may need to install the 
> Inline::Files module) (@INC contains: /etc/perl 
> /usr/local/lib/arm-linux-gnueabihf/perl/5.24.1 /usr/local/share/perl/5.24.1 
> /usr/lib/arm-linux-gnueabihf/perl5/5.24 /usr/share/perl5 
> /usr/lib/arm-linux-gnueabihf/perl/5.24 /usr/share/perl/5.24 
> /usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at 
> /opt/scripts/device/bone/show-pins.pl line 11.
> BEGIN failed--compilation aborted at /opt/scripts/device/bone/show-pins.pl 
> line 11.

sudo apt install libinline-files-perl


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/CAOCHtYiApGknihWCTdh5B0Fz75pOTkqoA4Ka%2BN0OUxCH8V5iWw%40mail.gmail.com.

Re: [beagleboard] BBAI: Assistance requested with configuring P9_15 as an output gpio

2019-10-24 Thread jonnymo 
Oh, duh!  I should  have caught that missing lib.
Okay, so the output of show-pins shows P.15 but it neither shows as up or
down.  Is this correct?

*debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl
 | grep "P9.15"*
*P9.15 69  AG4 e fast gpio3_12*


Also, is the '69' value the gpio number that is used to enable this?
Such as :

*debian@beaglebone:~$ sudo echo 69 > /sys/class/gpio/export *
*debian@beaglebone:~$ sudo echo out > /sys/class/gpio/gpio69/direction *
*debian@beaglebone:~$ sudo echo 1 > /sys/class/gpio/gpio69/value*


Since this is gpio3_12 I was thinking it was '108' considering the 32x3+12
calculation as with the BB Black.
Neither 69 or 108 seems to work though.

Also, are the failed messages from the version output something to be
concerned about?

*[1.582238] remoteproc remoteproc4: Direct firmware load for
dra7-ipu1-fw.xem4 failed with error -2*
*[1.582247] remoteproc remoteproc4: powering up 5882.ipu*
*[1.582322] remoteproc remoteproc4: Direct firmware load for
dra7-ipu1-fw.xem4 failed with error -2*
*[1.582330] remoteproc remoteproc4: request_firmware failed: -2*
*[1.588375] remoteproc remoteproc5: Direct firmware load for
dra7-ipu2-fw.xem4 failed with error -2*
*[1.588383] remoteproc remoteproc5: powering up 5502.ipu*
*[1.588455] remoteproc remoteproc5: Direct firmware load for
dra7-ipu2-fw.xem4 failed with error -2*
*[1.588463] remoteproc remoteproc5: request_firmware failed: -2*
*[1.594532] remoteproc remoteproc6: Direct firmware load for
dra7-dsp1-fw.xe66 failed with error -2*
*[1.594542] remoteproc remoteproc6: powering up 4080.dsp*
*[1.594630] remoteproc remoteproc6: Direct firmware load for
dra7-dsp1-fw.xe66 failed with error -2*
*[1.594639] remoteproc remoteproc6: request_firmware failed: -2*
*[1.600688] remoteproc remoteproc7: Direct firmware load for
dra7-dsp2-fw.xe66 failed with error -2*
*[1.600697] remoteproc remoteproc7: powering up 4100.dsp*
*[1.600770] remoteproc remoteproc7: Direct firmware load for
dra7-dsp2-fw.xe66 failed with error -2*
*[1.600777] remoteproc remoteproc7: request_firmware failed: -2*
*dmesg | grep pru*



Thanks,

Jon

On Thu, Oct 24, 2019 at 8:24 AM Robert Nelson 
wrote:

> On Thu, Oct 24, 2019 at 10:12 AM Jon Morss  wrote:
> >
> > Hi,
> >
> > I've been trying to configure a header gpio pin such as P9_15 as an
> output port on the BBAI but I am having no luck.  This pin is used with the
> Cloud9 Python and JS examples but it is not working so I have tried to
> enable it manually.
> >
> > I've added the following in the am5729-beagleboneai.dts file and run
> make and make install and a reboot:
> >
> > cape_pins: cape_pins {
> > compatible = "gpio-leds";
> > pinctrl-names = "default";
> > gpios = <&gpio3 12 GPIO_ACTIVE_HIGH>;
> > pinctrl-0 = <&cape_pins_default>;
> > };
> >
> >
> >
> >  DRA7XX_CORE_IOPAD(0x3514, PIN_OUTPUT | MUX_MODE14) /* AG4: P9.15:
> vin1a_d8.gpio3_12 - MDIR2A */
>
> ^ looks correct..
>
>
> > The config-pins tools shows
> >
> > debian@beaglebone:~$ sudo config-pin -q p9.15
> > [sudo] password for debian:
> > P9_15 pinmux file not found!
> > Pin has no cape: P9_15
>
> Don't use config-pin the bbai..
>
> > The show-pins tools shows:
> >
> > debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl
> > Can't locate Inline/Files.pm in @INC (you may need to install the
> Inline::Files module) (@INC contains: /etc/perl
> /usr/local/lib/arm-linux-gnueabihf/perl/5.24.1 /usr/local/share/perl/5.24.1
> /usr/lib/arm-linux-gnueabihf/perl5/5.24 /usr/share/perl5
> /usr/lib/arm-linux-gnueabihf/perl/5.24 /usr/share/perl/5.24
> /usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at
> /opt/scripts/device/bone/show-pins.pl line 11.
> > BEGIN failed--compilation aborted at /opt/scripts/device/bone/
> show-pins.pl line 11.
>
> sudo apt install libinline-files-perl
>
>
> 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/CAOCHtYiApGknihWCTdh5B0Fz75pOTkqoA4Ka%2BN0OUxCH8V5iWw%40mail.gmail.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/CAG99bkpE-gX9PjaOwqXJ6K0wZMsikQaVWNNGiOFv3Bi1i11fuA%40mail.gmail.com.

Re: [beagleboard] BBAI: Assistance requested with configuring P9_15 as an output gpio

2019-10-24 Thread Jason Kridner 
On Thu, Oct 24, 2019 at 12:39 PM jonnymo  wrote:

> Oh, duh!  I should  have caught that missing lib.
> Okay, so the output of show-pins shows P.15 but it neither shows as up or
> down.  Is this correct?
>
> *debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl
>  | grep "P9.15"*
> *P9.15 69  AG4 e fast gpio3_12*
>
>
> Also, is the '69' value the gpio number that is used to enable this?
> Such as :
>
> *debian@beaglebone:~$ sudo echo 69 > /sys/class/gpio/export *
> *debian@beaglebone:~$ sudo echo out > /sys/class/gpio/gpio69/direction *
> *debian@beaglebone:~$ sudo echo 1 > /sys/class/gpio/gpio69/value*
>
>
> Since this is gpio3_12 I was thinking it was '108' considering the 32x3+12
> calculation as with the BB Black.
> Neither 69 or 108 seems to work though.
>

There’s no gpio0 on AM57x, so it is 2*32 +12 = 76.


> Also, are the failed messages from the version output something to be
> concerned about?
>
> *[1.582238] remoteproc remoteproc4: Direct firmware load for
> dra7-ipu1-fw.xem4 failed with error -2*
> *[1.582247] remoteproc remoteproc4: powering up 5882.ipu*
> *[1.582322] remoteproc remoteproc4: Direct firmware load for
> dra7-ipu1-fw.xem4 failed with error -2*
> *[1.582330] remoteproc remoteproc4: request_firmware failed: -2*
> *[1.588375] remoteproc remoteproc5: Direct firmware load for
> dra7-ipu2-fw.xem4 failed with error -2*
> *[1.588383] remoteproc remoteproc5: powering up 5502.ipu*
> *[1.588455] remoteproc remoteproc5: Direct firmware load for
> dra7-ipu2-fw.xem4 failed with error -2*
> *[1.588463] remoteproc remoteproc5: request_firmware failed: -2*
> *[1.594532] remoteproc remoteproc6: Direct firmware load for
> dra7-dsp1-fw.xe66 failed with error -2*
> *[1.594542] remoteproc remoteproc6: powering up 4080.dsp*
> *[1.594630] remoteproc remoteproc6: Direct firmware load for
> dra7-dsp1-fw.xe66 failed with error -2*
> *[1.594639] remoteproc remoteproc6: request_firmware failed: -2*
> *[1.600688] remoteproc remoteproc7: Direct firmware load for
> dra7-dsp2-fw.xe66 failed with error -2*
> *[1.600697] remoteproc remoteproc7: powering up 4100.dsp*
> *[1.600770] remoteproc remoteproc7: Direct firmware load for
> dra7-dsp2-fw.xe66 failed with error -2*
> *[1.600777] remoteproc remoteproc7: request_firmware failed: -2*
> *dmesg | grep pru*
>
>
>
> Thanks,
>
> Jon
>
> On Thu, Oct 24, 2019 at 8:24 AM Robert Nelson 
> wrote:
>
>> On Thu, Oct 24, 2019 at 10:12 AM Jon Morss  wrote:
>> >
>> > Hi,
>> >
>> > I've been trying to configure a header gpio pin such as P9_15 as an
>> output port on the BBAI but I am having no luck.  This pin is used with the
>> Cloud9 Python and JS examples but it is not working so I have tried to
>> enable it manually.
>> >
>> > I've added the following in the am5729-beagleboneai.dts file and run
>> make and make install and a reboot:
>> >
>> > cape_pins: cape_pins {
>> > compatible = "gpio-leds";
>> > pinctrl-names = "default";
>> > gpios = <&gpio3 12 GPIO_ACTIVE_HIGH>;
>> > pinctrl-0 = <&cape_pins_default>;
>> > };
>> >
>> >
>> >
>> >  DRA7XX_CORE_IOPAD(0x3514, PIN_OUTPUT | MUX_MODE14) /* AG4: P9.15:
>> vin1a_d8.gpio3_12 - MDIR2A */
>>
>> ^ looks correct..
>>
>>
>> > The config-pins tools shows
>> >
>> > debian@beaglebone:~$ sudo config-pin -q p9.15
>> > [sudo] password for debian:
>> > P9_15 pinmux file not found!
>> > Pin has no cape: P9_15
>>
>> Don't use config-pin the bbai..
>>
>> > The show-pins tools shows:
>> >
>> > debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl
>> > Can't locate Inline/Files.pm in @INC (you may need to install the
>> Inline::Files module) (@INC contains: /etc/perl
>> /usr/local/lib/arm-linux-gnueabihf/perl/5.24.1 /usr/local/share/perl/5.24.1
>> /usr/lib/arm-linux-gnueabihf/perl5/5.24 /usr/share/perl5
>> /usr/lib/arm-linux-gnueabihf/perl/5.24 /usr/share/perl/5.24
>> /usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at
>> /opt/scripts/device/bone/show-pins.pl line 11.
>> > BEGIN failed--compilation aborted at /opt/scripts/device/bone/
>> show-pins.pl line 11.
>>
>> sudo apt install libinline-files-perl
>>
>>
>> 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/CAOCHtYiApGknihWCTdh5B0Fz75pOTkqoA4Ka%2BN0OUxCH8V5iWw%40mail.gmail.com
>> .
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To

[beagleboard] Re: Notes about Black , Green and Pocketbeagle GamePup and TechLab cape learning

2019-10-24 Thread Dennis Lee Bieber 
On Thu, 24 Oct 2019 07:19:34 -0700 (PDT), "Lee T. Davy"
 declaimed the
following:

>Will Beaglebone ever replace Raspberry Pi for learning about computers ?
>

Probably not...

The Beaglebone series appears optimized for use as embedded Linux
controllers. They provide a large number of binary GPIO, SPI, I2C, multiple
UARTs, along with ANALOG inputs and outputs. They have (at least the BBB)
only one USB port. But they tend toward slower single core processors
(ignoring the cryptic PRUs), small amount of RAM. The stand-alone Cloud-9
environment is the "friendly" interface for programming, favoring
Bonescript via node.js (though Cloud-9 does support Python too).


The R-Pi was billed as a cheap Linux computer using Python as the
primary programming language for teaching purposes. It really only has a
few binary GPIO, SPI, I2C -- but no analog I/O. Typically four USB ports.
The newer ones have 64-bit quad-core processors (though the normal OS is
just 32-bit for compatibility across the line) and more RAM -- but lack any
coprocessors. Really meant to be used with an HDMI monitor and local
keyboard/mouse.

Compare:
BBAI: 1.5GHz dual Cortex-A15, 1GB ? RAM, 4 PRU, 4 EVE, 2 DSP, 16GB eMMC,
USB2, USB3?, WiFi

$117+
BBB: 1GHz Cortex-A8, 512MB DDR3 RAM, 2 PRU, 4GB eMMC, USB2

$55+


R-Pi 4B: 1.5GHz quad Cortex-A72, 4GB DDR4 RAM, USB3, WiFi

$55
R-Pi 4B: 1.5GHz quad Cortex-A72, 1GB DDR4 RAM, USB3, WiFi

$35
R-Pi 3B+: 1.4GHz quad Cortex-A53, 1GB DDR2 RAM, USB2, WiFi

$35

The R-Pi foundation seems to release a new model every 12-18 months,
whereas Beagles appear to be targeted for long-term stability (what did I
read, 10 years production life?)

-- 
Dennis L Bieber

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/mfo3reh3n3rf4kitjh4qhsf7leqjsuj16r%404ax.com.

[beagleboard] bonescript@0.7.4-beta1 published

2019-10-24 Thread Jason Kridner 
Realized I hadn't published the work already done on putting BeagleBone AI 
GPIO pins into the node.js BoneScript library.

Any testing on this version would really be appreciated.


debian@beaglebone:/var/lib/cloud9/sensors$ *cd /usr/local/lib*
debian@beaglebone:/usr/local/lib$ *sudo npm install --unsafe-perm 
bonescript@0.7.4-beta1* 
npm WARN deprecated coffee-script@1.9.1: CoffeeScript on NPM has moved to 
"coffeescript" (no hyphen)
npm WARN deprecated json3@3.2.6: Please use the native JSON object instead 
of JSON 3
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead 
of JSON 3
colors@1.0.3 node_modules/winston/node_modules/colors -> node_modules/colors
cycle@1.0.3 node_modules/winston/node_modules/cycle -> node_modules/cycle
eyes@0.1.8 node_modules/winston/node_modules/eyes -> node_modules/eyes
isstream@0.1.2 node_modules/winston/node_modules/isstream -> 
node_modules/isstream
pkginfo@0.3.1 node_modules/winston/node_modules/pkginfo -> 
node_modules/pkginfo
stack-trace@0.0.10 node_modules/winston/node_modules/stack-trace -> 
node_modules/stack-trace
/usr/local/lib
└─┬ bonescript@0.7.4-beta1
  └── winston@2.1.1

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.1.2 
(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 
fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: 
{"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 
(node_modules/sensortag/node_modules/noble/node_modules/xpc-connection):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 
xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: 
{"os":"linux","arch":"arm"})
npm WARN enoent ENOENT: no such file or directory, open 
'/usr/local/lib/package.json'
npm WARN lib No description
npm WARN lib No repository field.
npm WARN lib No README data
npm WARN lib No license field.
debian@beaglebone:/usr/local/lib$ *node -pe 
"require('bonescript').bone.getPinObject('p9.15').ai.gpio"*
76


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to 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/28ae9679-ddb7-42e3-9437-aa56dacb147d%40googlegroups.com.

[beagleboard] Re: TIDL Classification example not properly identify objects

2019-10-24 Thread Dobrin Alexiev 


Thank you, Jason. 

Applying the changes  made the classification demo reliably working. 

No crashes. 

Dobrin



On Wednesday, October 23, 2019 at 11:20:21 AM UTC-4, Jason Kridner wrote:
>
> Sorry about that. I broke the example. I've updated it and it should work 
> now.
>
>
> https://github.com/beagleboard/cloud9-examples/commit/210388017fcb233c2f422d54af293bb8d5c94bc2
>
> I was visiting the TI office and talking to the developers about the 
> performance of this example. According to profiles,
> it should run up to 60fps. I attempted to make some changes to speed it 
> up, but I did it wrong.
>
> You can group different layers in the network to run on different 
> processors. For this classifier network, it is said to
> be fastest to run the first 11 stages on EVEs as fixed-point processes and 
> then run the last 3 layers as floating-point
> processes on the C66 DSPs. And, because we'd only be running 3 layers on 
> the DSPs, we only need a single DSP.
>
> Anyway, I didn't assign the layers properly and I still need to look at 
> the code a bit more to set them properly.
>
> For now, I've just switched back to running on all 14 layers on 4 EVEs. 
> The 30fps data from the camera seems to 
> be reasonably processed with this configuration.
>
> I picked up a Logitech C922 that is capable of doing 60fps and I'll be 
> looking to update the demo to run that way soon
> and finishing up the segmentation demo.
>
> Checking the commit-log is a nice way to check-up on me, even if my 
> comments aren't the best.
>
> The errors are mostly due to the fact that I'm learning as well. I'm 
> trying to get the TI developers to use my methodology
> of single-file mjpg-streamer filters rather then OpenCV desktop apps as I 
> feel those the desktop apps are overly complex
> and don't represent an embedded developer's use-case. They are pretty 
> reasonably documented,
> but, as you can see, it is taking me some time to understand them. Some 
> additional debug visibility needs to be added
> to my approach and I'll be chatting to the TI developers about that some 
> in my call later today about this stuff.
>
> Development work is on-going for Tensorflow Lite support. All should be 
> much easier once that lands.
>
> And, yes, I keep talking about TI as if I don't work there, and I do work 
> there, but my working with open source
> developers all day keeps me from adopting certain development processes 
> other TI developers take as granted.
> I don't install Code Composer Studio. I don't setup an Open Embedded build 
> environment. I don't cross-compile.
> I don't setup JTAG. I hope you get the idea.
>
>
> On Wednesday, October 23, 2019 at 12:46:26 AM UTC-4, Jon Morss wrote:
>>
>>
>> Yeah, I always find it suspect when am example is posted and demo'd but 
>> does not seem to work for others.
>>
>> Headbanging continues.
>>
>> Jon
>>
>> On Tuesday, October 22, 2019 at 4:03:38 PM UTC-7, Dobrin Alexiev wrote:
>>>
>>> In my case I also see often ping-pong_ball, or more often "segmentation 
>>> fault". 
>>> I wonder how can I debug this?
>>>
>>>
>>> On Sunday, October 20, 2019 at 2:11:54 AM UTC-4, Jon Morss wrote:

 I am attempting to run the TIDL example with a Beaglebone AI and the 
 only thing it seems to report identifying is a ping-pong, although I am 
 not 
 presenting a ping pong to the camera.  I am using a Logitech C920 camera 
 and have performed all of the updates to the system, so am not sure what I 
 am missing.

 This is what I see when running the classification.tidl.cpp example:

 sudo mjpg_streamer -i "input_opencv.so -r 640x480 --filter ./
 classification.tidl.so" -o "output_http.so -p 8080 -w 
 /usr/share/mjpg-streamer/www"
 [sudo] password for debian:
 MJPG Streamer Version.: 2.0
  i: device... : default
  i: Desired Resolution: 640 x 480
  i: filter... : ./classification.tidl.so
  i: filter args . :
 Initializing filter
 loading configuration
 allocating execution object pipelines (EOP)
 allocating executors
 allocating individual EOPs
 allocating I/O memory for each EOP
 Allocating input and output buffers
 Allocating input and output buffers
 Allocating input and output buffers
 Allocating input and output buffers
 num_eops=4
 About to start ProcessFrame loop!!
 http://localhost:8080/?action=stream
  o: www-folder-path..: /usr/share/mjpg-streamer/www/
  o: HTTP TCP port: 8080
  o: HTTP Listen Address..: (null)
  o: username:password: disabled
  o: commands.: enabled
 (722)=ping-pong_ball
 (722)=ping-pong_ball
 (722)=ping-pong_ball
 (722)=ping-pong_ball
 (722)=ping-pong_ball
 (722)=ping-pong_ball


 This is what I see from dmesg:

 [20753.769040] usb 1-1: New USB device found, idVendor=046d, idProduct=
 082d
 [20753.769075] usb 1-1: New USB device strings:

Re: [beagleboard] TIDL Classification example not properly identify objects

2019-10-24 Thread jonnymo 
Dobrin,

Are you running the 4.14 or 4.19 kernel?


Cheers,

Jon

On Thursday, October 24, 2019, Dobrin Alexiev  wrote:

> Thank you, Jason.
>
> Applying the changes  made the classification demo reliably working.
>
> No crashes.
>
> Dobrin
>
>
>
> On Wednesday, October 23, 2019 at 11:20:21 AM UTC-4, Jason Kridner wrote:
>>
>> Sorry about that. I broke the example. I've updated it and it should work
>> now.
>>
>> https://github.com/beagleboard/cloud9-examples/commit/210388
>> 017fcb233c2f422d54af293bb8d5c94bc2
>>
>> I was visiting the TI office and talking to the developers about the
>> performance of this example. According to profiles,
>> it should run up to 60fps. I attempted to make some changes to speed it
>> up, but I did it wrong.
>>
>> You can group different layers in the network to run on different
>> processors. For this classifier network, it is said to
>> be fastest to run the first 11 stages on EVEs as fixed-point processes
>> and then run the last 3 layers as floating-point
>> processes on the C66 DSPs. And, because we'd only be running 3 layers on
>> the DSPs, we only need a single DSP.
>>
>> Anyway, I didn't assign the layers properly and I still need to look at
>> the code a bit more to set them properly.
>>
>> For now, I've just switched back to running on all 14 layers on 4 EVEs.
>> The 30fps data from the camera seems to
>> be reasonably processed with this configuration.
>>
>> I picked up a Logitech C922 that is capable of doing 60fps and I'll be
>> looking to update the demo to run that way soon
>> and finishing up the segmentation demo.
>>
>> Checking the commit-log is a nice way to check-up on me, even if my
>> comments aren't the best.
>>
>> The errors are mostly due to the fact that I'm learning as well. I'm
>> trying to get the TI developers to use my methodology
>> of single-file mjpg-streamer filters rather then OpenCV desktop apps as I
>> feel those the desktop apps are overly complex
>> and don't represent an embedded developer's use-case. They are pretty
>> reasonably documented,
>> but, as you can see, it is taking me some time to understand them. Some
>> additional debug visibility needs to be added
>> to my approach and I'll be chatting to the TI developers about that some
>> in my call later today about this stuff.
>>
>> Development work is on-going for Tensorflow Lite support. All should be
>> much easier once that lands.
>>
>> And, yes, I keep talking about TI as if I don't work there, and I do work
>> there, but my working with open source
>> developers all day keeps me from adopting certain development processes
>> other TI developers take as granted.
>> I don't install Code Composer Studio. I don't setup an Open Embedded
>> build environment. I don't cross-compile.
>> I don't setup JTAG. I hope you get the idea.
>>
>>
>> On Wednesday, October 23, 2019 at 12:46:26 AM UTC-4, Jon Morss wrote:
>>>
>>>
>>> Yeah, I always find it suspect when am example is posted and demo'd but
>>> does not seem to work for others.
>>>
>>> Headbanging continues.
>>>
>>> Jon
>>>
>>> On Tuesday, October 22, 2019 at 4:03:38 PM UTC-7, Dobrin Alexiev wrote:

 In my case I also see often ping-pong_ball, or more often "segmentation
 fault".
 I wonder how can I debug this?


 On Sunday, October 20, 2019 at 2:11:54 AM UTC-4, Jon Morss wrote:
>
> I am attempting to run the TIDL example with a Beaglebone AI and the
> only thing it seems to report identifying is a ping-pong, although I am 
> not
> presenting a ping pong to the camera.  I am using a Logitech C920 camera
> and have performed all of the updates to the system, so am not sure what I
> am missing.
>
> This is what I see when running the classification.tidl.cpp example:
>
> sudo mjpg_streamer -i "input_opencv.so -r 640x480 --filter ./
> classification.tidl.so" -o "output_http.so -p 8080 -w
> /usr/share/mjpg-streamer/www"
> [sudo] password for debian:
> MJPG Streamer Version.: 2.0
>  i: device... : default
>  i: Desired Resolution: 640 x 480
>  i: filter... : ./classification.tidl.so
>  i: filter args . :
> Initializing filter
> loading configuration
> allocating execution object pipelines (EOP)
> allocating executors
> allocating individual EOPs
> allocating I/O memory for each EOP
> Allocating input and output buffers
> Allocating input and output buffers
> Allocating input and output buffers
> Allocating input and output buffers
> num_eops=4
> About to start ProcessFrame loop!!
> http://localhost:8080/?action=stream
>  o: www-folder-path..: /usr/share/mjpg-streamer/www/
>  o: HTTP TCP port: 8080
>  o: HTTP Listen Address..: (null)
>  o: username:password: disabled
>  o: commands.: enabled
> (722)=ping-pong_ball
> (722)=ping-pong_ball
> (722)=ping-pong_ball
> (722)=ping-pong_ball
> (722)=ping-pong_b

Re: [beagleboard] BBAI: Assistance requested with configuring P9_15 as an output gpio

2019-10-24 Thread jonnymo 
Huzzah!   Using 76 did the trick.  There is now light on P9.15
I guess I missed that the AM57x did not have a gpio0.


Thanks a bunch.

Jon

On Thu, Oct 24, 2019 at 10:05 AM Jason Kridner 
wrote:

> On Thu, Oct 24, 2019 at 12:39 PM jonnymo  wrote:
>
>> Oh, duh!  I should  have caught that missing lib.
>> Okay, so the output of show-pins shows P.15 but it neither shows as up or
>> down.  Is this correct?
>>
>> *debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl
>>  | grep "P9.15"*
>> *P9.15 69  AG4 e fast gpio3_12*
>>
>>
>> Also, is the '69' value the gpio number that is used to enable this?
>> Such as :
>>
>> *debian@beaglebone:~$ sudo echo 69 > /sys/class/gpio/export *
>> *debian@beaglebone:~$ sudo echo out > /sys/class/gpio/gpio69/direction *
>> *debian@beaglebone:~$ sudo echo 1 > /sys/class/gpio/gpio69/value*
>>
>>
>> Since this is gpio3_12 I was thinking it was '108' considering the
>> 32x3+12 calculation as with the BB Black.
>> Neither 69 or 108 seems to work though.
>>
>
> There’s no gpio0 on AM57x, so it is 2*32 +12 = 76.
>
>
>> Also, are the failed messages from the version output something to be
>> concerned about?
>>
>> *[1.582238] remoteproc remoteproc4: Direct firmware load for
>> dra7-ipu1-fw.xem4 failed with error -2*
>> *[1.582247] remoteproc remoteproc4: powering up 5882.ipu*
>> *[1.582322] remoteproc remoteproc4: Direct firmware load for
>> dra7-ipu1-fw.xem4 failed with error -2*
>> *[1.582330] remoteproc remoteproc4: request_firmware failed: -2*
>> *[1.588375] remoteproc remoteproc5: Direct firmware load for
>> dra7-ipu2-fw.xem4 failed with error -2*
>> *[1.588383] remoteproc remoteproc5: powering up 5502.ipu*
>> *[1.588455] remoteproc remoteproc5: Direct firmware load for
>> dra7-ipu2-fw.xem4 failed with error -2*
>> *[1.588463] remoteproc remoteproc5: request_firmware failed: -2*
>> *[1.594532] remoteproc remoteproc6: Direct firmware load for
>> dra7-dsp1-fw.xe66 failed with error -2*
>> *[1.594542] remoteproc remoteproc6: powering up 4080.dsp*
>> *[1.594630] remoteproc remoteproc6: Direct firmware load for
>> dra7-dsp1-fw.xe66 failed with error -2*
>> *[1.594639] remoteproc remoteproc6: request_firmware failed: -2*
>> *[1.600688] remoteproc remoteproc7: Direct firmware load for
>> dra7-dsp2-fw.xe66 failed with error -2*
>> *[1.600697] remoteproc remoteproc7: powering up 4100.dsp*
>> *[1.600770] remoteproc remoteproc7: Direct firmware load for
>> dra7-dsp2-fw.xe66 failed with error -2*
>> *[1.600777] remoteproc remoteproc7: request_firmware failed: -2*
>> *dmesg | grep pru*
>>
>>
>>
>> Thanks,
>>
>> Jon
>>
>> On Thu, Oct 24, 2019 at 8:24 AM Robert Nelson 
>> wrote:
>>
>>> On Thu, Oct 24, 2019 at 10:12 AM Jon Morss  wrote:
>>> >
>>> > Hi,
>>> >
>>> > I've been trying to configure a header gpio pin such as P9_15 as an
>>> output port on the BBAI but I am having no luck.  This pin is used with the
>>> Cloud9 Python and JS examples but it is not working so I have tried to
>>> enable it manually.
>>> >
>>> > I've added the following in the am5729-beagleboneai.dts file and run
>>> make and make install and a reboot:
>>> >
>>> > cape_pins: cape_pins {
>>> > compatible = "gpio-leds";
>>> > pinctrl-names = "default";
>>> > gpios = <&gpio3 12 GPIO_ACTIVE_HIGH>;
>>> > pinctrl-0 = <&cape_pins_default>;
>>> > };
>>> >
>>> >
>>> >
>>> >  DRA7XX_CORE_IOPAD(0x3514, PIN_OUTPUT | MUX_MODE14) /* AG4: P9.15:
>>> vin1a_d8.gpio3_12 - MDIR2A */
>>>
>>> ^ looks correct..
>>>
>>>
>>> > The config-pins tools shows
>>> >
>>> > debian@beaglebone:~$ sudo config-pin -q p9.15
>>> > [sudo] password for debian:
>>> > P9_15 pinmux file not found!
>>> > Pin has no cape: P9_15
>>>
>>> Don't use config-pin the bbai..
>>>
>>> > The show-pins tools shows:
>>> >
>>> > debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl
>>> > Can't locate Inline/Files.pm in @INC (you may need to install the
>>> Inline::Files module) (@INC contains: /etc/perl
>>> /usr/local/lib/arm-linux-gnueabihf/perl/5.24.1 /usr/local/share/perl/5.24.1
>>> /usr/lib/arm-linux-gnueabihf/perl5/5.24 /usr/share/perl5
>>> /usr/lib/arm-linux-gnueabihf/perl/5.24 /usr/share/perl/5.24
>>> /usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at
>>> /opt/scripts/device/bone/show-pins.pl line 11.
>>> > BEGIN failed--compilation aborted at /opt/scripts/device/bone/
>>> show-pins.pl line 11.
>>>
>>> sudo apt install libinline-files-perl
>>>
>>>
>>> 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 th

Re: [beagleboard] bonescript@0.7.4-beta1 published

2019-10-24 Thread jonnymo 
Jason,

I added this to my BB AI and ran the .js script from the Cloud9 IDE and it
did in fact blink an LED connected to P9.15 as well as the usrx LEDs.

Now, I did set P9.15 as an Output pin in the am5729-beagleboneai.dts file
so I am not sure if this is necessary in this case.

Also, from the Cloud9 IDE, the nodejs script stays active and causes the BB
AI to become very in console response.
This is what is left behind.

*debian@beaglebone:~/developement$ ps -aef |grep .js*
*root   569 1  0 21:44 ?00:00:01 /usr/bin/nodejs autorun.js*
*debian   22055 1  2 22:18 ?00:00:06 /usr/bin/nodejs server.js
--packed -w /var/lib/cloud9*
*debian   22105 22055  1 22:18 ?00:00:03
/opt/cloud9/.c9/node/bin/node
/opt/cloud9/build/standalonebuild/node_modules/vfs-child/child.js
{"root":"/","metapath":"/.c9/metadata","wsmetapath":"/.c9/metadata/workspace","readOnly":false,"debug":false,"homeDir":"/home/debian","projectDir":"/var/lib/cloud9","nakBin":"/opt/cloud9/build/standalonebuild/node_modules/nak/bin/nak","nodeBin":["/opt/cloud9/.c9/node/bin/node","/usr/bin/nodejs"],"tmuxBin":"/usr/bin/tmux","defaultEnv":{"CUSTOM":43},"inProcess":false}*


Perhaps there is a way to reset the function of the usrx LEDs after the
script runs?

Cheers,

Jon


On Thu, Oct 24, 2019 at 11:01 AM Jason Kridner  wrote:

> Realized I hadn't published the work already done on putting BeagleBone AI
> GPIO pins into the node.js BoneScript library.
>
> Any testing on this version would really be appreciated.
>
>
> debian@beaglebone:/var/lib/cloud9/sensors$ *cd /usr/local/lib*
> debian@beaglebone:/usr/local/lib$ *sudo npm install --unsafe-perm
> bonescript@0.7.4-beta1*
>
> npm WARN deprecated coffee-script@1.9.1: CoffeeScript on NPM has moved to
> "coffeescript" (no hyphen)
> npm WARN deprecated json3@3.2.6: Please use the native JSON object
> instead of JSON 3
> npm WARN deprecated json3@3.3.2: Please use the native JSON object
> instead of JSON 3
> colors@1.0.3 node_modules/winston/node_modules/colors ->
> node_modules/colors
> cycle@1.0.3 node_modules/winston/node_modules/cycle -> node_modules/cycle
> eyes@0.1.8 node_modules/winston/node_modules/eyes -> node_modules/eyes
> isstream@0.1.2 node_modules/winston/node_modules/isstream ->
> node_modules/isstream
> pkginfo@0.3.1 node_modules/winston/node_modules/pkginfo ->
> node_modules/pkginfo
> stack-trace@0.0.10 node_modules/winston/node_modules/stack-trace ->
> node_modules/stack-trace
> /usr/local/lib
> └─┬ bonescript@0.7.4-beta1
>   └── winston@2.1.1
>
> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.1.2
> (node_modules/chokidar/node_modules/fsevents):
> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
> fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current:
> {"os":"linux","arch":"arm"})
> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4
> (node_modules/sensortag/node_modules/noble/node_modules/xpc-connection):
> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
> xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current:
> {"os":"linux","arch":"arm"})
> npm WARN enoent ENOENT: no such file or directory, open
> '/usr/local/lib/package.json'
> npm WARN lib No description
> npm WARN lib No repository field.
> npm WARN lib No README data
> npm WARN lib No license field.
> debian@beaglebone:/usr/local/lib$ *node -pe
> "require('bonescript').bone.getPinObject('p9.15').ai.gpio"*
> 76
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to 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/28ae9679-ddb7-42e3-9437-aa56dacb147d%40googlegroups.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/CAG99bkoLNezW3O3HrdPdKKi1OHNKBaR-91DRuHKVAWWf0%3DS5UA%40mail.gmail.com.

RE: [beagleboard] Re: where to buy beagleboards X15 ?

2019-10-24 Thread SCEL 
OK robert your information is interesting.

My Digikey support in France does not know how to give me a precise delivery 
date. and my customer is angry because I missed the last X15 Beagleboard in 
September. (the quantity in stock went from 600 to 4 suddenly). 

Now My customer need 1 SEEED as soon as possible to compare with the X15, and 
the 45 other pcs if test is OK.  I hope the test will be conclusive

That's the reason for all my questions about Beagleboards

Regards
François Cartier

-Message d'origine-
De : beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] De la 
part de Robert Nelson
Envoyé : jeudi 24 octobre 2019 15:43
À : Beagle Board
Objet : Re: [beagleboard] Re: wher to buy beagleboards X15 ?

On Thu, Oct 24, 2019 at 1:33 AM  wrote:
>
> Thank you Robert for your answer.
>
> I know SEEED. there is no product available until december-january As I know.

our timeline showed sooner then that..

>
> I wonder why this lack of parts available. is there a real production problem 
> or other problem?

Not that i'm aware of..

Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to a topic in the Google 
Groups "BeagleBoard" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/beagleboard/pDpVeupmRuk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiArFVmnSSQMbJ66RxPe36sHc1OL5X6ATpvkif88M0N0g%40mail.gmail.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/000601d58af8%24e11bddc0%24a3539940%24%40scel.fr.

[beagleboard] StarterWare-like stuff for BB AI available?

2019-10-24 Thread Mike Maikaefer 
Hi,

I'm currently using the BBB with some extensive bare-metal software which 
bases on StarterWare. Now the BB AI looks very interesting for me and I 
would like to switch over with this software to the new platform.

I'm absolutely aware of the fact that a lot of things would have to be done 
as not only the two cores have to be handled completely different.

But my questions is: is there something like StarterWare/a board support 
package available which gives the possibility to directly program the BB AI 
in a similar low-level way like the BBB?

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/87962f49-264f-410b-a50f-61f1cfb5ca1c%40googlegroups.com.

[beagleboard] Beaglebone Black init script for Initramfs

2019-10-24 Thread Maurya 
Hi,

I want to run initramfs to update emmc if image available au usb storage
device script as follow

///Installer.sh/

#!/bin/sh

emmc="/dev/mmcblk1"
bootpart="p1"
mpoint="";

usbdev="/dev/sda1"
egiimage="/mnt/egi/sdcard.img.bz2"
echo "egiimage=$egiimage"

if ! [ -b "$usbdev" ]
then
echo "USB Block Device not found!! $usbdev"
exit 3
else
mount /dev/sda1 /mnt/egi/
if ! [ -e "$egiimage" ]
then
umount /mnt/egi
echo "Egi Image not found!!"
exit 3

fi
fi

if [ -b "$emmc" ]
then
echo "SD card detected!!"
#dd if=$egiimage of=/dev/mmcblk1
mpoint="/dev/mmcblk1"
else
echo "SD card not detected!!"
#dd if=$egiimage of=/dev/mmcblk0
mpoint="/dev/mmcblk0"
fi

# led blink logic
bzcat $egiimage | dd of=$mpoint



Above script tested and working fine when running from command line

For root file system I refer
https://embedjournal.com/custom-rfs-beaglebone-black/

whereas I used my busybox  and cross compiler which is used to build kernel
uImage.

I created soft link init in / to /bin/busybox

and added above script .Installer.sh to etc/inittab as:

null::sysinit:/bin/mount -a
null::sysinit:/bin/hostname -F /etc/hostname
null::respawn:/bin/cttyhack /bin/login root
null::restart:/sbin/reboot
null::wait:/root/Installer.sh

-

When usb is not connected and power up board it will be hanged at:

Freeing init memory: 8416K

My expectation is call main rootfs from /dev/mmcblk0p2 but it hangs. Even
if I comment Installer.sh from etc/inittab it keep hanging.

I guess my procedure is wrong. please anyone suggest how to do it.

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