Re: [beagleboard] BBB device tree compile

[Madhu K]

you want to compile am335x-boneblack.dts file?

On Fri, Apr 21, 2017 at 1:57 AM,  wrote:

> I am using Debian 4.6.3-14 and trying to compile a brand new device tree
> (the entire thing, not just an overlay) and I am getting errors trying to
> use the dtc functions. I read that it may be possible to use the make
> function to compile the device tree but have not seen anything specific to
> the BeagleboneBlack.
>
> If anyone has experience compiling a complete device tree on the
> beaglebone I would love to hear your input or links to relevant information.
>
> --
> 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/f492d554-5aa4-4d5d-862b-1461abf68546%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/CAA2oCOkGceHxNwiSK%2BKc86wiMuCeRo1TfMBFHZR6EKqP%2BataMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Debian Testing, un-root athon!!! (2017-04-18)

[Robert Nelson]

On Thu, Apr 20, 2017 at 8:09 PM, Mark A. Yoder  wrote:
> Well, I disabled the audio as described and I still get:
>
> debian@Bone:~$ config-pin P9_31 spi
> P9_31 pinmux file not found!
> cape-universala overlay not found
> debian@Bone:~$ config-pin -q P9_31
> P9_31 pinmux file not found!
> cape-universala overlay not found
> run "config-pin overlay cape-universala" to load the cape
> debian@Bone:~$ config-pin -q P9_32
> Pin is not modifyable: P9_32 VADC
> debian@Bone:~$ config-pin -q P9_28
> P9_28 pinmux file not found!
> cape-universala overlay not found
>
> Could the P9_31 and P9_28 enteries be missing from the overlay?

Yuck! Thanks Mark, i'll test that tomorrow morning, it should have worked. .;)

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

[beagleboard] BBB device tree compile

[jar6307]

I am using Debian 4.6.3-14 and trying to compile a brand new device tree 
(the entire thing, not just an overlay) and I am getting errors trying to 
use the dtc functions. I read that it may be possible to use the make 
function to compile the device tree but have not seen anything specific to 
the BeagleboneBlack. 

If anyone has experience compiling a complete device tree on the beaglebone 
I would love to hear your input or links to relevant information.

-- 
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/f492d554-5aa4-4d5d-862b-1461abf68546%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Debian Testing, un-root athon!!! (2017-04-18)

[Mark A. Yoder]

Well, I disabled the audio as described and I still get:

debian@Bone:~$ *config-pin P9_31 spi*
P9_31 pinmux file not found!
cape-universala overlay not found
debian@Bone:~$ *config-pin -q P9_31*
P9_31 pinmux file not found!
cape-universala overlay not found
run "config-pin overlay cape-universala" to load the cape
debian@Bone:~$ *config-pin -q P9_32*
Pin is not modifyable: P9_32 VADC
debian@Bone:~$ *config-pin -q P9_28*
P9_28 pinmux file not found!
cape-universala overlay not found

Could the P9_31 and P9_28 enteries be missing from the overlay?


--Mark

On Thursday, April 20, 2017 at 6:07:15 PM UTC-4, RobertCNelson wrote:
>
>
>
> On Apr 20, 2017 4:34 PM, "Mark A. Yoder"  > wrote:
>
> I'm having trouble with config-pin:
>
> $ *config-pin -a P9_30 spi # Data out*
> $ *config-pin -a P9_31 spi # Clock*
> P9_31 pinmux file not found!
> P9_31 overlay not found
> Loading cape-universala overlay
> bash: line 0: echo: write error: File exists
> Error loading device tree overlay file: cape-universala
>
> P9_30 configures but P9_31 doesn't.  I'm running as debian.
>
>
> Don't use the -a option, the overlay is setup to auto load. 
>
> Those pins are the audio side of HDMI..
>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices
>
> Add this to /boot/uEnv.txt
>
> disable_uboot_overlay_audio=1
>
> And reboot.
>
> Regards
>

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

Re: [beagleboard] Re: Debian Testing, un-root athon!!! (2017-04-18)

[Robert Nelson]

On Apr 20, 2017 4:34 PM, "Mark A. Yoder"  wrote:

I'm having trouble with config-pin:

$ *config-pin -a P9_30 spi # Data out*
$ *config-pin -a P9_31 spi # Clock*
P9_31 pinmux file not found!
P9_31 overlay not found
Loading cape-universala overlay
bash: line 0: echo: write error: File exists
Error loading device tree overlay file: cape-universala

P9_30 configures but P9_31 doesn't.  I'm running as debian.


Don't use the -a option, the overlay is setup to auto load.

Those pins are the audio side of HDMI..

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices

Add this to /boot/uEnv.txt

