Re: [beagleboard] Download a file from a beaglebone web server using client side

[Stuart Longland]

On 20/01/18 10:07, rmhayes1...@gmail.com wrote:
> Can someone explain what JavaScript should be in the server to catch the
> 'download' command and return the specified file? What should the
> "socket.on(???, downloadFile);" look like? What's the correct way to
> return the file so the client browser correctly saves it?

It looks much the same as what it does to display your index page, but
instead of setting "Content-Type: text/html" and dumping HTML, it sets
"Content-Type: application/octet-stream" and dumps binary data.

You haven't told us what HTTP server you're using, so it's a little
difficult to say exactly how you do it.  One commonly used one for this
task is Express…

https://expressjs.com/en/starter/hello-world.html gives an example of
doing more or less what you've done… if you were to modify that front
page with a hyperlink, the extra code would look like this:

app.get('/mydata.csv', function (req, res) {
res.set('Content-Type', 'application/octet-stream');
res.send('your CSV data');
});
-- 
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/ac0c7271-e36a-db67-b1d3-c6207da20f6d%40longlandclan.id.au.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB custom USB 4 Port Hub Expansion (NEW DESIGN)

[stephen . k . mansfield]

Hello Steve

On Tuesday, August 9, 2016 at 11:26:12 AM UTC-4, Steven Johnson wrote:
>
> I have been developing a 4 PORT USB Hub specifically designed for the 
> "quirks" of the BBB.
>
> It takes a regular BBB, extends it by only 16mm and increases the number 
> of HISH SPEED (480mbps) USB host ports to 4.
>
> It looks like this when attached:  
> http://imgur.com/kxBbbZR
> http://imgur.com/pMsLCIL
> http://imgur.com/gF6ZV62
>
> And this is what it looks like stand alone: 
> http://imgur.com/8RVfd3F
>
> It works great, and lines up with the mounting holes on the end of the 
> board near the existing USB Host port.  When screwed to those mounting 
> holes it is as structurally rigid as if the PCB was just longer.  It also 
> has hardware which is NON STANDARD for a normal USB HUB but which has been 
> added to the HUB to correct for deficiencies in the BBB Host Port Power 
> design.  Which means that the problems of hubs appearing and disappearing 
> and just generally misbehaving with the BBB do not occur with this hub.
>
> The reason for this post is to let people know this thing exists.
>
> I am currently working on the logistics of producing a batch of these 
> boards, part of the unknown is if there is anyone who would be interested 
> in buying it, and if so how many people that is.  Volume has a direct 
> impact on my ability to produce these at any reasonable price.  So please 
> dont ask me how much i will sell it for,  my aim is to sell it as cheaply 
> as reasonably possible.
>
> Prototypes of this board are currently being used by a few Replicape 
> developers with no reported faults.
>
> It can be run either SELF Powered, or BUS Powered from the BBB.
>
> A special non USB Compliant but useful mode is BUS Powered, but reporting 
> to the BBB as SELF Powered.  This is very handy for the use case where 
> there are multiple devices and the sum total of their reported power 
> consumption exceeds 500ma, but in use only one device is active at a time, 
> so the average draw is only 500ma.  Obviously, this mode is only intended 
> for experienced people who really understand what the implications are.
>
> If you have any questions I am happy to expand, if this device is of 
> interest to you please let me know so I can try and work out what sort of 
> volume i should produce, or if i should produce it at all.
>
> Strontium
>

-- 
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/ef7daab6-b76b-42ca-8eee-51ea3271224c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB custom USB 4 Port Hub Expansion (NEW DESIGN)

[stephen . k . mansfield]

Hello Steve,

The board looks pretty cool.  How can I purchase 5 of these boards?  How 
long will it take?  How much and where do I send the check?

Regards,
Steve Mansfield
stephen.k.mansfi...@gmail.com

On Tuesday, August 9, 2016 at 11:26:12 AM UTC-4, Steven Johnson wrote:
>
> I have been developing a 4 PORT USB Hub specifically designed for the 
> "quirks" of the BBB.
>
> It takes a regular BBB, extends it by only 16mm and increases the number 
> of HISH SPEED (480mbps) USB host ports to 4.
>
> It looks like this when attached:  
> http://imgur.com/kxBbbZR
> http://imgur.com/pMsLCIL
> http://imgur.com/gF6ZV62
>
> And this is what it looks like stand alone: 
> http://imgur.com/8RVfd3F
>
> It works great, and lines up with the mounting holes on the end of the 
> board near the existing USB Host port.  When screwed to those mounting 
> holes it is as structurally rigid as if the PCB was just longer.  It also 
> has hardware which is NON STANDARD for a normal USB HUB but which has been 
> added to the HUB to correct for deficiencies in the BBB Host Port Power 
> design.  Which means that the problems of hubs appearing and disappearing 
> and just generally misbehaving with the BBB do not occur with this hub.
>
> The reason for this post is to let people know this thing exists.
>
> I am currently working on the logistics of producing a batch of these 
> boards, part of the unknown is if there is anyone who would be interested 
> in buying it, and if so how many people that is.  Volume has a direct 
> impact on my ability to produce these at any reasonable price.  So please 
> dont ask me how much i will sell it for,  my aim is to sell it as cheaply 
> as reasonably possible.
>
> Prototypes of this board are currently being used by a few Replicape 
> developers with no reported faults.
>
> It can be run either SELF Powered, or BUS Powered from the BBB.
>
> A special non USB Compliant but useful mode is BUS Powered, but reporting 
> to the BBB as SELF Powered.  This is very handy for the use case where 
> there are multiple devices and the sum total of their reported power 
> consumption exceeds 500ma, but in use only one device is active at a time, 
> so the average draw is only 500ma.  Obviously, this mode is only intended 
> for experienced people who really understand what the implications are.
>
> If you have any questions I am happy to expand, if this device is of 
> interest to you please let me know so I can try and work out what sort of 
> volume i should produce, or if i should produce it at all.
>
> Strontium
>

