[beagleboard] Is cape manager obsolete? What about device tree overlays?

[Ken Shirriff]

I'm trying to understand the current state of device tree overlays. Is it 
correct that the cape manager is now obsolete, and device tree overlays 
should be set up through /boot/uEnv.txt? What about config-pin? Is that an 
alternative to device tree overlays, or something orthogonal?

The system I'm using is a PocketBeagle with 4.4.91-ti-r133. Before that I 
was using the 3.8 kernel on a BeagleBone and everything seems to have 
changed. (Is there a summary somewhere of the new world?)

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/c4fcb8bf-962f-414b-8f59-b459f045575f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Measure frequency of a square wave input without PRU?

[Drew Fustini]

Any suggestion on how to measure the frequency of a square wave input?

 Signal would be 3kHz or less.  The goal is to use the appropriate AM3358 
peripherals from the ARM core, not the PRU.

The eCAP peripheral comes to mind but I'm not sure it that would be 
appropriate for this use case.

For reference, the question comes from this github issue:
https://github.com/adafruit/adafruit-beaglebone-io-python/issues/204#issuecomment-347415768

-- 
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/5045e3af-ac56-4d54-9cd2-2188059b55d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: spi with beaglebone balck ubuntu 14.04 Linux arm 4.1.13-ti-r36 not run

[Robert Nelson]

On Mon, Nov 27, 2017 at 8:15 AM,   wrote:
> Hi ,
> I am also facing the same issue on Linux arm 4.4.30-ti-r66 .

Did you config-pin the spi pin's or load the spi overlay?

sudo /opt/scripts/tools/version.sh

Regards,

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

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

RE: [beagleboard] FB7 to R 150 Ohm ?

[Gerald Coley]

Sure, but I don't think making the resistence smaller will stop whatever you 
are plugging in from pulling too much current. Current limit is controlled by 
the switch itself.

How much current does the device you are plugging in require?

Gerald

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Riko
Sent: Monday, November 27, 2017 6:36 PM
To: Beagle Board 
Cc: Robert Nelson 
Subject: [beagleboard] FB7 to R 150 Ohm ?

Dear Beagleboard Members,
Can I replace FB7 to R 150 Ohm, I got 30 Ohm on that Ferrit Bead and making me 
over current all the time ?
Thanks
--

/*
Sent By
Ubuntu Linux 16.04 LTS
Kernel 4.4.0-92-generic
Kind Regards,
Riko Ho
==
谢谢从何金汉
*/

--
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/ee80455a-f749-fbda-3c0e-49905299d92d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[beagleboard] Can't connect to certain PC's through Wifi

[Josh Lotts]

I am a member of a local makerspace.  We use beaglebone to run our 
Lasersaur laser cutter.   That being said, we have had a couple years of 
issues with various connections that doesn't make any sense.For 
example, sometimes when a new person comes in and logs on to our network, 
the lasersaur page will not load, and pinging the IP says it cannot reach 
host.  That being said at the exact same time I can get it to pull up on 
another PC without a problem.  Then it will sometimes not connect to the PC 
is was working with  This doesn't make any sense to me, because no one 
changed anything and it was working before...  What gives!?  

-- 
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/1bb55b9f-a7b9-45e1-aeac-339109518d36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: spi with beaglebone balck ubuntu 14.04 Linux arm 4.1.13-ti-r36 not run

[nimishjain1000]

Hi ,
I am also facing the same issue on Linux arm 4.4.30-ti-r66 .