disable_uboot_overlay_audio=1

And reboot.

Regards

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

Re: [beagleboard] Re: Debian Testing, un-root athon!!! (2017-04-18)

[Mark A. Yoder]

I'm having trouble with config-pin:

$ *config-pin -a P9_30 spi # Data out*
$ *config-pin -a P9_31 spi # Clock*
P9_31 pinmux file not found!
P9_31 overlay not found
Loading cape-universala overlay
bash: line 0: echo: write error: File exists
Error loading device tree overlay file: cape-universala

P9_30 configures but P9_31 doesn't.  I'm running as debian.

--Mark


On Wednesday, April 19, 2017 at 10:19:11 PM UTC-4, RobertCNelson wrote:
>
> On Wed, Apr 19, 2017 at 2:38 PM, Mark A. Yoder  > wrote: 
> > The big picture is:  I'd like to use these in a workshop and the the 
> > participants play all they want.  Once we are done I want to run one 
> command 
> > to reset everything. 
> > 
> > I can't count on having internet, so a local git repo sounds like a good 
> > idea. 
>
> Okay give the bone101 package update a shot: 
>
> sudo apt update ; sudo apt upgrade 
>
> 1: backup old example folder: 
>
>
> https://github.com/rcn-ee/repos/blob/master/debian-9-bone101/suite/stretch/debian/preinst#L3-L9
>  
>
> 2: init example folder as a git repo, so it's initial state is always set: 
>
>
> https://github.com/rcn-ee/repos/blob/master/debian-9-bone101/suite/stretch/debian/postinst#L51-L58
>  
>
> 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/67769e3c-7c40-4257-97ad-d98d5bf347ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Official eQEP driver Support

[fisher . grubb]

Hi all,

I'm trying to use the eQEP Linux driver.  I can get it to load by adding a 
device tree overlay, but it doesn't increment much.  I can see that its 
loaded (called tieqep) with lsmod etc.

I've never used a quadrature encoder before, so I question if I just havn't 
connected it correctly.

At times it doesn't increment (reading Position file in 
/sys/device/ocp/epwmss48.. folder), other times it increments or 
decrements 2 or 3 positions.

If I jiggle the wheel back and forth a small a amount, it counts a lot. 
 The dual hall effect sensor outputs clean and clear waveforms at 3.3v, 90 
degrees out of phase, switches phase when change wheel direction just as I 
expected.

I'm only using channels A and B, did not touch other connections.

I've tried using all 3 eQEPs separately (including the 2b overlay for 
alternate pins of eQEP2).  I've used Derek Molloy's P9 and P8 header files.

Currently have proto-cape with pins 35 (A input)and 33 (B input)on P8 
header for eQEP1.

Other eQEPs have same behaviour.  I've also swapped the beaglebone black 
board with a new one.

I'm using kernel 4.4.9-ti-rt-r25 but with old llibraries and system from 
like 2015 I think as Simulink doesn't officially support anything higher. 
 I only upgraded the kernel.

Please let me know if anyone has any advice.

Thanks,
Fisher

On Saturday, 14 November 2015 03:41:59 UTC+10, dickelbeck wrote:
>
> > I would like to make known a bug we ran into with reading the eQEP 
> module that resulted in position values not updating after exactly 1020 
> reads without closing the file pointer.
>
> Of course you are using a low level read function, not buffered userspace 
> IO like fscanf().  
> That is, use read() not fscanf().  Then try using seek() back to file 
> begin, offset 0, in between reads.
>
> HTH,
>
> Dick
>
>
>

-- 
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/fc07fe81-85fd-492d-9921-eafc88f89672%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] eQEP1 setup problems with latest debian iOT

[Hugh Frater]

Following on from my earlier messages related to this, I am using 
cape-universal now to setup and control the pins for my mechatronics 
project. Pinmap constraints mean I need to use eQEP1 and eQEP2. eQEP2 on 
P8_11, P8_12 and P8_16 is working, but I can't get config-pin to setup 
eQEP1 on P8_31, P8_33 and P8_35.

root@beaglebone:/dev# config-pin -l P8_31 
default gpio gpio_pu gpio_pd uart qep

You can see qep is a supported mode.

root@beaglebone:/dev# config-pin P8_31 qep
bash: line 0: echo: write error: No such device
Cannot write pinmux file: /sys/devices/platform/ocp/ocp:P8_31_pinmux/state

And that is the error I get...

Does anyone know what is going on here? This 2nd encoder input is the last 
bit of the pinmux'ing puzzle I need to sort out, all the other GPIO is 
working nicely now.

Thanks, Hugh

-- 
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/d4410432-ed85-49b0-8fe7-c1ca3c1cd76c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: As much as possible GPIO Outs . What should I do ?