-- 
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/6ecaca3c-e92e-4f6b-9efa-dc835c7e5428%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Newcomer questions: capes and overlays

[lgilbert]

Hi Robert,

With regard to your comment on uboot overlays, slots 0-3 vs 4-7, where 
should one place a standard .dtbo ( eQEP, 2b ) to get it to load properly?  
 I have not had luck with slot 0 or 4...

thanks...


On Thursday, November 30, 2017 at 6:15:20 PM UTC-8, beagle...@gmail.com 
wrote:
>
> Hi,
>
> I'm just getting started on this great platform and I've got some 
> questions about capes/overlays on which I thought perhaps someone could 
> share their expertise.
>
> Most of the documentation you find online still refers to cape manager and 
> slots, which is slightly confusing for beginners. I did find this page [1] 
> and I understand (I think) that t*here is no longer a cape manager and 
> that u-boot does the loading of capes*.
>
> So first questions:
>
> - Is this assumption correct?
> - I do understand the concept of the device tree and loading overlays, 
> but... what is the difference between *overlays*, *capes* and *virtual 
> capes*? I've seen all mentioned in various places, but nowhere could I 
> find a description of each. I've also seen "*manual overlays*" mentioned. 
> Do they all actually refer to the same thing?
> - How can one see which capes/overlays are loaded once the system has 
> booted up in the new uboot overlays world?
>
> I'm starting to look at the PRUSS and how to use them, and I'm not sure 
> which overlays should be loaded to enable them, or if access to them is 
> already enabled by default. On /boot/uEnv.txt there seem to be a couple of 
> options, one of which is commented out. I notice the difference in the 
> naming ('*-RPROC-*', vs. *-UIO-* commented out), so I'm guessing that the 
> RPROC PRUSS overlay is loaded and the UIO one is not.
>
> But could someone elaborate a bit more on this?
>
> ###PRUSS OPTIONS
> ###pru_rproc (4.4.x-ti kernel)
> uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo
> ###pru_uio (4.4.x-ti & mainline/bone kernel)
> #uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
>
> Finally, on my /boot/uEnv.txt file I can see these lines, which I 
> understand are for older kernels. As a humble piece of feedback from a 
> newcomer, these make the file more confusing for options that no longer 
> apply. Would it not make sense to remove them for new images? 
>
> ##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=
>
> Thanks!
>
> [1] https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
>

-- 
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/e7462ce4-45f1-4ea1-aee3-568bb6819592%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Download a file from a beaglebone web server using client side

[rmhayes1954]

I have a web server running on a BBB and serving an html page with some 
tabular data and control buttons. On demand, I would like to download a 
file of the tabular data to the client. I can create, write, and delete the 
file with the fs module.

In the web page, I have HTML like Click to 
download.

When I click, I get a download file named "Sample.txt" but the contents of 
the file are the HTML code of the web page.  I think this is because I am 
not handling the download command in the server side JavaScript.

Can someone explain what JavaScript should be in the server to catch the 
'download' command and return the specified file? What should the 
"socket.on(???, downloadFile);" look like? What's the correct way to return 
the file so the client browser correctly saves it?

I can provide the rest of the code if needed, but it seems to be working - 
I just can't find references to handling the file download from that  
element.

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/ea30a94a-b568-44f3-b1e6-da614dbb84a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: More pimux woes

[lgilbert]

When I load a .dtbo  though my uEnv.txt file (ie, 
uboot_overlay_addr4=/lib/firmware/bone_eqep2b-00A0.dtbo ) I no longer have 
access to config-pin's ability to set up ANY pins.   Is there some sort of 
exclusiveness built into the system such that if .dtbos are found, then you 
cannot manually configure pins after boot with the config-pin utility?

My system info:
[root@beaglebone]> uname -a
Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
GNU/Linux

Thanks in advance!


On Thursday, January 18, 2018 at 4:53:59 AM UTC-8, Hugh Frater wrote:
>
> I've been trying to get my test hardware back up and running after 
> corrupting node and bonescript, see my earlier post.
>
> I'm trying to get up and running with an 8.6 image as I couldn't get a 9.2 
> image to provide pru_rproc support
>
> debian@beaglebone:~$ uname -r
> 4.4.54-ti-r93
>
> I'm trying to get the eqep support working on P8_31,33 & 35 (it was 
> working before)
>
> debian@beaglebone:~$ sudo config-pin -l P8_31
> default gpio gpio_pu gpio_pd uart qep
>
> Looks like qep is a supported mode...
>
> debian@beaglebone:~$ sudo config-pin P8_31 qep
> [sudo] password for debian: 
> bash: line 0: echo: write error: No such device
> Cannot write pinmux file: /sys/devices/platform/ocp/ocp:P8_31_pinmux/state
>
> Any idea what is causing the above error? The important bits from uEnv.txt 
> are:
>
> ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:
> dtb=am335x-boneblack-overlay.dtb
>
> cmdline=coherent_pool=1M net.ifnames=0 quiet cape-universal=enable
>
> ##Example v4.1.x
> #cape_disable=bone_capemgr.disable_partno=
> cape_enable=bone_capemgr.enable_partno=cape-universala
>
>
>
>
>
>
>
>

