[beagleboard] Re: Is it possible to make work the BBB C program code without installing any operating systems?

[soul . est . soul . est]

There is a baremetal BeagleBone project 
here: http://www.baremetal.tech/index.html

On Thursday, November 16, 2017 at 10:12:38 PM UTC-5, AVR wrote:
>
> Thank you Graham, I completely forgot that I also need and exchange data 
> on TCP/IP... in that case is it possible to realize programmatically TCP/IP 
> without OS ?
>
> четверг, 16 ноября 2017 г., 20:20:30 UTC+5 пользователь Graham написал:
>>
>> Yes, it is possible.
>> Also, probably extremely painful learning experience.
>> There are ARM processors that are designed to run with OS.  They start 
>> with the letter A.
>> The processor in the Beaglebone is an A-8.
>> There are ARM processors that are designed to run without OS. They start 
>> with the letter M.
>>
>> I would suggest that you look at one of the faster M series, like a 200 
>> MHz M4F and see it that will do your job.
>>
>> --- Graham
>>
>> ==
>>
>> On Wednesday, November 15, 2017 at 9:40:05 PM UTC-6, AVR wrote:
>>>
>>> In other words I'd like to make work the BeagleBone Black on the base C 
>>> program code without any operating systems. 
>>> My task is simple enough - frequency meter 0...100 KHz, DI/DO simple 
>>> logic and data exchange accross TCP/IP.
>>>
>>

-- 
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/73d519f4-21fd-419e-93bb-4a35a1e8a748%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Is it possible to make work the BBB C program code without installing any operating systems?

['AVR' via BeagleBoard]

Thank you Graham, I completely forgot that I also need and exchange data on 
TCP/IP... in that case is it possible to realize programmatically TCP/IP 
without OS ?

четверг, 16 ноября 2017 г., 20:20:30 UTC+5 пользователь Graham написал:
>
> Yes, it is possible.
> Also, probably extremely painful learning experience.
> There are ARM processors that are designed to run with OS.  They start 
> with the letter A.
> The processor in the Beaglebone is an A-8.
> There are ARM processors that are designed to run without OS. They start 
> with the letter M.
>
> I would suggest that you look at one of the faster M series, like a 200 
> MHz M4F and see it that will do your job.
>
> --- Graham
>
> ==
>
> On Wednesday, November 15, 2017 at 9:40:05 PM UTC-6, AVR wrote:
>>
>> In other words I'd like to make work the BeagleBone Black on the base C 
>> program code without any operating systems. 
>> My task is simple enough - frequency meter 0...100 KHz, DI/DO simple 
>> logic and data exchange accross TCP/IP.
>>
>

-- 
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/e7ab3b9f-a40a-474b-9bb1-a7445ab361a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unable to get WiFi working on BBBW using the latest Debian image

[lucien]

Chiming in, this combined with updating to the latest provided release of 
debian stretch fixed the wireless issues.
> GND TP1 then run as root: 

```
dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom 
```

My /opt/scripts/tools/version.sh after applying the fix for posterity:

git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]
eeprom:[A335BNLTBWA5BBWG*]
dogtag:[BeagleBoard.org Debian Image 2017-08-31]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
2017.09-rc2-2-g7c9353]
kernel:[4.9.45-ti-r57]
nodejs:[v6.11.2]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]
pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

Thank you!