[Graham]

Depending on how fast you need to control and respond to the GPIO, it may 
be easier to
use the I2C bus and control some GPIO expanders.

A chip like the PCA9555 will get you 16 each GPIO, and you can control 8 of 
them on an I2C bus.
If you need more GPIO than that, you can buy other parts that occupy 
different I2C addresses and
put another 8 times 16 GPIO on the bus.

This also adds a layer of isolation between the BBB and the GPIO.  The GPIO 
pins on the
expanders are more rugged than the GPIO pins on the BBB, and a Voltage 
spike would kill
the cheap expander IC, and generally, not the more expensive BBB.

Depending on how you organize things, using the I2C bus approach will add 
several milliseconds to
respond to, or command the GPIO.  On the other hand, you are running under 
Linux, which has it's 
own delays and jitter that can be greater than that.

So, how many do you need? and what are your timing requirements for sensing 
the state of a pin
or commanding an output on the pin?

--- Graham

==

On Wednesday, April 19, 2017 at 10:20:23 PM UTC-5, Immo wrote:
>
> Hi, I need the maximum possible GPIOs out of the BBB.
> I'll direct connect a optocopler to decouple the bbb form the external 
> devices.
> But my first tries with P8 Pin 3-46 wher enot successful may be my overlay 
> file is a bit to big. Or do somebody the same.? How about the boot pins ? 
> If I use them as output do I have to pull them down anyway ?
>
> Immo
>

-- 
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/ca25d19a-bdb1-49ee-adb3-15d8b1dde6df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Black and RS485 Cape Interface

[narravamsikrishna92]

hello hi Travis Lytle i am using same waveshare cape to interface with my 
begalbone black.here i have to read can data using begalbone black but i 
have some questions regarding this can u please help me out?? 

if i use this board with my begal bone black is it possible to read CAN 
messages ???

how to interface this with my begalbone black board?? i mean any circuit 
diagram?? 
is there 120ohm termination resistor on board?
On Sunday, October 9, 2016 at 3:30:23 AM UTC+2, Travis Lytle wrote:
>
> I've use the dts from waveshare website and have used the can portion of 
> the board with no issue.
>
> http://www.waveshare.com/wiki/RS485_CAN_CAPE
>
>
>
> On Friday, September 23, 2016 at 9:10:14 AM UTC-4, 
> sri...@faststreamtech.com wrote:
>>
>> Hi,
>>
>>  I got this Beaglebone Black RS485 Cape from amazon 
>> https://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps=BeagleBone+Black+CAPE+RS485=1
>>  
>>  I'm new to Beaglebone Black and RS485 Cape. I didn't any source for the 
>> communication between RS485 and BBB online. So I need help in software 
>> module and and how to communicate using RS485 via BBB. In the end I want to 
>> control Relay (3.3V / 5V) using RS485 Cape.
>>
>

-- 
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/5ee83611-5fd1-4afc-a9bf-d7c36b4a9549%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: SSH with internet through USB not working for minimal image of BBB

[sajeevan k]

*Hi Dennis,Regarding this issue, now I included all the modules associated 
with Ethernet CDC as built in modules.(For this I selected Ethernet CDC as 
USB Gadget driver, instead of M(Module), Y(Include) is selected for*

* USB Gadget driver )When I search for all build in modules with filters, 
it is showing the following results*

debian@arm:/etc/network$ cat /lib/modules/$(uname -r)/modules.builtin | 
grep usb_f*
kernel/drivers/power/supply/axp20x_usb_power.ko
kernel/drivers/usb/gadget/function/usb_f_ecm.ko
kernel/drivers/usb/gadget/function/usb_f_ecm_subset.ko
kernel/drivers/usb/gadget/function/usb_f_rndis.ko
kernel/drivers/usb/musb/musb_hdrc.ko
kernel/drivers/usb/musb/musb_dsps.ko
kernel/drivers/usb/musb/musb_am335x.ko
debian@arm:/etc/network$ 

debian@arm:/etc/network$ cat /lib/modules/$(uname -r)/modules.builtin | 
grep g_ether
kernel/drivers/usb/gadget/legacy/g_ether.ko

debian@arm:/etc/network$ cat /lib/modules/$(uname -r)/modules.builtin | 
grep u_ether
kernel/drivers/usb/gadget/function/u_ether.ko



*That means the modules g_ether, u_ether, usb_f_rndis, usb_f_ecm etc. are 
there and active in BBB.Also /etc/network/interfaces is as follows.*


auto lo
iface lo inet loopback

iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1







*But still ssh debian@192.168.7.2 is not working. Is there anything more to 
be done for that?Thanks in advance for the help.Thanks & Regards,Sajeevan.K*