-- 
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/246ca2a9-97a3-4f96-a78d-26bf03c64c98%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Debian Testing (2017-04-30) U-Boot Overlays are now enabled by Default

[lgilbert]

Hi Everyone,
 

I've been working with a Beaglebone Black recently and its eQEP peripheral; 
running into an issue where it works great when I manually configure it (with 
the config-pin command), but not when I set the pins up with a .dtbo...

First, here's my system info:
[root@beaglebone]> uname -a
Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
GNU/Linux

[root@beaglebone]> cat /boot/uEnv.txt
#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.4.91-ti-r133
#uuid=
dtb=
#dtb=am335x-boneblack-overlay.dtb


###U-Boot Overlays###
###Documentation: 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
###Master Enable
enable_uboot_overlays=1
###
###Overide capes with eeprom
uboot_overlay_addr0=/lib/firmware/bone_eqep2b-00A0.dtbo
#uboot_overlay_addr1=/lib/firmware/.dtbo
#uboot_overlay_addr2=/lib/firmware/.dtbo
#uboot_overlay_addr3=/lib/firmware/.dtbo
###
###Additional custom capes
#uboot_overlay_addr4=/lib/firmware/bone_eqep0-00A0.dtbo
#uboot_overlay_addr5=/lib/firmware/BB-PWM1-00A0.dtbo
#uboot_overlay_addr6=/lib/firmware/.dtbo
#uboot_overlay_addr7=/lib/firmware/.dtbo
###
###Custom Cape
#dtb_overlay=/lib/firmware/.dtbo
###
###Disable auto loading of virtual capes (emmc/video/wireless/adc)
disable_uboot_overlay_emmc=1
disable_uboot_overlay_video=1
disable_uboot_overlay_audio=1
disable_uboot_overlay_wireless=1
#disable_uboot_overlay_adc=1
###
###PRUSS OPTIONS
###pru_rproc (4.4.x-ti kernel)
uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo
###pru_uio (4.4.x-ti & mainline/bone kernel)
#uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
###
###Cape Universal Enable
enable_uboot_cape_universal=1
###
###Debug: disable uboot autoload of Cape
#disable_uboot_overlay_addr0=1
#disable_uboot_overlay_addr1=1
#disable_uboot_overlay_addr2=1
#disable_uboot_overlay_addr3=1
###
###U-Boot fdt tweaks...
#uboot_fdt_buffer=0x6
###U-Boot Overlays###

#cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
cmdline=coherent_pool=1M net.ifnames=0 quiet

#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M net.ifnames=0 quiet 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=

##enable Generic eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh


With this configuration, after booting:

[root@beaglebone]> find /sys/devices | grep eqep | grep position
/sys/devices/platform/ocp/48304000.epwmss/48304180.eqep/position


[root@beaglebone]> cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins
registered pins: 142
pin 0 (44e10800.0) 0031 pinctrl-single
pin 1 (44e10804.0) 0031 pinctrl-single
pin 2 (44e10808.0) 0031 pinctrl-single
pin 3 (44e1080c.0) 0031 pinctrl-single
pin 4 (44e10810.0) 0027 pinctrl-single
pin 5 (44e10814.0) 0027 pinctrl-single
pin 6 (44e10818.0) 0027 pinctrl-single
pin 7 (44e1081c.0) 0027 pinctrl-single
pin 8 (44e10820.0) 0027 pinctrl-single
pin 9 (44e10824.0) 0027 pinctrl-single
pin 10 (44e10828.0) 0027 pinctrl-single
pin 11 (44e1082c.0) 0027 pinctrl-single
pin 12 (44e10830.0) 002c pinctrl-single
pin 13 (44e10834.0) 002c pinctrl-single
pin 14 (44e10838.0) 002c pinctrl-single
pin 15 (44e1083c.0) 002c pinctrl-single
pin 16 (44e10840.0) 0027 pinctrl-single
pin 17 (44e10844.0) 0027 pinctrl-single
.
.
.


-->All of this looks good, and I have a good encoder signal going to pins p8.11 
& p8.12 (pins 13 & 14 above) on the BBB.   However, my counts keep hovering 
within +/-10 of 0, ie, they're not incrementing.

My mode is set to Absolute...
[root@beaglebone]> cat mode
0

and my period is 1sec
[root@beaglebone]> cat period
10

here are the contents of the eqep device folder:
/sys/devices/platform/ocp/48304000.epwmss/48304180.eqep/
[root@beaglebone]> ls -lha
total 0
drwxr-xr-x 3 root root0 Jan 18 22:39 .
drwxr-xr-x 4 root root0 Jan 18 22:39 ..
lrwxrwxrwx 1 root root0 Jan 18 22:39 driver -> 
../../../../../bus/platform/drivers/eqep
-rw-r--r-- 1 root root 4.0K Jan 18 22:39 driver_override
-rw-r--r-- 1 root root 4.0K Jan 18 22:39 enabled
-r--r--r-- 1 root root 4.0K Jan 18 22:39 modalias
-rw-r--r-- 1 root root 4.0K Jan 18 22:39 mode
lrwxrwxrwx 1 root root0 Jan 18 22:39 of_node -> 
../../../../../firmware/devicetree/base/ocp/epwmss@48304000/eqep@0x48304180
-rw-r--r-- 1 root root 4.0K Jan 18 22:39 period
-rw-r--r-- 1 root root 4.0K Jan 18 22:39 position
drwxr-xr-x 2 root root0 Jan 18 22:39 power
lrwxrwxrwx 1 root root0 Jan 18 22:39 subsystem -> 
../../../../../bus/platform
-rw-r--r-- 1 root root 4.0K Jan 18 22:39 uevent