On Thursday, October 5, 2017 at 9:37:42 AM UTC-4, RobertCNelson wrote:
>
> On Thu, Oct 5, 2017 at 7:12 AM, Hamza Khan  > wrote: 
> > 
> > Hey All, 
> > 
> > I'm a newb on Linux and having issues getting WiFi to work using the 
> latest 
> > Debain image Debian 9.1 2017-08-31 4GB SD LXQT (Stretch). When I try to 
> see 
> > the the network interfaces using ifconfig I get only the following 4 and 
> no 
> > wlan- 
> > 
> > eth0: flags=-28669  mtu 1500 
> > 
> > lo: flags=73  mtu 65536 
> > 
> > usb0: flags=4163  mtu 1500 
> > 
> > usb1: flags=4099  mtu 1500 
> > 
> > I don't know if this will help but the eprom from my version.sh file is 
> - 
> > 
> > eprom:[A335BNLTBBWG0491 
>
> another case of mis-programed: 
>
> GND TP1 then run as root: 
>
> dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
> of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom 
>
> reboot and everything will be okay.. 
>
> 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/26ecd21b-eda1-49fa-be53-1e3a98c94968%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Hello and Getting Ideas Ready for Posting/Seth

[Mala Dies]

Hello...when you are right, you are right. I just typed in the same search 
words. It was second like you stated. I had a bunch of elinux sites but 
that specific post you showed me was second. Thank you again, sir.

Seth

P.S. What have you been doing w/ your BBB lately?

On Thursday, November 16, 2017 at 7:14:07 PM UTC-6, Dennis Lee Bieber wrote:
>
> On Thu, 16 Nov 2017 13:44:45 -0800 (PST), Mala Dies 
> > declaimed the following: 
>
> >Hello, 
> > 
> >Sir, I do not know where you got that info. but thank you. It worked like 
> a 
>
> Simple Google search for 
>
> fritzing beaglebone black 
>
> and it came up as the second entry (first if you ignore the [AD] from 
> Mouser) 
> -- 
> Wulfraed Dennis Lee Bieber AF6VN 
> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.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/cb9fba7a-7fd4-4e9b-bdb4-8eaf45799bfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: PocketBeagle USB1 Question

[Graham]

Your first connection does not work, because you are trying to power the 
USB1 from the USB_VIN, but since the is no power going into USB_VIN on 
USB-0, there is no power to come out USB-1.
This only works when the board is powered from USB-0
The schematic does not tell you, but USB_VIN, USB0_VIN and USB1_VIN are all 
connected together.

VIN is a totally separate power supply input

Since you are powering the board from VIN (P1-01) you need to hook the 5V 
line on your Micro-USB board to P1-01 and P1-05.

In this case, it will work, although you have no current limit protection 
from a short on the 5V line in a downstream USB device, which is required 
by the USB spec.
So, only plug in USB devices and cables you trust.

I would not power the USB-5V-VBUS from the SYS-VOUT, because SYS-VOUT is 
limited to 0.2 A or so, and many USB devices draw more current than this 
(USB-2 devices are allowed to draw up to 0.9 A)

--- Graham

==

On Thursday, November 16, 2017 at 5:11:52 PM UTC-6, wi...@geomonkey.com 
wrote:
>
> I, too, am wondering about the best way to provide power to the board and 
> to a device connected to USB1 as host. Here is how I learned to hook up a 
> micro-b breakout to USB1 and also how I intend to provide power to the 
> board. The problem is that there is no measured voltage at USB1:
>
>
> 
>
> I was wondering if I could just power the USB1 device from P1_24 SYS VOUT 
> (which does have power when board is supplied by P1_01 SYS VIN) like this:
>
>
> 
> Would it be harmful to do it this way? Are there better ways to accomplish 
> this? Thanks!
>
> -- Will Bain
>
>
> On Sunday, November 5, 2017 at 6:59:39 PM UTC-7, Graham wrote:
>>
>> Further research, looking at the Eagle board and schematic files for the 
>> PB, it appears that USB0.VIN and USB1.VIN are both directly connected to 
>> VIN.USB
>> Which explains why I had no power on my USB1 host port when connected 
>> like the Fritzing diagram, since I am powering from VIN currently.
>>
>> So the question becomes,,,
>> What is the best way to power USB1 VBUS as a host if I don't know in 
>> advance whether the customer application will run from VIN or VIN.USB?
>>
>> --- Graham
>>
>> ==
>>
>> On Sunday, November 5, 2017 at 6:58:06 PM UTC-6, Graham wrote:
>>>
>>> I note that there is a PocketBeagle pin P1-7 named USB1-VIN.
>>>
>>> I don't find any connection on the PB schematic, other than to P1-7.
>>>
>>> It was connected externally in all of the USB1 host discussions and 
>>> Fritzing diagrams.
>>>
>>> The name would imply that it is a way to deliver power to the board when 
>>> USB1 has an external 5 Volt power source.
>>>
>>> I guess the basic question is whether this needs to be used/connected 
>>> when USB1 is functioning as a host.
>>>
>>> --- Graham
>>>
>>> ==
>>>
>>

-- 
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/baf74ece-3868-41d8-a46b-abc93678a101%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UART4 RS485 (RTS) not working

[Jeff Andich]

I'm fairly confident the answer to my question about whether the  8250 
driver implements "partial 485 capability", (allowing Python or a C#/.net 
application to manually control the RTS line for a given UART via the 
driver) is NO.  But the OMAP driver DOES appear to allow this.

When I toggle the serial driver defines in kernel 4.4.y's defconfig file ( 
see below),  re-build the kernel, and deploy to my target (along with the 
device tree which couples a given GPIO on my custom board to UART5)  I'm 
only able to toggle the RTS line from within Python (to enable/disable the 
485 chip's transmit)  when I open the /dev/ttyO4 device in Python, but not 
with the /dev/ttyS4 device.

Additionally, the device tree containing the fragment below appears to be 
successfully coupling gpio5_8 and UART5, so this appears to be a driver 
issue rather than a device tree user error issue.


I built the RCN 4.4.y kernel both ways: 

In paches/defconfig:

(1) {CONFIG_SERIAL_8250_OMAP=n,  CONFIG_SERIAL_OMAP=y}
(2) {CONFIG_SERIAL_8250_OMAP=y,  CONFIG_SERIAL_OMAP=n} 

*** Also worth noting is I lost my serial console until I enabled, 
CONFIG_SERIAL_OMAP_CONSOLE=y ***

Ironically enough, my current build (built using configuration (1) above) 
appears to have BOTH the OMAP and 8250 devices which isn't what I would 
expect.. I've only tried writing to /dev/ttyO4 at this point.  There maybe 
some other defines which need to be changed in the defconfig to switch off 
the 8250, named serial device files in the /dev/ directory.  Film at 11 on 
that one..


**
Listing of serial devices with kernel 4.4.y built with configuration (1)
**

debian@BeagleBoard-X15:~$ ls -l /dev/ttyO*
crw-rw 1 root   dialout 248, 0 Nov 16 19:28 /dev/ttyO0
crw--- 1 debian tty 248, 2 Nov 16 19:28 /dev/ttyO2
crw-rw 1 root   dialout 248, 4 Nov 16 19:28 /dev/ttyO4
crw-rw 1 root   dialout 248, 7 Nov 16 19:28 /dev/ttyO7

debian@BeagleBoard-X15:~$ ls -l /dev/ttyS*
crw-rw 1 root dialout 4, 64 Nov 16 19:28 /dev/ttyS0
crw-rw 1 root dialout 4, 65 Nov 16 19:28 /dev/ttyS1
crw-rw 1 root dialout 4, 66 Nov 16 19:28 /dev/ttyS2
crw-rw 1 root dialout 4, 67 Nov 16 19:28 /dev/ttyS3
crw-rw 1 root dialout 4, 68 Nov 16 19:28 /dev/ttyS4
crw-rw 1 root dialout 4, 69 Nov 16 19:28 /dev/ttyS5


*
Python snippet and brief description of test results
*
ser = serial.Serial('/devlttyO4')
ser.ctsrts = False
ser.write(b'I wish the BeagleBone folks would produce a pocket Beagle with 
an am5728')

I see Tx data from my 2 wire 485 chip on the scope.

ser.ctsrts = True
I see nothing from my 2 wire 485 chip on the scope.


***
Build Configuration
***
Started from the console build for BB-X15 with debian 8.9 on elinux Robert 
referred me to a few weeks ago.
Followed the instructions on eewiki for rebuilding BB-X15 kernel, but 
checked out branch origin/4.4.y, and built kernel using build_kernel.sh.
 
debian@BeagleBoard-X15:~$ uname -r
4.4.83-ti-r119
debian@BeagleBoard-X15:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2017-10-02
debian@BeagleBoard-X15:~$ 

Regards and thanks!

Jeff


On Tuesday, November 14, 2017 at 6:44:22 PM UTC-6, Jeff Andich wrote:
>
> Hi,
>
> Will the 8250 driver still allow "manual" control of the RTS line for a 
> given UART from an application like Python or C# (where the application 
> toggles the state of the RTS line, rather than driver, after sending a 
> request message in order to toggle the 485 XCVR), or is the OMAP driver (in 
> place of the 8250 driver) needed for this as well?
>
> I've attempted to associate the RTS line for UART5 with GPIO5_8 (which is 
> connected to the DE toggle on a 485 chip) via the device tree (kernel 
> 4.4.y), followed by calling setRTS(True/False) from Python, but that 
> doesn't appear to be switching the 485 XCVR.  However, I can still use 
> sysfs commands to toggle the GPIO5_8 connected to the 485 chip to control 
> the direction of transmission.
>
> In order to help differentiate between an incorrect device tree 
> configuration vs. needing to recompile the kernel with the OMAP  driver 
> instead of the 8250 driver, I'm wondering if you know whether the 8250 
> driver will support what we're trying here. Everything I've read (including 
> https://groups.google.com/forum/#!msg/beagleboard/nMtRpdWSJu0/EDSXqGpiBAAJ) 
> seems to suggest that the 8250 doesn't yet handle toggling the RTS/CTS 
> lines on its own based on delays between characters, but I haven't seen 
> anything about manual control.
>
>
> Following is a snippet/fragment from my device tree. ***LATE  
> DISCLOSURE*** From UART5_8, you can see that this is for the BB-X15, but I 
> believe the same issue pertains to both the BBB and the BB-X15: 
>
> &uart5 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart5_pins>;
> status = "okay";
> rts-gpio = <&gpio5 8 GPIO_ACTIVE_HIGH>;
> rs485-rts-active-high;
>   

[beagleboard] Re: PocketBeagle USB1 Question

[will]

I, too, am wondering about the best way to provide power to the board and 
to a device connected to USB1 as host. Here is how I learned to hook up a 
micro-b breakout to USB1 and also how I intend to provide power to the 
board. The problem is that there is no measured voltage at USB1:



I was wondering if I could just power the USB1 device from P1_24 SYS VOUT 
(which does have power when board is supplied by P1_01 SYS VIN) like this:


Would it be harmful to do it this way? Are there better ways to accomplish 
this? Thanks!

-- Will Bain


On Sunday, November 5, 2017 at 6:59:39 PM UTC-7, Graham wrote:
>
> Further research, looking at the Eagle board and schematic files for the 
> PB, it appears that USB0.VIN and USB1.VIN are both directly connected to 
> VIN.USB
> Which explains why I had no power on my USB1 host port when connected like 
> the Fritzing diagram, since I am powering from VIN currently.
>
> So the question becomes,,,
> What is the best way to power USB1 VBUS as a host if I don't know in 
> advance whether the customer application will run from VIN or VIN.USB?
>
> --- Graham
>
> ==
>
> On Sunday, November 5, 2017 at 6:58:06 PM UTC-6, Graham wrote:
>>
>> I note that there is a PocketBeagle pin P1-7 named USB1-VIN.
>>
>> I don't find any connection on the PB schematic, other than to P1-7.
>>
>> It was connected externally in all of the USB1 host discussions and 
>> Fritzing diagrams.
>>
>> The name would imply that it is a way to deliver power to the board when 
>> USB1 has an external 5 Volt power source.
>>
>> I guess the basic question is whether this needs to be used/connected 
>> when USB1 is functioning as a host.
>>
>> --- Graham
>>
>> ==
>>
>

-- 
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/0af0e0fc-ea86-45bc-8885-9ed6b3e789be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Is it possible to make work the BBB C program code without installing any operating systems?

[briselec]

TI StarterWare  is 
what you want 

-- 
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/5e9de538-a5b4-46d8-8b5b-638390b22f29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Booting from eMMC issue

[radagastearendil]

It can be trusted. Does not matter whether one pushes RST (reset) button or 
plugs in power as long as SD card is in first and then SD button is held 
down and only after this power it up.
Make sure to use BBBL images (not BBB like I at first did ;-)) and be 
patient when botting, i.e. it will show a cylon effect after some time of 
heartbeat flashing. When finished all blue LEDs will be either fully on 
indicating error I guess (at least it was like this for me) or all will be 
100% off ready to remove SD card and boot up.