On Wednesday, August 3, 2016 at 4:58:50 PM UTC+5:30, caongu...@gmail.com 
wrote:
>
> Hi ALL 
> I work with beaglebone balck ubuntu 14.04 Linux arm 4.1.13-ti-r36 
> I want interface spi but  after execution:
> open file uEnv.txt
> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
>
> uname_r=4.1.13-ti-r36
> #uuid=
> #dtb=
>
> ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)
>
> ##BeagleBone Black: HDMI (Audio/Video) disabled:
> dtb=am335x-boneblack-emmc-overlay.dtb
>
> ##BeagleBone Black: eMMC disabled:
> #dtb=am335x-boneblack-hdmi-overlay.dtb
>
> ##BeagleBone Black: HDMI Audio/eMMC disabled:
> #dtb=am335x-boneblack-nhdmi-overlay.dtb
>
> ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:
> dtb=am335x-boneblack-overlay.dtb
>
> ##BeagleBone Black: wl1835
> #dtb=am335x-boneblack-wl1835mod.dtb
>
> ##BeagleBone Black: replicape
> #dtb=am335x-boneblack-replicape.dtb
>
> ##BeagleBone Green: eMMC disabled
> #dtb=am335x-bonegreen-overlay.dtb
>
> cmdline=coherent_pool=1M quiet cape_universal=enable
>
> #In the event of edid real failures, uncomment this next line:
> #cmdline=coherent_pool=1M quiet cape_universal=enable 
> video=HDMI-A-1:1024x768@60e
>
> ##Example v3.8.x
> #cape_disable=capemgr.disable_partno=
> #cape_enable=capemgr.enable_partno=
>
> ##Example v4.1.x
> #cape_disable=bone_capemgr.disable_partno=
> #cape_enable=bone_capemgr.enable_partno=
>
> cape_disable=bone_capemgr.disable_partno=BB-SPIDEV0,BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G
> cape_enable=bone_capemgr.enable_partno=BB-I2C1,BB-SPIDEV1
> ##enable Generic eMMC Flasher:
> ##make sure, these tools are installed: dosfstools rsync
> #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
> savle file and rebbot
> That : 
>
> *cat /sys/devices/platform/bone_capemgr/slots* 
>
> 0: PF -1
>
> 1: PF -1
>
> 2: PF -1
>
> 3: PF -1
>
>
> *cat /sys/devices/platform/bone_capemgr/slots*
>
> 0: PF -1
>
> 1: PF -1
>
> 2: PF -1
>
> 3: PF -1
>
> 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,BB-SPIDEV1
>
>
> after I run my code
>
> BlackLib::BlackSPI mySpi4(BlackLib::SPI1_0, 8, BlackLib::SpiDefault, 
> 240);
> bool isOpened4 = mySpi4.open( BlackLib::ReadWrite | 
> BlackLib::NonBlock);
> if( !isOpened4 )
> {
> std::cout << "SPI DEVICE CAN\'T OPEN " << std::endl;
> cout<<"  value 4: " < cout<<" \r\n "< }
> else
> {
> cout<<" OPEN spi 4: " < cout<<" value open spi:" < cout<<" \r\n "< }
>
>
> notification 
> SPI DEVICE CAN\'T OPEN
>
> please help
>
> thanks all
>

-- 
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/7fdfc6c1-4016-4a7b-8fbc-72b76950ab7d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] FB7 to R 150 Ohm ?

[Riko]

Dear Beagleboard Members,
Can I replace FB7 to R 150 Ohm, I got 30 Ohm on that Ferrit Bead and 
making me over current all the time ?

Thanks
--

*/*
Sent By
Ubuntu Linux 16.04 LTS
Kernel 4.4.0-92-generic
Kind Regards,
Riko Ho
==
谢谢从何金汉
*/*


--
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/ee80455a-f749-fbda-3c0e-49905299d92d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB pps0 assigned to serial4

[Joe Smith]

I have a BeagleBone Black configured with U-Boot overlays for PPS input on 
header pin 9.12 and UART4 on 9.11 and 9.13. This is being fed from an 
AdaFruit Ultimate GPS breakout board.

Excerpt from /boot/uEnv.txt

uboot_overlay_addr0=/lib/firmware/NF3H-PPS-00A0.dtbo
uboot_overlay_addr1=/lib/firmware/BB-UART4-00A0.dtbo

No other mods were made to uEnv.txt. Initially when I set it up, all 
appeared good, with the PPS input getting assigned to /dev/pps0  Then all 
of a sudden on my last reboot the PPS input started getting assigned to 
/dev/pps1 and serial4 getting assigned to /dev/pps0  I noticed something 
like this before I installed the latest BBB debian image but dismissed it. 
Now that I see it again I have questions as to what is causing it. I need 
to be able to reliably predict what PPS device is getting assigned, as this 
BBB is being set up as a GPS NTP server using GPSD and Chrony. See dmesg 
output below.

[   17.330602] pps_ldisc: PPS line discipline registered
[   17.332357] pps pps0: new PPS source serial4
[   17.332431] pps pps0: source "/dev/ttyS4" added

Then later in dmesg output...