What's weird is when I comment out loading the eQEP 2b dtbo in the uEnv.txt 
file and boot, I can get my count working 

[beagleboard] Multiple RPMSG channels between PRU and Linux?

[Jesse Abella]

Hello, I am using the PRU to create multiple transceivers and I am trying 
to use the rpmsg_pru functions to create multiple /dev/rpmsg_pru** entries 
for each individual transceiver. Currently in all examples I see, PRU0 is 
restricted to use Port 30 and PRU1 is restricted to use Port 31. Is it 
possible to use any other port for these devices or create multiple 
channels from the same pru? Even when changing the port number in my 
pru_rpmsg_channel declaration to something other than 30, the device entry 
still shows up as 30.

-- 
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/cc16146c-eab2-4ab7-882c-d8f34faf2671%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Wiznet W5500 ethernet module driver can't install

[Graham]

But it will change the MAC address, every time you load a new image on the 
memory card.
--- Graham

==

On Thursday, January 18, 2018 at 10:42:57 PM UTC-6, santosh aiwale wrote:
>
>
> Thanks it's working now.
>
> actually problem was : I didn't connect RST, INT pin and kept floating. 
> Now it's connected and working fine.
>
> One more question is it possible to change RST and INT pin to other port 
> pin?
>
> On Thursday, 18 January 2018 22:29:41 UTC+5:30, RobertCNelson wrote:
>>
>> On Thu, Jan 18, 2018 at 10:32 AM, santosh aiwale 
>>  wrote: 
>> > Yes, sir I am trying with singal SPI0 but it's can't work board not 
>> booting. 
>> > 
>> > With 
>> > uboot_overlay_addr0=/lib/firmware/PB-SPI0-ETH-WIZ-CLICK.dtbo 
>> > 
>> > And using SPI1 
>> > uboot_overlay_addr0=/lib/firmware/PB-SPI1-ETH-WIZ-CLICK.dtbo 
>> > It's detect but can't communicate. 
>> > If i test ifconfig 
>> > 
>> > 
>> > eth0: flags=-28605  mtu 1500 
>> > inet 169.254.136.246  netmask 255.255.0.0  broadcast 
>> 169.254.255.255 
>> > inet6 fe80::34ad:5dff:fe89:940  prefixlen 64  scopeid 
>> 0x20 
>> > ether de:ad:be:ef:ca:fe  txqueuelen 1000  (Ethernet) 
>> > RX packets 0  bytes 0 (0.0 B) 
>> > RX errors 0  dropped 0  overruns 0  frame 0 
>> > TX packets 40  bytes 9097 (8.8 KiB) 
>> > TX errors 39  dropped 0 overruns 0  carrier 0  collisions 0 
>> > 
>> > This results Tx errors 
>> > And randomly ip changed. 
>>
>> Yeah, it works for me: 
>>
>> Grabbed this image: 
>>
>> https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-iot/ 
>>
>> added 
>>
>> uboot_overlay_addr0=/lib/firmware/PB-SPI1-ETH-WIZ-CLICK.dtbo 
>>
>> to /boot/uEnv.txt 
>>
>> then ssh'ed thru the eth0 interface.. 
>>
>> debian@beaglebone:~$ sudo ifconfig -a eth0 
>> eth0: flags=-28605  mtu 1500 
>> inet 192.168.0.149  netmask 255.255.255.0  broadcast 
>> 192.168.0.255 
>> inet6 fe80::94fb:95ff:fee3:4270  prefixlen 64  scopeid 0x20 
>> ether 96:fb:95:e3:42:70  txqueuelen 1000  (Ethernet) 
>> RX packets 181  bytes 25287 (24.6 KiB) 
>> RX errors 0  dropped 0  overruns 0  frame 0 
>> TX packets 145  bytes 26141 (25.5 KiB) 
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
>>
>> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh 
>> git:/opt/scripts/:[b372df3221bb67a9a09c6b89df5110ca32a9e482] 
>> eeprom:[A335PBGL00A21736GPB30111] 
>> model:[TI_AM335x_PocketBeagle] 
>> dogtag:[BeagleBoard.org Debian Image 2018-01-14] 
>> bootloader:[microSD]:[/dev/mmcblk0]:[U-Boot 2018.01-2-gcc9c2d1992] 
>> kernel:[4.9.76-ti-r91] 
>> nodejs:[v6.12.3] 
>> uboot_overlay_options:[enable_uboot_overlays=1] 
>> uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/PB-SPI1-ETH-WIZ-CLICK.dtbo]
>>  
>>
>> uboot_overlay_options:[enable_uboot_cape_universal=1] 
>> pkg:[bb-cape-overlays]:[4.4.20180104.0-0rcnee1~stretch+20180104] 
>> pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104] 
>> pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830] 
>> dmesg | grep pinctrl-single 
>> [1.436073] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 
>> size 568 
>> END 
>>
>> 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/7ce4d378-e218-4850-85e4-8eec05af3a2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: More pimux woes

[Hugh Frater]

Thanks Robert, I won’t be back in front of my BBB till Monday now but I’ll be 
sure to test it first thing.

-- 
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/5b8146ee-3982-4472-b6eb-1883101442c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: More pimux woes

[Robert Nelson]