-- 
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/229efa9c-24db-4ab8-9bf2-1df14d819a97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Possible for Beaglebone Blue to support a non-wireless Ethernet connection?

[n feehan]

Hi, I'm looking at buying the Beaglebone Blue, after prototyping with the 
Beaglebone Black. I'm making this change because my application needs 
hardware support for four quadrature encoders and not three.

However, my application streams this encoder data as fast as possible over 
UDP as an OSC message - when I use a wireless connection anywhere in my OSC 
path, I see the data rate reduce drastically, to the point where it's not 
suitable for my application.

My questions are:
* Does the Beaglebone Green support four quadrature encoder channels?
* Is there a way to get wired Ethernet (ie, cat5 cable) out of the 
Beaglebone Blue?

Thanks for any help / info you may be able to provide!

AKA

-- 
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/ce56e36c-3732-4a36-a8f7-6fbc5c98caef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Hello and Getting Ideas Ready for Posting/Seth

[Mala Dies]

Hello,

Sir, I do not know where you got that info. but thank you. It worked like a 
charm. B/c of my OrCad version (Lite), I cannot handle large files. Anyway, 
thank you very much.

Seth

P.S. If you need anything, let me know. 

On Wednesday, November 15, 2017 at 11:45:32 PM UTC-6, Dennis Lee Bieber 
wrote:
>
> On Wed, 15 Nov 2017 16:45:34 -0800 (PST), Mala Dies 
> > declaimed the following: 
>
>
> > 
> >   - I cannot find out how to get the BBB photo to get it integrated into 
> >   OrCad or Fritzing. 
> >   - I tried OrCad Lite and the .brd file that is available. There is no 
> >   photo alongside the .brd file. 
> >   - Also, I tried to find some .pdf files or .svg files for Fritzing to 
> >   use the "schematic" of the BBB to make small works. 
>
> Based upon an early version... try: 
>
> https://github.com/adafruit/Fritzing-Library/blob/master/parts/BeagleBone%20Black.fzpz
>  
> -- 
> Wulfraed Dennis Lee Bieber AF6VN 
> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.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/17fbcd69-0178-44be-b062-4e1f7e837292%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Is it possible to make work the BBB C program code without installing any operating systems?

[Graham]

The one I was thinking of was the Freescale/NXP   Kenitis K66 series.
180 MHz, ARM M4F
(I guess not 200 MHz, but close.)
Available on a maker board as the Teensy 3.6  
https://www.sparkfun.com/products/14057

Ti, NXP, Stm, may also have fast M4F, but it would take some digging.

Microchip has PIC32MZ, 200  MHz, but is MIPS4 rather than ARM M4F.

--- Graham

==

