[beagleboard] Re: npm fmclick1 javascript node version of si4703 mikrobus fm click board

2017-12-22 Thread pete 
no i finally got it published.  it is javascript version of si4703 driver.  
when i first posted i was still having trouble publishing to npm.  thanks.

On Friday, December 22, 2017 at 4:12:42 PM UTC-5, pete wrote:
>
> npm install fmclick1.  node javascript version of si4703 driver.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you 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/9c19c0a1-bb5d-4ec1-80c7-c3abc6c22d0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] npm fmclick1 javascript node version of si4703 mikrobus fm click board

2017-12-22 Thread Stuart Longland 
On 23/12/17 07:12, pete wrote:
> npm install fmclick1.  node javascript version of si4703 driver.

Are you having problems with this Node module?  This is the second time
you've posted this and I really don't understand what you are trying to
tell us.

-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you 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/2473d4cb-e60c-87bc-7788-1fe335258c90%40longlandclan.id.au.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] npm fmclick1 javascript node version of si4703 mikrobus fm click board

2017-12-22 Thread pete 
npm install fmclick1.  node javascript version of si4703 driver.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you 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/021f5b30-c942-4c0b-adc7-71bfa3587f09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Timers, interrupts and other such delights

2017-12-22 Thread 'Mark Lazarewicz' via BeagleBoard 
I'm  working on commercial  drive much more complex than what your doing but 
jog is a use case. we use  rtos not Linux but concept is the same.
While loops in interrupts bad practice might be causing problem and won't work 
in multithreaded environment.
We have a high speed periodic servo thread calculating next  command looking at 
desired speed etc. In a real  drive this requires a PID and some control theory 
that you wont need right now for your simple use case
 you also need a state machine the  start state is  fed by button pressed  
Interrupt Then you poll the button after press is first  detected for release 
you  need to communicate the release to the servo loop
A periodic task can be driven by software timers in a barebones  system 
The details  of implementing  this in Linux I can't help with
Good luck
Sent from Yahoo Mail on Android 
 
  On Fri, Dec 22, 2017 at 9:13 AM, Hugh Frater wrote:   
I have a mechatronic device which has a couple of 'jog' buttons, these are 
working nicely on a interrupt. The interrupt code fires on level change then 
checks the value - corresponding code sections send a command to the PRU via 
/dev/rpmsg_pru31.
Part of the command sent is a numeric value representing the frequency of the 
pru_ecap PWM generation (this connects to an AC servo motor 'step' input)...
As you can now see, press the button, the motor moves, release the button & the 
frequency command sent is reduced to '0' and the PRU code stops the pwm 
generation.
What I've been playing around with today is making this a ramped (accelerated) 
jog. I can put a loop inside the interrupt code that increases the value of the 
numeric value, works fine, but I would like to delay the loop so the 
acceleration is more gradual. I've played around with a setTimeout function 
inside the loop, doesn't work.
I've moved this delayed loop to a separate function outside of the ISR. Inside 
the ISR I just loop in a do->while until the ramp generation code has 
incremented the value to a maximum, I then cancel the interval timer - this 
doesn't work either.
Is there a better way to do this that I've overlooked?



-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you 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/e2c31a95-5479-45b6-bc25-3082e485c772%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/1943150257.2788628.1513972666463%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Roboticscape support under Ubuntu 16.04 LTS on Beaglebone Black Wireless + Robotics Cape

2017-12-22 Thread Louis L. Whitcomb 

Hi Robert:

   Just checking in to see if you have had a chance to look into the 
combination of the robotics cape under Ubuntu that we discussed via 
email on 11/27/2017?  The beaglebone blue worked great under Ubuntu, but 
the roboticscape does not.  If not, perhaps you can point me in the 
right direction on how to fix this.


   Wishing you safe and happy holidays!

  Best Regards,

   -Louis

-
Louis L. Whitcomb, Ph.D.
Professor, Department of Mechanical Engineering
115 Hackerman Hall, 3400 N. Charles Street
Johns Hopkins University, Baltimore, MD, 21218-2681
l...@jhu.edu, 410-516-6724, dscl.me.jhu.edu
-

On 11/27/2017 04:14 PM, Robert Nelson wrote:

Yeah, i need to fix that combination.  My robotic's cape is at work,
and i'm at home today with the furnace guys over..

Regards,

On Mon, Nov 27, 2017 at 10:00 AM, Louis L. Whitcomb  wrote:

Dear Robert and Jason:

  I am trying to work out the details getting the EduMIP running with ROS
under Ubuntu 16.04 on the Beaglebone Blue and also the Beaglebone Black
wireleess+ Robotics Cape, and hope you may office some pointers. I have the
latest version of roboticscape installed ("sudo apt-get install
roboticscape").

ubuntu@arm:~$ sudo apt-get install roboticscape
[sudo] password for ubuntu:
Reading package lists... Done
Building dependency tree
Reading state information... Done
roboticscape is already the newest version
(0.3.4-git20170602-0rcnee4~xenial+20171108).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Here are my 2 quesions:

1. On the Beaglebone Blue under Ubuntu 16.04, when you run a rc_xxx program
it reports the error "ERROR: pru-rproc driver missing", but then runs
normally.   Example:

ubuntu@arm:~$ rc_balance
ERROR: pru-rproc driver missing
Inner Loop controller D1:

So far I have been ignoring this message.

Question: any thoughts?



2. On the Beaglebone Black wireless + robotics cape, under Ubuntu 16.04,
when you run rc_xxx program it reports numerous startup errors.  Some
programs such as rc_check_battery run normally after printing numerous
errors.  Other programs such as rc_balance print a continuous stram of
"ERROR: uart4 must be initialized first" and fail to operate properly,
perhaps due to the stream of "ERROR: uart4 must be initialized first"
messages (see below).

The warning messages for rc_balance begin with this (longer transcript at
the end of this email)

ubuntu@arm:~$ rc_balance
WARNING: RoboticsCape library should only be run on BB Blue, Black, and
Black wireless when the roboticscape device tree is in use.
If you are on a BB Black or Black Wireless, please execute
"configure_robotics_dt.sh" and reboot to enable the device tree
can't open: /sys/devices/platform/ocp/ocp:P9_28_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_23_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_11_pinmux/state
Pinmux: No such file or directory

So I ran Robotics_Cape_Installer/device_tree$ sudo
./configure_robotics_dt.sh, but configure_robotics_dt.sh appears to only
support Debian:

ubuntu@arm:~/Robotics_Cape_Installer/device_tree$ sudo
./configure_robotics_dt.sh
ERROR: This is not Debian Jessie.
Flash the latest Jessie image to your BBB
or use the Wheezy branch of this installer.
ubuntu@arm:~/Robotics_Cape_Installer/device_tree$


Question: Do you have suggestions on how to fix this?

Thanks and Best Regards,

   -Louis



ubuntu@arm:~$ rc_balance
WARNING: RoboticsCape library should only be run on BB Blue, Black, and
Black wireless when the roboticscape device tree is in use.
If you are on a BB Black or Black Wireless, please execute
"configure_robotics_dt.sh" and reboot to enable the device tree
can't open: /sys/devices/platform/ocp/ocp:P9_28_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_23_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_11_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_22_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_21_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_26_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_24_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_30_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_29_pinmux/state
Pinmux: No such file or directory
can't open: /sys/devices/platform/ocp/ocp:P9_31_pinmux/state
Pinmux: No such file or directory
WARNING: missing PINMUX driver
You probbaly just need a newer kernel
ERROR: ti-eqep driver not loaded for eqep0
WARNING: failed to initialize eQEP0
ERROR: ti-eqep driver not loaded for

[beagleboard] hardware trouble, BBB can't boot successfully

2017-12-22 Thread vinker vinker 
Hi，
I got a BBB a few days ago. It has a XAM3359 MPU.  It can't boot 
from emmc, so I tried to boot it from SD card. However， everytime it 
stopped at the same place with the same log.
The image version 
is Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.
 The follow is the booting message:

Uncompressing Linux... done, booting the kernel.
[0.230005] omap2_mbox_probe: platform not supported
[0.243435] tps65217-bl tps65217-bl: no platform data provided
[0.328978] bone-capemgr bone_capemgr.8: slot #0: No cape found
[0.368036] bone-capemgr bone_capemgr.8: slot #1: No cape found
[0.407097] bone-capemgr bone_capemgr.8: slot #2: No cape found
[0.446160] bone-capemgr bone_capemgr.8: slot #3: No cape found
[0.471219] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN 
conflict P8.45 (#5:BB-BONELT-HDMI)
[0.483286] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[0.491777] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 
BB-BONELT-HDMIN:00A0 (prio 2)
[0.520132] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' 
failed
[0.587312] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[0.601997] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status 
-22
[0.611188] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
device pinctrl-single
[   11.042147] Unable to handle kernel paging request at virtual address 
004de000
[   11.051620] pgd = df58
[   11.055151] [004de000] *pgd=
[   11.059825] Internal error: Oops: 5 [#1] SMP THUMB2
[   11.066157] Modules linked in: autofs4
[   11.071036] CPU: 0Not tainted  (3.8.13 #1)
[   11.076824] PC is at lg_local_lock_cpu+0xa/0x38
[   11.082709] LR is at file_sb_list_del+0x13/0x30
[   11.088591] pc : []lr : []psr: 0033
[   11.088591] sp : df051f78  ip : 50c5387d  fp : 000db9c0
[   11.103500] r10:   r9 : df05  r8 : c000c7e4
[   11.110283] r7 : 0006  r6 : df04cac0  r5 : df05  r4 : df5ca6c0
[   11.118757] r3 : 004de000  r2 : 004de000  r1 :   r0 : c065a4e4
[   11.127233] Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  
Segment user
[   11.136722] Control: 50c5387d  Table: 9f580019  DAC: 0015
[   11.144182] Process systemd (pid: 1, stack limit = 0xdf050240)
[   11.151754] Stack: (0xdf051f78 to 0xdf052000)
[   11.157545] 1f60:   
df5ca6c0 c0095313
[   11.168205] 1f80: df5ca6c0  df04fe80 c0092ebb   
000f88a8 c0092e5b
[   11.178854] 1fa0: b6dd3450 c000c641   000b  
003c b6dd3450
[   11.189500] 1fc0:   000f88a8 0006 000cd980 000f85d0 
000f6550 000db9c0
[   11.200145] 1fe0:  bea357b4 b6dd46ac b6dd3460 600f0010 000b 
de7d76df 1b9f2915
[   11.210807] [] (lg_local_lock_cpu+0xa/0x38) from [] 
(file_sb_list_del+0x13/0x30)
[   11.222698] [] (file_sb_list_del+0x13/0x30) from [] 
(fput+0x37/0x94)
[   11.233243] [] (fput+0x37/0x94) from [] 
(filp_close+0x3b/0x44)
[   11.243102] [] (filp_close+0x3b/0x44) from [] 
(sys_close+0x19/0x3e)
[   11.253534] [] (sys_close+0x19/0x3e) from [] 
(ret_fast_syscall+0x1/0x46)
[   11.264539] Code: 6803 f852 2021 189b (e853) 1f00
[   11.270795] ---[ end trace 079fae02e79b2d40 ]---
[   11.277758] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[   11.277758]
[   11.289629] drm_kms_helper: panic occurred, switching back to text 
console

I googled to find this may mean some hardware , but I'm not familiar with 
TI processor. So I don't know which part of the board  doesn't work.
I tried to boot another BBB board(a reduced version with AM3352 instead, 
and without emmc and HDMI) , using the identical SD card with the same 
image. And it boot successfully. 

Can anyone give me some advice on which part to check?  Many 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/832b17ee-b12f-4a40-9c03-76ce1f49575a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] hardware trouble! can't boot my BBB

2017-12-22 Thread vinkerv 
Hi,
I got a BBB board a few days ago. It is a board with XAM3359 MPU. 
It can not boot from emmc. So I tried to boot from SD card. However, 
everytime it stopped at the same place, with log:

U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)
I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, 
SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, 
SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
33 bytes read in 3 ms (10.7 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
gpio: pin 55 (gpio 55) value is 1
4270840 bytes read in 763 ms (5.3 MiB/s)
gpio: pin 56 (gpio 56) value is 1
24129 bytes read in 44 ms (535.2 KiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Angstrom/3.8.13/beaglebone
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:4270776 Bytes = 4.1 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 80f88e40
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[0.230596] omap2_mbox_probe: platform not supported
[0.244033] tps65217-bl tps65217-bl: no platform data provided
[0.329571] bone-capemgr bone_capemgr.8: slot #0: No cape found
[0.368629] bone-capemgr bone_capemgr.8: slot #1: No cape found
[0.407691] bone-capemgr bone_capemgr.8: slot #2: No cape found
[0.446752] bone-capemgr bone_capemgr.8: slot #3: No cape found
[0.471825] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN 
conflict P8.45 (#5:BB-BONELT-HDMI)
[0.483856] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[0.492317] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 
BB-BONELT-HDMIN:00A0 (prio 2)
[0.520644] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' 
failed
[0.587895] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[0.602512] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status 
-22
[0.611660] pinctrl-single 44e10800.pinmux: could not request pin 21 on 
device pinctrl-single
systemd-fsck[86]: Angstrom: clean, 50545/218160 files, 304986/872448 blocks
[   11.711891] Unable to handle kernel paging request at virtual address 
004de000
[   11.721435] pgd = df694000
[   11.724996] [004de000] *pgd=
[   11.729666] Internal error: Oops: 5 [#1] SMP THUMB2
[   11.735995] Modules linked in: rfcomm ircomm_tty ircomm irda ipv6 hidp 
bluetooth rfkill autofs4
[   11.747351] CPU: 0Not tainted  (3.8.13 #1)
[   11.753140] PC is at lg_local_lock_cpu+0xa/0x38
[   11.759025] LR is at file_sb_list_del+0x13/0x30
[   11.764907] pc : []lr : []psr: 0033
[   11.764907] sp : df689f78  ip : 50c5387d  fp : 
[   11.779814] r10:   r9 : df688000  r8 : c000c7e4
[   11.786596] r7 : 0006  r6 : df668ac0  r5 : df688000  r4 : df590600
[   11.795070] r3 : 004de000  r2 : 004de000  r1 :   r0 : c065a4e4
[   11.803546] Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  
Segment user
[   11.813035] Control: 50c5387d  Table: 9f694019  DAC: 0015
[   11.820494] Process systemd-journal (pid: 94, stack limit = 0xdf688240)
[   11.829081] Stack: (0xdf689f78 to 0xdf68a000)
[   11.912084] 9f60:   
df590600 c0095313
[   11.947711] 9f80: df590600  df04f880 c0092ebb   
000408b8 c0092e5b
[   11.978467] 9fa0: b6d65450 c000c641   000b fbad2408 
 b6d65450
[   12.016333] 9fc0:   000408b8 0006 000294dc becbd898 
00038018 
[   12.075746] 9fe0:  becbd02c b6d666ac b6d65460 600f0010 000b 
 
[   12.086479] [] (lg_local_lock_cpu+0xa/0x38) from [] 
(file_sb_list_del+0x13/0x30)
[   12.098422] [] (file_sb_list_del+0x13/0x30) from [] 
(fput+0x37/0x94)
[   12.108973] [] (fput+0x37/0x94) from [] 
(filp_close+0x3b/0x44)
[   12.118833] [] (filp_close+0x3b/0x44) from [] 
(sys_close+0x19/0x3e)
[   12.129284] [] (sys_close+0x19/0x3e) from []

[beagleboard] Network connection problem

2017-12-22 Thread Pankhuri Vanjani 
This status doesn't turn to active sometimes after connecting.
If i restart it later or do it again n again..then it gets fine ...
but is there any good solution to 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/3053409c-2cb1-455e-b782-bc5b9584d031%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Hardware-accelerated GUI

2017-12-22 Thread dvd1202 
I have to develop a GUI application for Beaglebone Black. As I'm using Gtk, 
it's unacceptably slow. Problem is that the SGX drivers don't work with X, 
so I have to access the frame buffer directly somehow.

Using Gtk is ideal but not necessary - my goal is to develop a GUI that 
makes use of hardware rendering, so whichever means to achieve that is 
welcome (within reasonable limits - getting too low-level wouldn't be 
practicable).

What I've managed to accomplish so far:

1) Install Debian 9.1 on the SD card 
(http://debian.beagleboard.org/images/bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img.xz)
2) Install the SGX drivers:
2.1) Install a 4.4 LTS kernel as described here 
:

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --bone-kernel --lts-4_4
sudo reboot

2.2) On a x86 linux environment (VM, whatever):

git clone https://github.com/RobertCNelson/bb-kernel.git
cd bb-kernel/
git checkout origin/am33x-v4.4 -b tmp-sgx
./sgx_create_package.sh

2.3) Copy ./deploy/GFX_5.01.01.02_es8.x.tar.gz to BBB. Once there…

sudo tar xfv GFX_5.01.01.02_es8.x.tar.gz -C /
cd /opt/gfxinstall/
sudo ./sgx-install.sh
sudo reboot
sudo apt-get install ti-sgx-es8-modules-`uname -r`

sudo depmod -a `uname -r`
sudo update-initramfs -uk `uname -r`

2.4) Load drivers manually

cd /etc/init.d
sudo ./sgx-startup.sh start

2.5) Verify that drivers are loaded correctly:

lsmod | grep omaplfb

I see that there's a number of libraries (Clutter, raylib, simple2d), some 
specifically targeting the Raspberry (should be pretty similar?), that 
support OpenGL ES, but they all fail to build for one reason or another. I 
suppose they all build some tailored version of SDL, so I tried building 
SDL from scratch without X11 support as detailed here 
,
 
but then the examples compiled with this version complain that there is no 
available video device.

Any 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/06d2b1c1-e610-451e-b14d-07318c3bddf9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] node-red errors: waiting for missing types to be registered: - bbb-discrete-out -- How do i fix this