On Fri, Jan 19, 2018 at 2:25 PM, Robert Nelson  wrote:
> On Fri, Jan 19, 2018 at 10:25 AM, Hugh Frater  wrote:
>> Top man, thanks for taking care of this. Let me know when it gets pushed up
>> and i'll re-run apt update
>
> Okay all pushed out..
>
> sudo apt update ; sudo apt upgrade bb-cape-overlays
>
> sudo reboot
>
> Please test it and let us know if those config-pin options work..

debian@test-bbb-4:~$ config-pin -q P9.42
P9_42 Mode: default Direction: in Value: 0
debian@test-bbb-4:~$ config-pin -l P9.42
default gpio gpio_pu gpio_pd gpio_input spi_cs spi_sclk uart pwm pru_ecap
debian@test-bbb-4:~$ config-pin P9.42 pru_ecap
debian@test-bbb-4:~$ config-pin -q P9.42
P9_42 Mode: pru_ecap

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

Re: [beagleboard] Re: More pimux woes

[Robert Nelson]

On Fri, Jan 19, 2018 at 10:25 AM, Hugh Frater  wrote:
> Top man, thanks for taking care of this. Let me know when it gets pushed up
> and i'll re-run apt update

Okay all pushed out..

sudo apt update ; sudo apt upgrade bb-cape-overlays

sudo reboot

Please test it and let us know if those config-pin options work..

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

Re: [beagleboard] Minimum needed to run a Qt4 program

[Hartley Sweeten]