On Thursday, November 16, 2017 at 10:48:50 AM UTC-6, Dennis Lee Bieber 
wrote:
>
> On Thu, 16 Nov 2017 07:20:30 -0800 (PST), Graham 
> > declaimed the following: 
>
> >Yes, it is possible. 
> >There are ARM processors that are designed to run without OS. They start 
> >with the letter M. 
> > 
> >I would suggest that you look at one of the faster M series, like a 200 
> MHz 
> >M4F and see it that will do your job. 
> > 
> >--- Graham 
> > 
> >== 
> > 
> >On Wednesday, November 15, 2017 at 9:40:05 PM UTC-6, AVR wrote: 
> >> 
> >> In other words I'd like to make work the BeagleBone Black on the base C 
> >> program code without any operating systems. 
> >> My task is simple enough - frequency meter 0...100 KHz, DI/DO simple 
> logic 
> >> and data exchange accross TCP/IP. 
> >> 
>
> Haven't found a reference for one at that speed, but possibly of 
> interest would be the TIVA-C Launchpads: The TM4C123G (80MHz M4F, 256kB 
> Flash, 32kB RAM, and way too many timers [6@64bit, 6@32bit -- each of 
> which 
> can be configured as two half-width timers]); TM4C1294 (120MHz M4F, 1MB 
> Flash, 256kB RAM, Ethernet, fewer timers [8@32bit, likely also splitable]; 
> the TM4C129E is identical but adds some HW crypto support]). Supported by 
> TI Code Composer Studio, and TI-RTOS for tasking. 
> -- 
> Wulfraed Dennis Lee Bieber AF6VN 
> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.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/7b83470d-67b9-4d00-ba09-7277a631d18e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Using PRU with PocketBeagle: remoteproc problems

[Ken Shirriff]

Alex, thank you for such a detailed response. Your answer solved all my 
problems.

Ken

On Tuesday, November 14, 2017 at 3:58:12 PM UTC-8, Alex Bagehot wrote:
>
> Hi Ken,
> Having recently also bought a pocket beagle(my first), I ran through these 
> steps from Jason, as he suggested in another thread recently, successfully 
> : https://gist.github.com/jadonk/2ecf864e1b3f250bad82c0eae12b7b64
> I thought it would be instructive to work out how to run the example you 
> tried also though. Basically taking the working gist and resolving issues 
> with your example as they appear.
> Resulting in:
>
> Received 100 messages, closing /dev/rpmsg_pru31
> ie. success. It did a thing.
> Thanks,
> Alex
>
> On Tue, Nov 14, 2017 at 7:10 AM, Ken Shirriff  > wrote:
>
>> I got a PocketBeagle and I want to try out the PRU on it. Everything 
>> seems different from the PRUSSDRV stuff I'm used to. I can't get remoteproc 
>> to work, so I wanted to know which kernel and interfaces I should use.
>>
>> Specifically, I'm running the 2017-10-10 Stretch IoT build from 
>> http://beagleboard.org/latest-images
>>
> Yep. which is:
>
> *debian@beaglebone*:*~/hello*$ uname -a
>
> Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
> GNU/Linux
>  
>
>> I tried running the remoteproc "Hello world" from here 
>> .
>> First, I ran into problems with stdint.h not found; I eventually found it 
>> in /usr/share/ti/cgt-pru/include - is that the right include path to use?
>>
> Yes based on the gist.
>
> I also got some linking errors:
>
> /usr/bin/clpru -z hello.cmd -o /home/debian/hello/pru0/am335x-pru0-fw 
> /home/debian/hello/pru0//main0.object 
> -l/usr/lib/ti/pru-software-support-package/lib/rpmsg_lib.lib
> 
> warning: automatic RTS selection:  attempt to automatically link in index
>library "libc.a" failed; file not found
> warning: entry-point symbol "_c_int00" undefined
> warning: no suitable entry-point found; setting to 0
>
> Adding in another include based on the gist fixed them.
>
> /usr/bin/clpru -z hello.cmd -i/usr/share/ti/cgt-pru/lib -o 
> /home/debian/hello/pru1/am335x-pru1-fw 
> /home/debian/hello/pru1//main1.object 
> -l/usr/lib/ti/pru-software-support-package/lib/rpmsg_lib.lib
> 
>
>
> Now built it needs to be deployed:
>
> Initially I got an error deploying to pru1 as I just changed 4a334000.pru0 
> to 4a334000.pru1.
> It wasn't hard to find the right ID:
>
> debian@beaglebone:~/hello$ grep pru1 /var/log/messages |head -1
> Oct 10 12:07:05 beaglebone kernel: [   11.700167]  remoteproc1: 
> 4a338000.pru1 is available
>
> With this in hand I just wrote a quick sudoable script :
>
> debian@beaglebone:~/hello$ cat a.sh 
> set -x
> dmesg --clear
> echo "4a334000.pru0" > /sys/bus/platform/drivers/pru-rproc/unbind
> echo "4a334000.pru0" > /sys/bus/platform/drivers/pru-rproc/bind
> echo "4a338000.pru1" > /sys/bus/platform/drivers/pru-rproc/unbind
> echo "4a338000.pru1" > /sys/bus/platform/drivers/pru-rproc/bind
>
> Which produced:
>
>
> debian@beaglebone:~/hello$ sudo ./a.sh && dmesg
> + dmesg --clear
> + echo 4a334000.pru0
> + echo 4a334000.pru0
> + echo 4a338000.pru1
> + echo 4a338000.pru1
> [ 7750.734933] pru-rproc 4a334000.pru0: pru_rproc_remove: removing rproc 
> 4a334000.pru0
> [ 7750.744148] ti-pruss 4a30.pruss: unconfigured system_events = 
> 0x0003 host_intr = 0x0005
> [ 7750.744179]  remoteproc2: stopped remote processor 4a334000.pru0
> [ 7750.744387]  remoteproc2: releasing 4a334000.pru0
> [ 7750.751046]  remoteproc2: 4a334000.pru0 is available
> [ 7750.751076]  remoteproc2: Note: remoteproc is still under development 
> and considered experimental.
> [ 7750.751085]  remoteproc2: THE BINARY FORMAT IS NOT YET FINALIZED, and 
> backward compatibility isn't yet guaranteed.
> [ 7750.755059]  remoteproc2: powering up 4a334000.pru0
> [ 7750.755101]  remoteproc2: Booting fw image am335x-pru0-fw, size 73588
> [ 7750.755362] ti-pruss 4a30.pruss: configured system_events = 
> 0x0003 intr_channels = 0x0005 host_intr = 0x0005
> [ 7750.761686]  remoteproc2: remote processor 4a334000.pru0 is now up
> [ 7750.762068] virtio_rpmsg_bus virtio0: rpmsg host is online
> [ 7750.762127] virtio_rpmsg_bus virtio0: creating channel rpmsg-pru addr 
> 0x1e
> [ 7750.763089] rpmsg_pru rpmsg5: new rpmsg_pru device: /dev/rpmsg_pru30
> [ 7750.763232]  remoteproc2: registered virtio0 (type 7)
> [ 7750.763325] pru-rproc 4a334000.pru0: PRU rproc node 
> /ocp/pruss@4a30/pru0@4a334000 probed successfully
> [ 7750.767206] pru-rproc 4a338000.pru1: pru_rproc_remove: removing rproc 
> 4a338000.pru1
> [ 7750.767237] pru-rproc 4a338000.pru1: stopping the manually booted PRU 
> core
> [ 7750.767353] ti-pruss 4a30.pruss: unconfigured system_events = 
> 0x host_intr = 0x0001
> [ 7750.767368]  remoteproc1: stopped remote processor 4a338000.pru1
> [ 7750.767476]  remoteproc1: releasing 4a338000.pru1
> [ 7750.774260]  remoteproc1: 4a338000