On Thursday, April 20, 2017 at 10:02:27 AM UTC+5:30, sajeevan k wrote:
>
>
> Hi Dennis Lee,
>
> Q: Did you build the added modules has kernal built-in objects, or as 
> loadable objects ?
>
> A: I was building the added modules as loadable objects.
> Also I am working on systemctrl and initd systems.
>
> Initially I included all the loadable modules(g_mass_storage, 
> usb_f_mass_storage and g_multi) in
> /etc/modules-load.d/modules.conf
>
> Then after reboot it is showing the following message:
>
> [FAILED] Failed to start Load Kernel Modules
> see 'systemctl status systemd-modules-load.service'   for details.
>
> systemctl status systemd-modules-load.service shows the following errors
>
> debian@arm:~$ systemctl status systemd-modules-load.service
> ● systemd-modules-load.service - Load Kernel Modules
>Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; 
> static; ven
>Active: failed (Result: exit-code) since Sat 2016-05-21 22:31:30 UTC; 
> 10 mont
>  Docs: man:systemd-modules-load.service(8)
>man:modules-load.d(5)
>  Main PID: 103 (code=exited, status=1/FAILURE)
>
> Warning: Journal has been rotated since unit was started. Log output is 
> incomple
> lines 1-8/8 (END)...skipping...
> ● systemd-modules-load.service - Load Kernel Modules
>Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; 
> static; ven
>Active: failed (Result: exit-code) since Sat 2016-05-21 22:31:30 UTC; 
> 10 mont
>  Docs: man:systemd-modules-load.service(8)
>man:modules-load.d(5)
>  Main PID: 103 (code=exited, status=1/FAILURE)
>
> Warning: Journal has been rotated since unit was started. Log output is 
> incomple
> ~
>
>
>
> Q: Did you recreate the, uhm from memory, initramfs (or whatever the files 
> loaded by u-boot are called) containing your added modules?
>
> I didn't understand what is meant by uhm. Googling also didn't provide me 
> the results.
> Please explain it.
>
> After I added the modules, the added modules were available in 
> /proc/modules, which  indicates they are active.
> But after reboot it is not availble in /proc/modules 
>
> Also 
>
> find /lib/modules/$(uname -r) -type f -name \*.ko  gives all the modules 
> including 
> g_mass_storage, usb_f_mass_storage and g_multi. I think this is the list of 
> all modules built.
>
> I am trying with systemctrl and initd systems. Please inform if I am missing 
> something.
> Thanks in advance for the help.
>
>
> Thanks & Regards,
> Sajeevan.K
>
>
> On Tuesday, April 18, 2017 at 7:00:54 PM UTC+5:30, Dennis Lee Bieber wrote:
>>
>> On Mon, 17 Apr 2017 23:30:50 -0700 (PDT), sajeevan k 
>>  declaimed the 
>> following: 
>>
>>
>> > 
>> >So I reboot and checked. But after rebooting, all this newly added 
>> modules 
>> >disappears.   
>> > 
>> > 
>> >How can I include the modules in such a way that, it is available even 
>> >after reboot? 
>> > 
>>
>> Again, we are beyond my actual experience -- this is just an 
>> hypothesis... 
>>
>> Did you recreate the, uhm from memory, initramfs (or whatever the 
>> files 
>> loaded by u-boot are called) containing your added modules? Did you build 
>> the added modules has kernal built-in objects, or as loadable objects -- 
>> the latter would require running some command during start-up 
>> (systemctrl? 
>> my experience is still the initd system)? 
>>
>> >I feel, if the Beaglebone drive appears, in Ubuntu Host, if BBB connect 
>> to 
>> >it through USB cable, 

Re: [beagleboard] Re: Explanation of PRU Programming in C

[Joseph Heller]

Thanks for the positive feedback. The TI video does not work on Mac though. 

I've now also included the hello world blink LED in C. 

> On 19 Apr 2017, at 19:38, Greg  wrote:
> 
> Excellent!  I did a couple of projects with PRU and C code, and this type of 
> tutorial is sorely needed.
> 
> I would add a link to this:
> 
> https://training.ti.com/pru-compiler-tips-tricks
> 
> So I wonder how common it is to use a C union and bit selector?
> When I first encountered this in the PRU header files, I didn't even think it 
> was C code!
> In fact, in the information provided by TI in the video and slides, they say 
> it is really warped C code.
> 
> Regards,
> Greg
> -- 
> 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/3KjD7ULjD6M/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/bb0d76a6-0108-4f8c-a027-5a461c73ec68%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/830480A5-BD30-4277-882F-230B7BB8D387%40gmail.com.
For more options, visit https://groups.google.com/d/optout.