On Friday, January 19, 2018 at 10:36:14 AM UTC-7, RobertCNelson wrote:
>
> On Fri, Jan 19, 2018 at 11:20 AM, Hartley Sweeten  > wrote: 
> > Hello all, 
> > 
> > Does anyone know what the minimum install is needed to get a Qt4 program 
> to 
> > run on a BeagleBone Black? 
> > 
> > I'm trying to get a kiosk type program running with a 7" touchscreen. I 
> have 
> > tried various LCD capes and have narrowed it down to a Newhaven 
> > NHD-7.0CTP-CAPE. That screen has a capacitive touch instead of a 
> resistive 
> > touch and seems to work a lot better. The capacitive touch doesn't have 
> the 
> > calibration issues I saw with the resistive touch. 
> > 
> > Starting with this image: 
> > 
> > https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-console/ 
> > 
> > I have verified that the LCD and touch work using the ts_test program 
> from 
> > the libts-bin package (thank Robert for adding the libts packages!). 
> > 
> > I have also tested the LCD and touch with SDL1.2 (again thanks to Robert 
> for 
> > adding libsdl1.2* with directfb and libts support!). 
> > 
> > Pygame also works fine with the updated libsdl1.2*. 
> > 
> > Great! I know the screen "works". Now hoe do I get a Qt4 program to 
> work? I 
> > have tried a simple program but when I run it I get: 
> > 
> > $ ./test 
> > test: cannot connect to X server 
> > 
> > The '-qws' switch also doesn't work. I think this is due to the Qt4 
> library 
> > not being compiled with the --embedded option (and possible other..). 
> > 
> > I have also tried to use xvfb (Virtual Framebuffer 'fake' X server). But 
> it 
> > either doesn't work or I'm doing something wrong. When I try to run the 
> test 
> > app I don't get any error messages but nothing happens. 
> > 
> > I don't want to use a full X11 install due to the bloat. I just need a 
> > working X server so that the Qt4 program will run. I could try building 
> Qt4 
> > with the necessary options but last time I tried it didn't work. I was 
> able 
> > to get the program to run on the LCD but the touchscreen didn't work. Of 
> > course that was with a resistive not the capacitive touchscreen. The 
> other 
> > problem was it takes something like 40 hours to build Qt4. Agh... 
>
> So QT5 ( i know it's not QT4 ;) ) 
>
> Has a direcfb that is currently disabled: 
>
>   QPA backends: 
> DirectFB . no 
> EGLFS  yes 
>   EGLFS i.MX6  no 
>   EGLFS i.MX6 Wayland. no 
>   EGLFS EGLDevice  yes 
>   EGLFS GBM .. yes 
>   EGLFS Mali . no 
>   EGLFS Raspberry Pi . no 
>   EGLFS X11 .. yes 
>
> It also has a tslib option: 
>
> tslib .. no 
>
>
> https://buildd.debian.org/status/fetch.php?pkg=qtbase-opensource-src=armhf=5.7.1%2Bdfsg-3=1484191682=0
>  
>
> we could try rebuilding 'qtbase-opensource-src' and see what happens.. 


 Qt4 or Qt5 will work for me.

I wasn't aware that Qt5 could work directly with the framebuffer. I thought 
QWS was needed in order to run without X. According to the following site, 
the QWS implementation was removed in Qt5:

http://doc.qt.io/qt-5/embedded-linux.html

Qt4 specifically states that it can work without X:

http://doc.qt.io/archives/qt-4.8/qt-embedded-linux.html

I'm willing to try either one it your willing to rebuild it :-)

Thanks,
Hartley



-- 
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/42797957-8b04-4c02-a2e0-ccfd2b90ec74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Minimum needed to run a Qt4 program

[Robert Nelson]

On Fri, Jan 19, 2018 at 11:20 AM, Hartley Sweeten  wrote:
> Hello all,
>
> Does anyone know what the minimum install is needed to get a Qt4 program to
> run on a BeagleBone Black?
>
> I'm trying to get a kiosk type program running with a 7" touchscreen. I have
> tried various LCD capes and have narrowed it down to a Newhaven
> NHD-7.0CTP-CAPE. That screen has a capacitive touch instead of a resistive
> touch and seems to work a lot better. The capacitive touch doesn't have the
> calibration issues I saw with the resistive touch.
>
> Starting with this image:
>
> https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-console/
>
> I have verified that the LCD and touch work using the ts_test program from
> the libts-bin package (thank Robert for adding the libts packages!).
>
> I have also tested the LCD and touch with SDL1.2 (again thanks to Robert for
> adding libsdl1.2* with directfb and libts support!).
>
> Pygame also works fine with the updated libsdl1.2*.
>
> Great! I know the screen "works". Now hoe do I get a Qt4 program to work? I
> have tried a simple program but when I run it I get:
>
> $ ./test
> test: cannot connect to X server
>
> The '-qws' switch also doesn't work. I think this is due to the Qt4 library
> not being compiled with the --embedded option (and possible other..).
>
> I have also tried to use xvfb (Virtual Framebuffer 'fake' X server). But it
> either doesn't work or I'm doing something wrong. When I try to run the test
> app I don't get any error messages but nothing happens.
>
> I don't want to use a full X11 install due to the bloat. I just need a
> working X server so that the Qt4 program will run. I could try building Qt4
> with the necessary options but last time I tried it didn't work. I was able
> to get the program to run on the LCD but the touchscreen didn't work. Of
> course that was with a resistive not the capacitive touchscreen. The other
> problem was it takes something like 40 hours to build Qt4. Agh...

So QT5 ( i know it's not QT4 ;) )

Has a direcfb that is currently disabled:

  QPA backends:
DirectFB . no
EGLFS  yes
  EGLFS i.MX6  no
  EGLFS i.MX6 Wayland. no
  EGLFS EGLDevice  yes
  EGLFS GBM .. yes
  EGLFS Mali . no
  EGLFS Raspberry Pi . no
  EGLFS X11 .. yes

It also has a tslib option:

tslib .. no

https://buildd.debian.org/status/fetch.php?pkg=qtbase-opensource-src=armhf=5.7.1%2Bdfsg-3=1484191682=0

we could try rebuilding 'qtbase-opensource-src' and see what happens..

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

[beagleboard] Minimum needed to run a Qt4 program

[Hartley Sweeten]

Hello all,

Does anyone know what the minimum install is needed to get a Qt4 program to 
run on a BeagleBone Black?

I'm trying to get a kiosk type program running with a 7" touchscreen. I 
have tried various LCD capes and have narrowed it down to a Newhaven 
NHD-7.0CTP-CAPE. That screen has a capacitive touch instead of a resistive 
touch and seems to work a lot better. The capacitive touch doesn't have the 
calibration issues I saw with the resistive touch.

Starting with this image:

https://rcn-ee.net/rootfs/bb.org/testing/2018-01-14/stretch-console/ 

I have verified that the LCD and touch work using the ts_test program from 
the libts-bin package (thank Robert for adding the libts packages!).

I have also tested the LCD and touch with SDL1.2 (again thanks to Robert 
for adding libsdl1.2* with directfb and libts support!).

Pygame also works fine with the updated libsdl1.2*.

Great! I know the screen "works". Now hoe do I get a Qt4 program to work? I 
have tried a simple program but when I run it I get:

$ ./test
test: cannot connect to X server

The '-qws' switch also doesn't work. I think this is due to the Qt4 library 
not being compiled with the --embedded option (and possible other..).

I have also tried to use xvfb (Virtual Framebuffer 'fake' X server). But it 
either doesn't work or I'm doing something wrong. When I try to run the 
test app I don't get any error messages but nothing happens.

I don't want to use a full X11 install due to the bloat. I just need a 
working X server so that the Qt4 program will run. I could try building Qt4 
with the necessary options but last time I tried it didn't work. I was able 
to get the program to run on the LCD but the touchscreen didn't work. Of 
course that was with a resistive not the capacitive touchscreen. The other 
problem was it takes something like 40 hours to build Qt4. Agh...

Regards,
Hartley

-- 
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/82cae07b-2174-4439-ae0c-756cb5a3497c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: More pimux woes

[Hugh Frater]

Top man, thanks for taking care of this. Let me know when it gets pushed up 
and i'll re-run apt update


On Friday, 19 January 2018 16:17:21 UTC, RobertCNelson wrote:
>
> On Fri, Jan 19, 2018 at 5:45 AM, Hugh Frater  > wrote: 
> >>> 
> >> Running: 
> >> 
> >> sudo apt update ; sudo apt install bb-cape-overlays 
> >> 
> >> Has fixed the eqep errors and the clash between p9_26 and p8_24 that I 
> was 
> >> seeing - however, pru_ecap has now gone as a mode for p9_42 - 
> argggh 
> > 
> > 
> > I see from the most recent commit that this has been added back again as 
> a 
> > mux option Robert, any idea when it will be pushed up and available 
> through 
> > apt update? 
>
> Hi Hugh, 
>
> Yeah after your message yesterday, i went thru the overlays and 
> regenerated with *.dts/pinmux.. 
>
> I'll have a full update for the kernel/config-pin/etc shortly 
>
> (plus gpio_input option will be available).. 
>
> 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/8047deb5-a5b3-42bc-b550-e38fb34ad843%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: More pimux woes

[Robert Nelson]

On Fri, Jan 19, 2018 at 5:45 AM, Hugh Frater  wrote:
>>>
>> Running:
>>
>> sudo apt update ; sudo apt install bb-cape-overlays
>>
>> Has fixed the eqep errors and the clash between p9_26 and p8_24 that I was
>> seeing - however, pru_ecap has now gone as a mode for p9_42 - argggh
>
>
> I see from the most recent commit that this has been added back again as a
> mux option Robert, any idea when it will be pushed up and available through
> apt update?

Hi Hugh,

Yeah after your message yesterday, i went thru the overlays and
regenerated with *.dts/pinmux..

I'll have a full update for the kernel/config-pin/etc shortly

(plus gpio_input option will be available)..

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/CAOCHtYg0umVu10RBtTjM0fu49W4ZX%3DcOw0OT%3D-2ZQOLsWn%2BnFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: X15 Boot via USB

['Roger Quadros' via BeagleBoard]

Hi Angel,

On 18/01/18 06:09, Angel Sosa wrote:
> On Tuesday, January 16, 2018 at 11:51:57 AM UTC-5, marc bellazzini wrote:
>> Hello Angel, 
>> Mine is still collecting dust after my failed attempt at booting off the 
>> eSATA and making the modifications you have also done. Very disappointing 
>> since it was an expensive purchase. I am also awaiting a solution. The 
>> directions on booting from eSATA were not very clear. 
>>
>>
>> Good luck!
>>
>>
>> On Mon, Jan 15, 2018 at 2:07 PM, Angel Sosa  wrote:
>>
>>
>>
>> Hi Everyone,
>>
>>
>>
>>  I am new to the X15. I have an XM since it came out and have done many 
>> projects with it. I have recently purchased and X15. My desire is to 
>> boot from a SATA drive connected to the ESATA port. I have verified when
>>  booted from the MMC card the SATA drive is bootable, can mount and it 
>> works well. I imaged the SATA drive with the X15 image, In my case SDA1 
>>  is the first partition created. I have removed R444 and placed a jumper
>>  I believe what is J3 pins 1-2 and have left the R444 resister solder 
>> points/mounts empty. When I try to boot off of the SATA drive the board 
>> times out and powers down. The instructions are  a little vague on the 
>> on instructions with in the user manual. I had a similar problem when 
>> the partition was enlarged on the MMC card to 32 gigs, the boot process 
>> would timeout. I used the grow_partition.sh script which fixed the time 
>> out issue with the MMC card. If I hold the X15 board orienting J3, J4,J6
>>  at the upper right corner hand corner, And join pins 1-2 -- most left 
>> hole moving right towards the center  pin, there orientation is 
>> horizontal I believe. The board as I mention powers up and then times 
>> out and shuts down. I have tried with the MMC in and out no avail. I 
>> have also purchased two boards at a pretty steep price and would like to
>>  pass them out to family members with the hopes of purchasing additional
>>  boards. But the ESATA/SATA issue is stopping me and I don't want to 
>> return the second board to DIGIKEY. I cant return the first board well 
>> because I modified it by removing the resistor. 
>>
>>
>>
>> Is the image I used on the SATA drive incorrect or need an adjustment? Are 
>> the PIN orientation as I understand it incorrect.
>>
>>
>>
>> Held the X15 so that the ON switch is the upper left and jumpers are upper 
>> right hand corner. 
>>
>>
>>
>> The drive spins up when I power up the board. So I know the ESATA port is 
>> powering up with the board.
>>
>>           1 2 3
>>
>> | Ethernet   |   | XX0 | J3 Short 1 and 2
>>
>> | Connector|   | 000 | J4
>>
>> |             |   | 000 | J6
>>
>>
>>
>> Drive Manufacturer is the SEAGATE IRON WOLF. 
>>
>>
>>
>> Image:
>>
>> bbx15-debian-9.0-lxqt-armhf-2017-07-02-4gb.img.xz,
>>
>> I have also run ( apt-get -y update && and apt-get -y upgrade )
>>
>>
>>
>>
>>
>> Can you please help? Is there an alternate way of booting off of the ESATA 
>> port
>>
>>
>>
>> Thanks in advance 
>>
>>
>>
>> Angel
>>
>>
>>
>>
>>
>> On Thursday, September 28, 2017 at 10:54:51 AM UTC-4, mab.mo...@gmail.com 
>> wrote:
>> Hello,
>>
>> I just purchased an X15 and the EMMC memory is rapidly filling up. 
>>
>> 1. Is there a way to boot from an external USB hard drive?
>> or 
>> 2. Can someone provide more detail directions on switching boot sequence to 
>> boot directly from eSATA?
>> The reference manual is very vague on this. You need to unsolder and 
>> resolder resistors to act as jumpers? There are perforated holes in the 
>> circuit board where the resistors and jumpers are supposed to be. Are the 
>> resistors supplied? Are they on the board? If so where are they? What are 
>> their values in Ohms? How are the perforations on the board numbered 1-3 
>> from left to right or right to left? This needs to be much more detailed. 
>> Why would you design a board that make switching the boot sequence so 
>> difficult? How about just putting in some removable jumpers!
>>
>> Any detailed help and direction would be appreciated. 
>>
>> Thanks
>>
>> MAB
>>
>>
>>
>>
>>
>> -- 
>>
>> 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/xPYp2vR6TDk/unsubscribe.
>>
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/6e58bd35-d1d8-4027-a5f8-23bd76edf60e%40googlegroups.com.
>>
>>
>>
>> For more options, visit https://groups.google.com/d/optout.
> 
> Hi Marc,
>  One other detail, The SATA/ESATA is powered with an external power supply. 
>  The ESATA port is not providing power to the drive itself. And in addition 
> since I de-soldered R444 and added the 

Re: [beagleboard] Using two analog inputs and occurs distortion on the measure

[evilwulfie]

Ain3 has a maximum input voltage of 1.8v
the lm35 is being powered from a +5v supply
your going to need to do something a bit different with the output of
the LM35 so you dont damage the adc input.

On 1/19/2018 6:17 AM, Mateus Lucas wrote:
> Oh, sorry. I have sent the wrong image.
> Thanks for your attention.
>
>
>
> 2018-01-19 9:49 GMT-03:00 evilwulfie  >:
>
> Would love to try to help but even when i saved your schematic
> picture and enlarged it
> i was unable to make out anything in it.
>
> On 1/18/2018 8:34 PM, mateuslucas.l7...@gmail.com
>  wrote:
>>
>>
>>
>> I'm using two analog inputs, the first with a LDR and a resistor
>> of 10k Ohm, connected at P9_39 (AIN0), and the second connected
>> at P9_38 (AIN3).
>> When the lights are down, the measure of LM35 works very well,
>> with a low distorction, +/- 0.2 ºC.
>> But when the lights are on, the measure of LM35 starts to float,
>> about +/- 1 ºC.
>> I have tried to put a 4.7nF between GNDA_ADC and AIN3, but the
>> distorction continues.
>>
>> I asking for help to diminish this distorction when the lights
>> are on.
>>
>> -- 
>> 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/d5353977-2025-4aa3-b6a0-361742ae9c96%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout
>> .
>
>
>
>
> -- 
> Mateus Lucas de Campos e Silva
> Técnico em Eletrônica pelo IFPB - Campus João Pessoa
> Bacharelando em Engenharia Elétrica pelo IFPB
> Celular: (83) 988335074

-- 
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/da7477ba-2546-009c-65f1-d799a088cec1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Can I use GPIO pin that is not provide PWM mode for PWM?

[TJF]

Toggling a GPIO pin by ARM software is very limited.

There're 19 pins at the board for hardware PWM output, 13 of them can work 
simultanously:

| Pin   | Subsystem   | Frequency Range| Notice|
| - | :-: | :- | : |
| P8_07 | TIMER-4 | 0.10914 to 6e6 Hz  | free  |
| P8_09 | TIMER-5 | 0.10914 to 6e6 Hz  | free  |
| P8_10 | TIMER-6 | 0.10914 to 6e6 Hz  | free  |
| P8_08 | TIMER-7 | 0.10914 to 6e6 Hz  | free  |
| P8_13 | PWMSS-2, PWM B  | 0.42 to 50e6 Hz| free  |
| P8_19 | PWMSS-2, PWM A  | 0.42 to 50e6 Hz| free  |
| P9_14 | PWMSS-1, PWM A  | 0.42 to 50e6 Hz| free  |
| P9_16 | PWMSS-1, PWM B  | 0.42 to 50e6 Hz| free  |
| P9_21 | PWMSS-0, PWM B  | 0.42 to 50e6 Hz| free  |
| P9_22 | PWMSS-0, PWM A  | 0.42 to 50e6 Hz| free  |
| P8_34 | PWMSS-1, PWM B  | 0.42 to 50e6 Hz| HDMI  |
| P8_36 | PWMSS-1, PWM A  | 0.42 to 50e6 Hz| HDMI  |
| P8_45 | PWMSS-2, PWM B  | 0.42 to 50e6 Hz| HDMI  |
| P8_46 | PWMSS-2, PWM A  | 0.42 to 50e6 Hz| HDMI  |
| P9_29 | PWMSS-0, PWM B  | 0.42 to 50e6 Hz| MCASP0|
| P9_31 | PWMSS-0, PWM A  | 0.42 to 50e6 Hz| MCASP0|
| P9_28 | PWMSS-2, CAP| 0.0233 to 50e6 Hz  | MCASP0|
| P9_42 | PWMSS-0, CAP| 0.0233 to 50e6 Hz  | free (double pin) |
| JT_05 | PWMSS-1, PRUCAP | 0.0233 to 50e6 Hz  | JTag (UART0_TXD)  |

If those are not enough, you can use direct PRU pins to generate PWM. When 
both PRUSS are used, up to 24 PWM outputs are possible (ie. 
https://github.com/omcaree/bbb-prupwm).

BR

-- 
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/31d05321-30a3-414d-841f-d707db817b21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to connect to wifi with beagle bone blue running ubuntu Bionic ?

[SHYAM SRINIVASAN]

Hello guys , I am relatively new to beagle bone platform and Linux. This 
board shipped with debian in which I was able to connect to wifi. However 
when I boot from an SD card using Ubuntu I am not able to connect to wifi. 
ifconfig doesn't work always returns invalid argument . if I use connmanctl 
it says no command found. I am really stuck in this can anyone help?

-- 
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/a052509e-ae7e-4887-b0f3-99d439c37f1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to SSH to my beagle bone blue running ubuntu ?

[SHYAM SRINIVASAN]

I am able to SSH to my beagle bone blue running debian , but when I boot 
from SD with Ubuntu I am not able to establish an SSH connection

-- 
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/86bd22b3-07a2-4f30-89a5-aa960bc0213d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: More pimux woes

[Hugh Frater]

>
>
>> Running:
>
> sudo apt update ; sudo apt install bb-cape-overlays
>
> Has fixed the eqep errors and the clash between p9_26 and p8_24 that I was 
> seeing - however, pru_ecap has now gone as a mode for p9_42 - argggh
>

I see from the most recent commit that this has been added back again as a 
mux option Robert, any idea when it will be pushed up and available through 
apt update?

 

-- 
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/e8fc5f86-3620-4968-94fa-dd8b1615059b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.