2017-12-22 Thread kris . r . jensen 
Here is the output from starting node-red at the command line


Welcome to Node-RED
===

22 Dec 04:55:06 - [info] Node-RED version: v0.17.5
22 Dec 04:55:06 - [info] Node.js  version: v6.12.2
22 Dec 04:55:06 - [info] Linux 4.4.91-ti-r133 arm LE
22 Dec 04:55:11 - [info] Loading palette nodes
22 Dec 04:55:22 - [info] Dashboard version 2.7.0 started at /ui
22 Dec 04:55:25 - [warn] 
--
22 Dec 04:55:25 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific 
node
22 Dec 04:55:25 - [warn] [bbb] Error: ENOENT: no such file or directory, 
open '/sys/devices/platform/bone_capemgr/slots' (line:13)
22 Dec 04:55:25 - [warn] 
--
22 Dec 04:55:25 - [info] Settings file  : /root/.node-red/settings.js
22 Dec 04:55:25 - [info] User directory : /root/.node-red
22 Dec 04:55:25 - [info] Flows file : 
/root/.node-red/flows_beaglebone.json
22 Dec 04:55:25 - [info] Server now running at http://127.0.0.1:1880/
22 Dec 04:55:26 - [info] Waiting for missing types to be registered:
22 Dec 04:55:26 - [info]  - bbb-discrete-out