Re: [beagleboard] Re: MySQL on Beaglebone Black

[Robert Nelson]

On Thu, Nov 16, 2017 at 12:29 PM, Paul Van den Bergh  wrote:

> Finaly, I was able to connect to the MySql server on the remote Beaglebone
> :
>
>
>
> However, I get this warning re compatibility of the server:
>
>
>
> So, my next question is how to remove the installed version (installed by
> 'apt-get install mysql-server mysql-client' on the Beaglebone) and install
> the official MySQL distribution?
>


You don't, well in Debian 9.x Stretch.

https://mariadb.com/about-us/newsroom/press-releases/mariadb-replaces-mysql-default-debian-9

You downgrade to Debian 8.x Jessie, or build it yourself...

With Debian 9.x (stretch), the developers transitioned from MySQL ->
MariaDB.  While "corporate" Oracle may not agree with that move, hence
"their" tool see's it as incompatible. Most distro's have dropped MySQL
like solid waste, and replaced it with MariaDB...

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

Re: [beagleboard] Beagleboard XM boot hangs on kernel 3.14.20

[michel . he]

https://groups.google.com/forum/?fromgroups=#!topic/beagleboard/FqaaSUd37VY
https://groups.google.com/forum/#!topic/beagleboard/8Xw9XXNsQQ0
https://groups.google.com/forum/#!topic/beagleboard/1H99Vig16-Q

2017-11-16 8:51 GMT+01:00 MHE 何海宇 :

> Maybe you should use an old beagleboard rootfs that doesn't need to start
> all systemd default services. Btw, afaik this kernel 3.4.20 doesn't handle
> usb, ethernet, framebuffer, it seems some patches were missing.
> I tried several kernel, but all failed..
> Try to get some issues solved by xM community here in google forum
>
> --
> 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/HlvbIbqDBLA/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/b7b3064a-1d00-4f86-86ee-81e49a82ac71%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/CACOKaTpLZ7yoormQtg1VjH-NapEkbYPdA41q8KdGxi2Kibi5Wg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Weird behaviour with pins and PRUs

[TJF]