[   26.246745] pps pps1: new PPS source ocp:bs_pinmode_P9_12_0x27_pinm
[   26.246871] pps pps1: Registered IRQ 88 as PPS source

Does anybody have any ideas as to what is causing this? The uEnv.txt mods 
above are the only system changes made other than doing apt-gets to install 
the necessary debian packages for ppstools, gpsd, man-db, and chrony. I 
also had to build and "make install" chrony from source in order to get PPS 
support built in. If the answer is that it'll always be /dev/pps1 I'm OK 
with that. It's just that it has flopped around on me a couple of times now 
for reasons I don't understand. Now when I power-cycle or reboot the BBB, 
the chrony service will not start because it fails to open /dev/pps1 yet 
when I do a ppstest /dev/pps1 I see the PPS input coming in. Almost as if 
during startup the chrony service is trying to access /dev/pps1 before it 
is ready. If I then start chrony manually with systemctl start chrony, it 
starts up successfully.

debian@beaglebone:~$ uname -a
Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
GNU/Linux

-- 
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/c33a66f2-6138-47e4-9f54-f6188a268ee8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Low level initialisation steps?

[mike . maikaefer]

Hi,

I'm currently try to run a bare metal application which works fine on the 
BBB on my new PocketBeagle. MLO bootloader works as expected, it loads the 
main application image to addres 0x8000. But when it jumps to this 
address to execute the main application, the whole board stalls.

This lets me think some of the basic hardware initialisations done by the 
bootloader do fit for BBB, but not for PocketBeagle.

So my question: are there some fundamental differences between both? Does 
the Octavo-internal RAM need a different timing than the one on BBB? If 
yes: what exactly is different? Or what else needs to be low-level 
initialised in a different way?

Thanks!

Mike


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

Re: [beagleboard] Re: Boot bare metal application - MLO no longer used?

[mike . maikaefer]

OK, I got it: it seems, the Octavo-SoC does NOT support MLO as file on the 
FatSF partition. Writing it into the forst section of the SD card solved 
the problem, now the MLO is found and loaded.

-- 
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/e10ea90b-7916-472d-857b-2116c582f1ef%40googlegroups.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

[Robert Nelson]

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 eqep1
> WARNING: failed to initialize eQEP1
> ERROR: ti-eqep driver not loaded for eqep2
> WARNING: failed to initialize eQEP2
> ERROR: ti-pwm driver not loaded for pwm subsystem 1
> ERROR: failed to initialize hrpwm1
> WARNING: Failed to initialize motors
> ERROR: pru-rproc driver missing
> Inner Loop controller D1:
> order: 2
> timestep dt: 0.0100
> -4.9450z² +  8.8620z  + -3.9670
> 
>  1.z² + -1.4810z  +  0.4812
>
> Outer Loop controller D2:
> order: 2
> timestep dt: 0.0100
>  0.1886z² + -0.3721z  +  0.1835
> 
>  

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

[Louis L. Whitcomb]

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 eqep1
WARNING: failed to initialize eQEP1
ERROR: ti-eqep driver not loaded for eqep2
WARNING: failed to initialize eQEP2
ERROR: ti-pwm driver not loaded for pwm subsystem 1
ERROR: failed to initialize hrpwm1
WARNING: Failed to initialize motors
ERROR: pru-rproc driver missing
Inner Loop controller D1:
order: 2
timestep dt: 0.0100
-4.9450z² +  8.8620z  + -3.9670

 1.z² + -1.4810z  +  0.4812

Outer Loop controller D2:
order: 2
timestep dt: 0.0100
 0.1886z² + -0.3721z  +  0.1835

 1.z² + -1.8605z  +  0.8605

Hold your MIP upright to begin balancing

dsm Calibration File Doesn't Exist Yet
Run calibrate_dsm example to create one
Using default values for now
can't open: /sys/devices/platform/ocp/ocp:P9_11_pinmux/state
Pinmux: No such file or directory
error opening uart4 in /dev/
device tree probably isn't loaded
Error, failed to initialize UART4 for dsm
ERROR: trying to disable 

Re: [beagleboard] Re: Boot bare metal application - MLO no longer used?

[acheesehead]

Try reformatting SD card or use a new one. Copy MLO to the card *first*. 
Use a known good MLO. It is signed by a special TI utility.