---

I had node-red working well today then it stopped working. I restarted the 
system and for the last to this error. For the past four hours I have been 
troubleshooting the issue. 

While working the issue, I have disabled all the other nodes types. This 
node type will no longer show up in flows or even operate.

Looking for ways to fix this other than starting with a new image.

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

[beagleboard] Timers, interrupts and other such delights

2017-12-22 Thread Hugh Frater 
I have a mechatronic device which has a couple of 'jog' buttons, these are 
working nicely on a interrupt. The interrupt code fires on level change 
then checks the value - corresponding code sections send a command to the 
PRU via /dev/rpmsg_pru31.

Part of the command sent is a numeric value representing the frequency of 
the pru_ecap PWM generation (this connects to an AC servo motor 'step' 
input)...

As you can now see, press the button, the motor moves, release the button & 
the frequency command sent is reduced to '0' and the PRU code stops the pwm 
generation.

What I've been playing around with today is making this a ramped 
(accelerated) jog. I can put a loop inside the interrupt code that 
increases the value of the numeric value, works fine, but I would like to 
delay the loop so the acceleration is more gradual. I've played around with 
a setTimeout function inside the loop, doesn't work.

I've moved this delayed loop to a separate function outside of the ISR. 
Inside the ISR I just loop in a do->while until the ramp generation code 
has incremented the value to a maximum, I then cancel the interval timer - 
this doesn't work either.