Am Donnerstag, 16. November 2017 16:16:15 UTC+1 schrieb Loïc Droz:
>
> I could yes, but I read somewhere (can't remember where exactly, but it 
> was in some TI PowerPoint presentation that reading the eCAP register takes 
> at least 4 cycles, which is not ideal for my purposes.
>

Read or write access from PRU to the PRU internal eCAP module takes exactly 
one cycle. You can find this information in the PRU TRM.

Please don't confuse other readers.

-- 
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/444f37db-7576-4abf-9ea3-45de1a0924ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Is it possible to make work the BBB C program code without installing any operating systems?

[Graham]

Yes, it is possible.
Also, probably extremely painful learning experience.
There are ARM processors that are designed to run with OS.  They start with 
the letter A.
The processor in the Beaglebone is an A-8.
There are ARM processors that are designed to run without OS. They start 
with the letter M.

I would suggest that you look at one of the faster M series, like a 200 MHz 
M4F and see it that will do your job.

--- Graham

==

On Wednesday, November 15, 2017 at 9:40:05 PM UTC-6, AVR wrote:
>
> In other words I'd like to make work the BeagleBone Black on the base C 
> program code without any operating systems. 
> My task is simple enough - frequency meter 0...100 KHz, DI/DO simple logic 
> and data exchange accross TCP/IP.
>

-- 
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/adc5be5d-1ecd-4868-be44-eb5dd51703d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Weird behaviour with pins and PRUs

[Loïc Droz]

I could yes, but I read somewhere (can't remember where exactly, but it was 
in some TI PowerPoint presentation that reading the eCAP register takes at 
least 4 cycles, which is not ideal for my purposes. In the meantime I found 
a way to use the BBB built in PWM as a CLK signal and it works now. Check 
this link 
 if 
you're interested. Thanks for your help nonetheless.

Le jeudi 9 novembre 2017 16:08:16 UTC+1, TJF a écrit :
>
>
>
> Am Donnerstag, 9. November 2017 14:00:37 UTC+1 schrieb Loïc Droz:
>>
>> I could also do both operations on one PRU yes. However, since the audio 
>> processing steps involve memory writes to the host, I am worried these 
>> might not take deterministic time, which would prevent my clock my clock 
>> from being stable.
>>
>
> On one PRU, you could use the PRU internal eCAP subsystem to generate the 
> CLK output. Synchronize your software by reading back the eCAP counter.
>
> 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/73a403da-8322-46f1-8488-9d5114d02602%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: MySQL on Beaglebone Black

[Tarmo Kuuse]

On Thursday, 16 November 2017 16:27:47 UTC+2, Paul Van den Bergh wrote:
>
> My prevous post was shortened while posting
>
> 4.  I see no firewall roules:
>
> root@beaglebone:~# iptables -L -n -v 
>
> Chain INPUT (policy ACCEPT 2959 packets, 304K bytes) 
>
>  pkts bytes target prot opt in out source   
> destination 
>   
>   
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) 
>
>  pkts bytes target prot opt in out source   
> destination 
>   
>   
> Chain OUTPUT (policy ACCEPT 478 packets, 42627 bytes) 
>   
>  pkts bytes target prot opt in out source   
> destination 
>
> I'll examine the logs in the hope to find the problem.  Thanks for your 
> valuable input !
>
> Regards,
> Paul
>
>
> Op donderdag 16 november 2017 15:22:57 UTC+1 schreef Paul Van den Bergh:
>>
>> Hi Tarmo,
>>
>> 1. since I can ssh into the BBB, it's the exact IP address:
>>
>> paul@debian-9-2-1-64:~$ ssh root@192.168.1.52
>> Last login: Tue Oct 10 14:07:21 2017 from 192.168.1.13
>> root@beaglebone:~# ifconfig
>> eth0: flags=-28605  mtu 1500
>> inet *192.168.1.52*  netmask 255.255.255.0  broadcast 192.168.
>> 1.255
>> inet6 fe80::d239:72ff:fe17:eaae  prefixlen 64  scopeid 0x20
>> ether d0:39:72:17:ea:ae  txqueuelen 1000  (Ethernet)
>> RX packets 7335  bytes 663521 (647.9 KiB)
>> RX errors 0  dropped 1751  overruns 0  frame 0
>> TX packets 582  bytes 54176 (52.9 KiB)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> device interrupt 174  
>>   
>>   
>> lo: flags=73  mtu 65536 
>>
>> inet 127.0.0.1  netmask 255.0.0.0   
>> 
>> inet6 ::1  prefixlen 128  scopeid 0x10 
>>
>> loop  txqueuelen 1  (Local Loopback) 
>>
>> RX packets 160  bytes 12960 (12.6 KiB)   
>>
>> RX errors 0  dropped 0  overruns 0  frame 0 
>> 
>> TX packets 160  bytes 12960 (12.6 KiB)   
>>
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0   
>>
>>   
>>   
>> usb0: flags=4099  mtu 1500   
>>
>> inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3 
>>
>> ether d0:39:72:17:ea:b0  txqueuelen 1000  (Ethernet) 
>>
>> RX packets 0  bytes 0 (0.0 B)   
>> 
>> RX errors 0  dropped 0  overruns 0  frame 0 
>> 
>> TX packets 0  bytes 0 (0.0 B)   
>> 
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0   
>>
>>   
>>   
>> usb1: flags=4099  mtu 1500   
>>
>> inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3 
>>
>> ether d0:39:72:17:ea:b3  txqueuelen 1000  (Ethernet) 
>>
>> RX packets 0  bytes 0 (0.0 B)   
>> 
>> RX errors 0  dropped 0  overruns 0  frame 0 
>> 
>> TX packets 0  bytes 0 (0.0 B)   
>> 
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0   
>>
>>   
>>   
>>
>> 2.  mysql is running: (another problem is setting up the time server on 
>> the BBB ;) )
>>
>> root@beaglebone:~# systemctl status mysql   
>> 
>> ● mariadb.service - MariaDB database server 
>> 
>>Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor 
>> preset: enabled)
>>Active: active (running) since Tue 2017-10-10 14:07:21 CEST; 4h 52min 
>> ago
>>   Process: 909 ExecStartPost=/bin/sh -c systemctl unset-environment 
>> _WSREP_START_POSITIO
>>   Process: 900 ExecStartPost=/etc/mysql/debian-start (code

Re: [beagleboard] Re: MySQL on Beaglebone Black

[Alex Bagehot]

Hi Paul,

Usually I stop the service that is being installed or has issues to remove
it form the equation and test the network connectivity first.

stop mysql
install netcat if needed
run netcat listening on port 3306
  sudo nc -l 3306
check that it is indeed being listened on in another terminal:
  netstat -nat |grep LISTEN|grep 3306
or
  ss -nat |grep LISTEN|grep 3306

test connectivity locally first !!
  telnet ... blah
test connectivity remotely
   telnet ... blah

If you can connect locally but not remotely then there is some
firewall/other network issue.
If you can connect remotely then your issue is in the service you
originally wanted to test/ install

Googling though for "maria db 3306 connection refused" suggests another
check: have you enabled remote access?
eg.
https://mariadb.com/kb/en/library/configuring-mariadb-for-remote-client-access/
In your original email we don't see bind-address in your config or other
remote access config.

thanks,
Alex


On Thu, Nov 16, 2017 at 2:27 PM, Paul Van den Bergh 
wrote:

> My prevous post was shortened while posting
>
> 4.  I see no firewall roules:
>
> root@beaglebone:~# iptables -L -n -v
>
> Chain INPUT (policy ACCEPT 2959 packets, 304K bytes)
>
>  pkts bytes target prot opt in out source
> destination
>
>
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
>
>  pkts bytes target prot opt in out source
> destination
>
>
> Chain OUTPUT (policy ACCEPT 478 packets, 42627 bytes)
>
>  pkts bytes target prot opt in out source
> destination
>
> I'll examine the logs in the hope to find the problem.  Thanks for your
> valuable input !
>
> Regards,
> Paul
>
>
> Op donderdag 16 november 2017 15:22:57 UTC+1 schreef Paul Van den Bergh:
>>
>> Hi Tarmo,
>>
>> 1. since I can ssh into the BBB, it's the exact IP address:
>>
>> paul@debian-9-2-1-64:~$ ssh root@192.168.1.52
>> Last login: Tue Oct 10 14:07:21 2017 from 192.168.1.13
>> root@beaglebone:~# ifconfig
>> eth0: flags=-28605  mtu 1500
>> inet *192.168.1.52*  netmask 255.255.255.0  broadcast 192.168.
>> 1.255
>> inet6 fe80::d239:72ff:fe17:eaae  prefixlen 64  scopeid 0x20
>> ether d0:39:72:17:ea:ae  txqueuelen 1000  (Ethernet)
>> RX packets 7335  bytes 663521 (647.9 KiB)
>> RX errors 0  dropped 1751  overruns 0  frame 0
>> TX packets 582  bytes 54176 (52.9 KiB)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> device interrupt 174
>>
>>
>> lo: flags=73  mtu 65536
>>
>> inet 127.0.0.1  netmask 255.0.0.0
>>
>> inet6 ::1  prefixlen 128  scopeid 0x10
>>
>> loop  txqueuelen 1  (Local Loopback)
>>
>> RX packets 160  bytes 12960 (12.6 KiB)
>>
>> RX errors 0  dropped 0  overruns 0  frame 0
>>
>> TX packets 160  bytes 12960 (12.6 KiB)
>>
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>>
>>
>> usb0: flags=4099  mtu 1500
>>
>> inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
>>
>> ether d0:39:72:17:ea:b0  txqueuelen 1000  (Ethernet)
>>
>> RX packets 0  bytes 0 (0.0 B)
>>
>> RX errors 0  dropped 0  overruns 0  frame 0
>>
>> TX packets 0  bytes 0 (0.0 B)
>>
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>>
>>
>> usb1: flags=4099  mtu 1500
>>
>> inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3
>>
>> ether d0:39:72:17:ea:b3  txqueuelen 1000  (Ethernet)
>>
>> RX packets 0  bytes 0 (0.0 B)
>>
>> RX errors 0  dropped 0  overruns 0  frame 0
>>
>> TX packets 0  bytes 0 (0.0 B)
>>
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>>
>>
>>
>> 2.  mysql is running: (another problem is setting up the time server on
>> the BBB ;) )
>>
>> root@beaglebone:~# systemctl status mysql
>>
>> ● mariadb.service - MariaDB database server
>>
>>Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor
>> preset: enabled)
>>Active: active (running) since Tue 2017-10-10 14:07:21 CEST; 4h 52min
>> ago
>>   Process: 909 ExecStartPost=/bin/sh -c systemctl unset-environment
>> _WSREP_START_POSITIO
>>   Process: 900 ExecStartPost=/etc/mysql/debian-start (code=exited, status
>> =0/SUCCESS)
>>   Process: 598 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ]
>> && VAR= ||   VA
>>   Process: 573 ExecStartPre=/bin/sh -c systemctl unset-environment
>> _WSREP_START_POSITION
>>   Process: 540 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /
>> var/run/mysqld
>>  Main PID: 812 (mysqld)
>>
>>Status: "Taking your SQL requests now..."
>>
>> Tasks: 26>
>
> --
> 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 vi