On Sunday, November 26, 2017 at 11:44:50 AM UTC-7, mike.ma...@gmail.com 
wrote:
>
>
>> TI has not changes anything in StarterWare since BBB, so I don't expect a 
>> new MLO from this side - but it is not a problem since sources are included 
>> in StarterWare package and therefor can be build easily.
>
>  
> But this does not seem to be the problem, this ""-sequence means, 
> the SoC does not find the MLO anywhere! So although it is available on the 
> FatFS partition of the microSD card, it isn't loaded.
>
>

-- 
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/e2f27eb7-27ee-4c34-93c7-f926706df6f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] 4.4.91-ti-r133 SPI0 "48030000.spi: chipselect 0 already in use"

[nemith592]

Hi,


I can't create SPIDEVx character devices in /dev. I recompiled my 
BB-SPI0-00A0.dts 
with the released dtc compiler. 

In the uEnv.txt file, I tried moving the BB-SPI0-00A0.dtbo to 
cape_enable=bone_capemgr.enable_partno=BB-KATS,BB-SPI0 
and got the following error "4803.spi: chipselect 0 already in use". 

How do I determine what is assigned to the SPI0 CS pin?

What default or base device tree binary does the U-Boot enabled uEnv.txt 
file use?


PS: I did try the generic BB-SPIDEV0 overlay and got the same error.


sudo  /opt/scripts/tools/version.sh

git:/opt/scripts/:[23650994e41b16bcf78253cde7d35a93664beeef]

eeprom:[A335BNLT00C03016BBBK0E44]

model:[TI_AM335x_BeagleBone_Black]

dogtag:[BeagleBoard.org Debian Image 2017-10-10]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
2017.09-2-g0f3f1c7907]

kernel:[4.4.91-ti-r133]

nodejs:[v6.12.0]

uboot_overlay_options:[enable_uboot_overlays=1]

uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-KATS-00A0.dtbo]

uboot_overlay_options:[uboot_overlay_addr5=/lib/firmware/BB-SPI0-00A0.dtbo]

uboot_overlay_options:[disable_uboot_overlay_video=1]

uboot_overlay_options:[disable_uboot_overlay_audio=1]

uboot_overlay_options:[disable_uboot_overlay_wireless=1]

uboot_overlay_options:[disable_uboot_overlay_adc=1]

uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo]

uboot_overlay_options:[enable_uboot_cape_universal=1]

pkg:[bb-cape-overlays]:[4.4.20171126.0-0rcnee1~stretch+20171126]

pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]

pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

-- 
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/8f0ac3ba-7af2-44ed-adb2-b0d74e2f2f19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Programming on Beagle Bone

[rohithpoona]

Hello everyone, 

We are developing a industrial gateway on pocket beagle bone.

For the standalone application we want to write the python code.  So that 
during boot up we will add C Project binaries  &  Python Project binaries.

Just want to know if we can use both C and Python for the development .




-- 
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/55cca5ca-b4ad-4dbb-a5a1-f1e505ed2a75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] about using uBoot

[amosku]

Hi,

I intend to let my Beaglebone Black board to boot into an application that 
I wrote. After many Google searches, I came across some discussion about 
using uBoot.
However, the instructions on getting uBoot to work have been very confusing 
to me. Can anyone point me to a webpage where instructions are clear and 
guarantee to work?

-- 
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/9ff8b147-c55a-4c9a-85c9-059d04f37237%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Not working GPIO pins

[amosku]

Hi,

This is my first time using Beaglebone black. 

While I am developing a poject, I realized that there are quite many GPIO 
pins on my new Beaglebone Black board that are not responding to the 
commands I keyed in in linux.

Has anyone seen a similar situation?

-- 
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/4ad6664a-ab10-4cf6-909a-35265f50f948%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] kernel module compile for beagle bone

[jishant03]

how to cross compile kernel module for beagle bone using host pc

i have cross compile images i have to build kernel module for beagle bone.

-- 
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/8719a59f-f84c-4e1f-93ac-8403610440b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] XOpenDisplay failed (:0) x11vnc version: 0.9.13

[kumar.rishi via BeagleBoard]

Hi,
I have trouble while executing X11VNC version: 0.9.13 from putty . Please 
below output.
help me necessary steps.
Thanks 
Dev