Is there a better way to do this that I've overlooked?


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you 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/e2c31a95-5479-45b6-bc25-3082e485c772%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] npm fmclick1

2017-12-22 Thread pete 
fmclick1 at npm is javascript version of si4703 radio driver.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you 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/44b5c71f-46e7-4bb2-a74a-69eea908480f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Bootstrapping the PocketBeagle with a 2GB SD card

2017-12-22 Thread Stuart Longland 
Hi all,

Just having a crack at getting the PocketBeagle going.  If I plug it in
to USB with no SD card attached, I see the blue power LED come on, and
the following kernel messages:

> Dec 22 19:59:53 localhost kernel: [1568370.371239] usb 2-1.6: new full-speed 
> USB device number 4 using ehci-pci
> Dec 22 19:59:53 localhost kernel: [1568370.449682] usb 2-1.6: not running at 
> top speed; connect to a high speed hub
> Dec 22 19:59:53 localhost kernel: [1568370.450552] usb 2-1.6: New USB device 
> found, idVendor=0451, idProduct=6141
> Dec 22 19:59:53 localhost kernel: [1568370.450554] usb 2-1.6: New USB device 
> strings: Mfr=33, Product=37, SerialNumber=0
> Dec 22 19:59:53 localhost kernel: [1568370.450555] usb 2-1.6: Product: AM335x 
> USB
> Dec 22 19:59:53 localhost kernel: [1568370.450556] usb 2-1.6: Manufacturer: 
> Texas Instruments
> Dec 22 19:59:53 localhost kernel: [1568370.895843] EXT4-fs (sda7): 
> re-mounted. Opts: data=ordered,commit=600
> Dec 22 19:59:55 localhost kernel: [1568372.754859] usbcore: registered new 
> interface driver cdc_ether
> Dec 22 19:59:55 localhost kernel: [1568372.797082] rndis_host 2-1.6:1.0 usb0: 
> register 'rndis_host' at usb-:00:1d.0-1.6, RNDIS d
> evice, aa:b6:7d:f9:4a:34
> Dec 22 19:59:55 localhost kernel: [1568372.797118] usbcore: registered new 
> interface driver rndis_host
> Dec 22 19:59:55 localhost kernel: [1568372.799387] usbcore: registered new 
> interface driver rndis_wlan
> Dec 22 19:59:55 localhost kernel: [1568373.040159] EXT4-fs (sda7): 
> re-mounted. Opts: data=ordered,commit=600
> Dec 22 19:59:57 localhost kernel: [1568375.196263] EXT4-fs (sda7): 
> re-mounted. Opts: data=ordered,commit=600
> Dec 22 19:59:59 localhost kernel: [1568377.148978] rndis_host 2-1.6:1.0 
> enp0s29u1u6: renamed from usb0
> Dec 22 19:59:59 localhost kernel: [1568377.164979] IPv6: ADDRCONF(NETDEV_UP): 
> enp0s29u1u6: link is not ready
> Dec 22 20:00:00 localhost kernel: [1568377.285143] usb 2-1.6: reset 
> full-speed USB device number 4 using ehci-pci
> Dec 22 20:00:00 localhost kernel: [1568377.349148] usb 2-1.6: device 
> descriptor read/64, error 16
> Dec 22 20:00:00 localhost kernel: [1568377.519163] usb 2-1.6: device 
> descriptor read/64, error 16
> Dec 22 20:00:00 localhost kernel: [1568377.687143] usb 2-1.6: reset 
> full-speed USB device number 4 using ehci-pci
> Dec 22 20:00:00 localhost kernel: [1568377.751149] usb 2-1.6: device 
> descriptor read/64, error 16
> Dec 22 20:00:00 localhost kernel: [1568377.919173] usb 2-1.6: device 
> descriptor read/64, error 16
> Dec 22 20:00:00 localhost kernel: [1568378.087166] usb 2-1.6: reset 
> full-speed USB device number 4 using ehci-pci
> Dec 22 20:00:00 localhost kernel: [1568378.101994] usb 2-1.6: device 
> descriptor read/8, error -32
> Dec 22 20:00:00 localhost kernel: [1568378.219996] usb 2-1.6: device 
> descriptor read/8, error -32
> Dec 22 20:00:01 localhost kernel: [1568378.391142] usb 2-1.6: reset 
> full-speed USB device number 4 using ehci-pci
> Dec 22 20:00:01 localhost kernel: [1568378.405991] usb 2-1.6: device 
> descriptor read/8, error -32
> Dec 22 20:00:01 localhost kernel: [1568378.523994] usb 2-1.6: device 
> descriptor read/8, error -32
> Dec 22 20:00:01 localhost kernel: [1568378.631770] usb 2-1.6: USB disconnect, 
> device number 4
> Dec 22 20:00:01 localhost kernel: [1568378.631805] rndis_host 2-1.6:1.0 
> enp0s29u1u6: unregister 'rndis_host' usb-:00:1d.0-1.6, RNDIS device
> Dec 22 20:00:01 localhost kernel: [1568378.701123] usb 2-1.6: new full-speed 
> USB device number 5 using ehci-pci
> Dec 22 20:00:01 localhost kernel: [1568378.765118] usb 2-1.6: device 
> descriptor read/64, error 16
> Dec 22 20:00:01 localhost kernel: [1568378.935119] usb 2-1.6: device 
> descriptor read/64, error 16
> Dec 22 20:00:01 localhost kernel: [1568379.105124] usb 2-1.6: new full-speed 
> USB device number 6 using ehci-pci
> Dec 22 20:00:01 localhost kernel: [1568379.169115] usb 2-1.6: device 
> descriptor read/64, error 16
> Dec 22 20:00:02 localhost kernel: [1568379.335119] usb 2-1.6: device 
> descriptor read/64, error 16
> Dec 22 20:00:02 localhost kernel: [1568379.503115] usb 2-1.6: new full-speed 
> USB device number 7 using ehci-pci
> Dec 22 20:00:02 localhost kernel: [1568379.517977] usb 2-1.6: device 
> descriptor read/8, error -32
> Dec 22 20:00:02 localhost kernel: [1568379.635996] usb 2-1.6: device 
> descriptor read/8, error -32
> Dec 22 20:00:02 localhost kernel: [1568379.807109] usb 2-1.6: new full-speed 
> USB device number 8 using ehci-pci
> Dec 22 20:00:02 localhost kernel: [1568379.822008] usb 2-1.6: device 
> descriptor read/8, error -32
> Dec 22 20:00:02 localhost kernel: [1568379.939976] usb 2-1.6: device 
> descriptor read/8, error -32
> Dec 22 20:00:02 localhost kernel: [1568380.048232] usb 2-1-port6: unable to 
> enumerate USB device