[beagleboard] Re: BeagleBone Green wont boot if cape connected

[Paulo Sherring]

Thanks, Graham. You are correct. I have already used these pins before, but 
for output purposes, so, I had no issues with that. But, since using as 
inputs, the switches are driving the pins and changing the SYSBOOT (aka 
LCDDATA) bus, which I had no idea that existed for my unfortunate surprise. 
I guess I'll have to redesign my boards including a tristate buffer.

Paulo Sherring.

Em quarta-feira, 15 de novembro de 2017 16:59:03 UTC-3, Graham escreveu:
>
> You have apparently used two pins that conflict with the boot 
> configuration pins on the BBB, or the eMMC.
>
> Read the "BeagleBone Black System Reference Manual" (Version C.1), pages 
> 62, 63, 68, 82, 106, 107.
>
> --- Graham
>
> ==
>
> On Wednesday, November 15, 2017 at 1:48:34 PM UTC-6, Paulo Sherring wrote:
>>
>> Hi, all. I have a beaglebone green connected to a custom cape. I am 
>> running the latest machinekit image.
>> I have it all configured and runs mostly OK. I am having an issue with 
>> end switch circuitry.
>> The switched are connected to P8_41 and P8_42 and are connected through 
>> the circuit in the attachment (BJT with open collector, connected through 
>> load resistor and internal pullup). If the end switch is opened, the board 
>> wont boot at all. If the end switch is closed, the board boots without any 
>> further issue. 
>> My question is: is there any blocking mechanism that prevents CPU from 
>> booting if, for example, any input is driver high?
>>
>> Thanks in advance!
>> Paulo Sherring.
>>
>

-- 
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/bd8bf279-556e-45e6-acf8-defd206c60ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] IOError: [Errno 13] Permission denied

[Robert Nelson]

Yeah I think TI assumed the user would be root with those dlp scripts.  I
need to double check them and fix that..

On Nov 15, 2017 2:40 PM, "Przemek Klosowski" 
wrote:

> It looks like your software is trying to write to
> /opt/scripts/device/bone/capes/DLPDLCR2000/0524/tmp_header_Video Play
> Test__Tue__Nov_14_2017__11_19_37__.xls
> but you don't have permissions to that location. Can you confirm that, and
> do you know how to address that problem? I'm asking because I don't know
> how much do you know, so I'm not sure what advice to give.
>
> On Wed, Nov 15, 2017 at 12:04 PM,  wrote:
>
>> Hello,
>>
>> I am trying to play video using Beaglebone black and DLPDLCR2000EVM
>>  projector.
>>
>> I can play video manually but when I try to play videos using python
>> script I am getting an error like this
>>
>> debian@beaglebone:/opt/scripts/device/bone/capes/DLPDLCR2000$ python
>> MplayerTest.py
>>
>> Traceback (most recent call last):
>> File "MplayerTest.py", line 89, in 
>> main()
>> File "MplayerTest.py", line 59, in main
>> datalog = DataLog(LogDir, Test_name)
>> File "build/bdist.linux-armv7l/egg/dlp_lightcrafter/datalog.py", line
>> 77, in __init__
>> IOError: [Errno 13] Permission denied: '0524/tmp_header_Video Play
>> Test__Tue__Nov_14_2017__11_19_37__.xls'
>>
>>
>> the system isn't being allowed to write to the datalog file.
>>
>> any one please help me to fix this problem.
>>
>> thank you.
>>
>> --
>> 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/ms
>> gid/beagleboard/9681b811-a796-4c62-af23-492c8e26ae84%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/CAC%3D1GgH4LahivKLOOKROmJ%3DDZ5vC_
> bV4kQ%3DwtN19SGT_uNx%2B9w%40mail.gmail.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/CAOCHtYjWzCtz%2B89jyXvUJyfadS7bQQ-8tFvjoYOgEAHhvnYC_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Green's HDMI cape with 2016-04-10 Jessi firmware

[Robert Nelson]

Yeah Seeed ported it to v4.4.x.

It needs someone to write and push a real DRM driver to mainline. ( The
chipset used is also on a few rockchip boards. )

Regards,

On Nov 16, 2017 6:34 AM,  wrote:

> Its almost 2018... this cape still doesn't work.
>
> "zcat /proc/config.gz | grep CONFIG_BONE_CAPEMGR" >>reports>>
> "CONFIG_BONE_CAPEMGR=y" Latest OS fully up to date:
> bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img
>
> On Thursday, April 14, 2016 at 7:34:16 AM UTC-7, RobertCNelson wrote:
>>
>>
>>
>> On Thu, Apr 14, 2016 at 9:16 AM, Aitor Ardanza  wrote:
>>
>>> Hi all,
>>>
>>> I'm trying to operate the Seeds Studio HDMI cape into the BeagleBone
>>> Green with last firmware. The LCD screen that I'm using is a 5" size and
>>> 800x480 resolution touch screen. I know that this resolution is not
>>> supported directly by the beaglebone but as I read is posible to configure
>>> beaglebone's out resolution manualy. But that's a problem that I will
>>> later. The screen works because if I connet it to the laptop I can see the
>>> laptop desktop there.
>>>
>>> So with newly installed firmware the output of the "cat
>>> /sys/devices/platform/bone_capemgr/slots" command is
>>>  0: PF  -1
>>>  1: PF  -1
>>>  2: PF  -1
>>>  3: P-  -1 Beaglebone green hdmi cape,00A0,Seeed,BB-GREEN-HDMI
>>>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,univ-emmc
>>>
>>> So with this, I can interpret this firmware brings support for this
>>> cape, but is not loaded for some reason...
>>> I try editing the /boot/uEnv.tx file adding
>>> "cape_enable=bone_capemgr.enable_partno=BB-GREEN-HDMI" line but it has
>>> not been effective.
>>>
>>> I found multiple threads with information to disable the hdmi in
>>> beaglebone, but nothing about how to activate the hdmi cape. SeedStudio
>>> gives you a firmware but is out of date and I want to try to configure it
>>> for the last firmaware.
>>>
>>> Can anyone give me some tip as to which way to go?
>>>
>>
>> For this cape, you'll need to downgrade to 3.8.x:
>>
>> sudo apt-get update
>> sudo apt-get install linux-image-3.8.13-bone79
>> sudo reboot
>>
>> I haven't got it working on v4.1.x yet..
>>
>> 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/652fd222-dff5-426e-8017-9237bfd2aedd%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/CAOCHtYhMwxH1hgJX2oy%2BxGA8K%2BmLmpFTT%2Bz_jB6oZtzx-220Lw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Connection to Beaglebone blue

[radagastearendil]

Same here.
First BBBlue died from either a spark when connecting barrel plug (from now 
on I only plug in the AC side) or emmc emptied from a magnetic XBee  being 
pulled across the wifi card it got attracted to accidentally.

2nd first worked then same heartbeat LED came on (no more red, yellow 
lights) and no more hotspot to connect to. From now I never plug in a 
second Wifi interface. Or it was the SSH connection that got interrupted. 
Difficult to tell

-- 
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/ab0ab8b2-d0d6-43a8-8aff-f25c9f02931e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Green's HDMI cape with 2016-04-10 Jessi firmware

[zezba9000]

Its almost 2018... this cape still doesn't work.

"zcat /proc/config.gz | grep CONFIG_BONE_CAPEMGR" >>reports>> 
"CONFIG_BONE_CAPEMGR=y" Latest OS fully up to date: 
bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img

On Thursday, April 14, 2016 at 7:34:16 AM UTC-7, RobertCNelson wrote:
>
>
>
> On Thu, Apr 14, 2016 at 9:16 AM, Aitor Ardanza  > wrote:
>
>> Hi all,
>>
>> I'm trying to operate the Seeds Studio HDMI cape into the BeagleBone 
>> Green with last firmware. The LCD screen that I'm using is a 5" size and 
>> 800x480 resolution touch screen. I know that this resolution is not 
>> supported directly by the beaglebone but as I read is posible to configure 
>> beaglebone's out resolution manualy. But that's a problem that I will 
>> later. The screen works because if I connet it to the laptop I can see the 
>> laptop desktop there.
>>
>> So with newly installed firmware the output of the "cat 
>> /sys/devices/platform/bone_capemgr/slots" command is
>>  0: PF  -1 
>>  1: PF  -1 
>>  2: PF  -1 
>>  3: P-  -1 Beaglebone green hdmi cape,00A0,Seeed,BB-GREEN-HDMI
>>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,univ-emmc
>>
>> So with this, I can interpret this firmware brings support for this cape, 
>> but is not loaded for some reason...
>> I try editing the /boot/uEnv.tx file adding 
>> "cape_enable=bone_capemgr.enable_partno=BB-GREEN-HDMI" line but it has not 
>> been effective.
>>
>> I found multiple threads with information to disable the hdmi in 
>> beaglebone, but nothing about how to activate the hdmi cape. SeedStudio 
>> gives you a firmware but is out of date and I want to try to configure it 
>> for the last firmaware.
>>
>> Can anyone give me some tip as to which way to go?
>>
>
> For this cape, you'll need to downgrade to 3.8.x:
>
> sudo apt-get update
> sudo apt-get install linux-image-3.8.13-bone79
> sudo reboot
>
> I haven't got it working on v4.1.x yet..
>
> 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/652fd222-dff5-426e-8017-9237bfd2aedd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: MySQL on Beaglebone Black

[Tarmo Kuuse]

On Thursday, 16 November 2017 11:25:13 UTC+2, Paul Van den Bergh wrote:
>
> Same with telnet (from Debian in VirtualBox) :
>
> paul@debian-9-2-1-64:~$ telnet 192.168.1.52 3306
> Trying 192.168.1.52...
> telnet: Unable to connect to remote host: Connection refused
>
>
>
>
Then you can proceed to further debugging your setup. Some suggestions:

1. Verify that the IP you're connecting to is the IP of the Beaglebone 
("ifconfig" on BB)
2. Verify that mysql service is running on the Beaglebone ("systemctl 
status mysql" on BB)
3. Verify that mysql is accepting connections on port 3306 from external 
hosts (no idea, refer to the docs)
4. Verify that there aren't any firewall rules to block traffic ("sudo 
iptables -L -n -v" on BB)
5. Go through the mysql logs for any failures (/var/log/mysql.*)

--
Kind regards,
Tarmo Kuuse

-- 
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/9626234a-b650-4f97-9644-2ca7b2266ad3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] SPI on Linux version 4.4.0-72-generic

[Reshmi Chandran]

Hi ,
I downloaded the latest prebuilt image Debian 9.1 2017-08-31 4GB SD LXQT 
.
 
I want to connect a SPI device.
I could see 4 devices 
spidev1.0
spidev1.1
spidev2.0
spidev2.1

but slot does not show any spi entry
root@beaglebone:/sys/devices/platform/bone_capemgr# cat slots 
 0: --  -1 
 1: ---l--  -1 
 2: ---l--  -1 
 3: ---l--  -1 
root@beaglebone:/sys/devices/platform/bone_capemgr# 


pinctrl shows spi enbaled


cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pingroups| grep spi


group: pinmux_P9_42_spics_pin
group: pinmux_P9_42_spiclk_pin
group: pinmux_P9_30_spi_pin
group: pinmux_P9_22_spi_pin
group: pinmux_P9_21_spi_pin
group: pinmux_P9_18_spi_pin
group: pinmux_P9_17_spi_pin
root@beaglebone:/sys/devices/platform/bone_capemgr# 


I loaded the spidev module.But spidev_test did not  pass.
Please help. Am I missing out something.


-- 
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/28881384-504b-41f9-a2df-c08edcc7cbad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.