###
#@#
#@ @#
#@ ** WARNING ** WARNING ** WARNING ** WARNING ** @#
#@ @#
#@ YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!! @#
#@ @#
#@ This means anyone with network access to this computer @#
#@ may be able to view and control your desktop. @#
#@ @#
#@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
#@ @#
#@#
#@ @#
#@ You can create an x11vnc password file by running: @#
#@ @#
#@ x11vnc -storepasswd password /path/to/passfile @#
#@ or x11vnc -storepasswd /path/to/passfile @#
#@ or x11vnc -storepasswd @#
#@ @#
#@ (the last one will use ~/.vnc/passwd) @#
#@ @#
#@ and then starting x11vnc via: @#
#@ @#
#@ x11vnc -rfbauth /path/to/passfile @#
#@ @#
#@ an existing ~/.vnc/passwd file from another VNC @#
#@ application will work fine too. @#
#@ @#
#@ You can also use the -passwdfile or -passwd options. @#
#@ (note -passwd is unsafe if local users are not trusted) @#
#@ @#
#@ Make sure any -rfbauth and -passwdfile password files @#
#@ cannot be read by untrusted users. @#
#@ @#
#@ Use x11vnc -usepw to automatically use your @#
#@ ~/.vnc/passwd or ~/.vnc/passwdfile password files. @#
#@ (and prompt you to create ~/.vnc/passwd if neither @#
#@ file exists.) Under -usepw, x11vnc will exit if it @#
#@ cannot find a password to use. @#
#@ @#
#@ @#
#@ Even with a password, the subsequent VNC traffic is @#
#@ sent in the clear. Consider tunnelling via ssh(1): @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/#tunnelling @#
#@ @#
#@ Or using the x11vnc SSL options: -ssl and -stunnel @#
#@ @#
#@ Please Read the documention for more info about @#
#@ passwords, security, and encryption. @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/faq.html#faq-passwd @#
#@ @#
#@ To disable this warning use the -nopw option, or put @#
#@ 'nopw' on a line in your ~/.x11vncrc file. @#
#@ @#
#@#
###
23/11/2017 13:41:27 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 823
23/11/2017 13:41:27 XOpenDisplay(":0") failed.
23/11/2017 13:41:27 Trying again with XAUTHLOCALHOSTNAME=localhost ...

23/11/2017 13:41:27 ***
23/11/2017 13:41:27 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the 
failure.

Some tips and guidelines:

** An X server (the one you wish to view) must be running before x11vnc is
started: x11vnc does not start the X server. (however, see the -create
option if that is what you really want).

** You must use -display , -OR- set and export your $DISPLAY
environment variable to refer to the display of the desired X server.
- Usually the display is simply ":0" (in fact x11vnc uses this if you forget
to specify it), but in some multi-user situations it could be ":1", ":2",
or even ":137". Ask your administrator or a guru if you are having
difficulty determining what your X DISPLAY is.

** Next, you need to have sufficient permissions (Xauthority)
to connect to the X DISPLAY. Here are some Tips:

- Often, you just need to run x11vnc as the user logged into the X session.
So make sure to be that user when you type x11vnc.
- Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
file may be accessed. The cookie file contains the secret key that
allows x11vnc to connect to the desired X DISPLAY.
- You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
by the -auth option, e.g.:
x11vnc -auth /home/someuser/.Xauthority -display :0
x11vnc -auth /tmp/.gdmzndVlR -display :0
you must have read permission for the auth file.
See also '-auth guess' and '-findauth' discussed below.

** If NO ONE is logged into an X session yet, but there is a greeter login
program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
to find and use the raw display manager MIT-MAGIC-COOKIE file.
Some examples for various display managers:

gdm: -auth /var/gdm/:0.Xauth
-auth /var/lib/gdm/:0.Xauth
kdm: -auth /var/lib/kdm/A:0-crWk72
-auth /var/run/xauth/A:0-crWk72
xdm: -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
dtlogin: -auth /var/dt/A:0-UgaaXa

Sometimes the command "ps aux | grep auth" can reveal the file location.

Starting with x11vnc 0.9.9 you can have it try to guess by using:

-auth guess

(see also the x11vnc -findauth option.)

Only root will have read permission for the file, and so x11vnc must be run
as root (or copy it). The random characters in the filenames will of course
change and the directory the cookie file resides in is system dependent.

See also: http://www.karlrunge.com/x11vnc/faq.html
UNIX1977