That to me, suggests *something* is alive.  I grabbed a 16GB microSD
card, only to find it was a dud.  The ones I have spare are 2GB ones.

Okay,

[beagleboard] Debian Stretch Flavors

2017-12-22 Thread Paul Van den Bergh 
Hi All,

On https://elinux.org/BeagleBoard:BeagleBoneBlack_Debian there are four 
kind of 'flavors' of Debian Stretch:

   - Machinekit
   - lxqt
   - iot
   - console

I would like to know which features are supported by the different 
flavors.  Couldn't find info via Google, allas...


Is there some kind of comparisson table for this?  Where can I find more 
info?


In particular, for the current project I'm looking for the minimal system 
without gui (so afaik this eliminates lxqt), but with support for apache, 
MySql, PRU rpmsg.  The main application software (C++) is cross-compiled on 
desktop PC.  For debugging gdb runs on the BBB.  The connection to the BBB 
is over ssh.


Thanks for any input!


Paul

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you 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/d4c86d9b-f3ec-4d00-8beb-5a7dbbd9058f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Controlling which partition gets booted to in an A/B partitioning scheme using a boot partition

2017-12-22 Thread 'Luther Goh Lu Feng' via BeagleBoard 
I have a multi paritioned microSD card as follows. P1 is the boot partition, P2 
and P3 are rootfs partitions. Based on my investigations, I have ensured both 
P2 and P3 are bootable rootfs. By default, the BBB will boot to P2. By adding 
mmcpart=3 in /boot/uEnv.txt, I can let the BBB boot to P3. The partition booted 
to was verified using output from df and seeing which device / was mounted on
I would like to control which partition gets booted to using P1 instead of P2. 
I remove mmcpart=3 in /boot/uEnv.txt in P2. Then in 1 attempt I added a 
/uEnv.txt with mmcpart=3 in P1, and in another, I added a /boot/uEnv.txt with 
mmcpart=3 in P1. Both attempts did not work.
I have referenced the uboot patch[1] by Robert, but perhaps I have missed 
something

# fdisk -l /dev/mmcblk0Disk /dev/mmcblk0: 14.5 GiB, 15523119104 bytes, 30318592 
sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 
bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel 
type: dosDisk identifier: 0x9582e2f8
Device         Boot   Start      End Sectors  Size Id Type/dev/mmcblk0p1        
 8192   212991  204800  100M 83 Linux/dev/mmcblk0p2       212992  4308991 
4096000    2G 83 Linux/dev/mmcblk0p3      4308992  8404991 4096000    2G 83 
Linux/dev/mmcblk0p4      8404992 12503039 4098048    2G  5 
Extended/dev/mmcblk0p5      8407040 12503039 4096000    2G 83 Linux
[1] 
https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2017.11/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you 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/1494718876.3098305.1513932864753%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.