Re: [beagleboard] recipe to make the RTC on BBB work

[Harke Smits]

Robert, following all of your advise: it works. Thanks a lot! I have
installed rtc's on about 7 BBB's the last 5 years and it always was a
challenge. Mainly because the procedure changed a lot. In addition, I
added an rtc service and the Beagle now shows the right time even when not
connected to the internet. I still feel a newbie, though.
Thanks again, best regards,
Harke


On Wed, 5 Feb 2020 at 20:50, Robert Nelson  wrote:

> On Wed, Feb 5, 2020 at 1:40 PM Harke Smits  wrote:
> >
> > Thanks Robert for your attention. I replaced the line in uEnv.txt and it
> indeed installs the rtc. But it also uninstalled my display (4D Systems),
> so I outcommented it.
> > This is what I see with the line as recommended active:
> >
> > debian@beaglebone:~$ ls -al /dev/rtc*
> > lrwxrwxrwx 1 root root  4 Feb  5 16:20 /dev/rtc -> rtc1
> > crw--- 1 root root 252, 0 Feb  5 16:20 /dev/rtc0
> > crw--- 1 root root 252, 1 Feb  5 16:46 /dev/rtc1
> > debian@beaglebone:~$ sudo nano /boot/uEnv.txt---> line outcommented
> >
> >
> > After reboot:
> >
> > debian@beaglebone:~$ ls -al /dev/rtc*
> > lrwxrwxrwx 1 root root  4 Nov  3  2016 /dev/rtc -> rtc0
> > crw--- 1 root root 252, 0 Nov  3  2016 /dev/rtc0
>
> Okay, so use addr4->7:
>
> uboot_overlay_addr0=/lib/firmware/BB-I2C2-RTC-DS1307.dtbo
> ->
> uboot_overlay_addr4=/lib/firmware/BB-I2C2-RTC-DS1307.dtbo
>
> as addr0->addr3 also map to cape, so if you have an lcd plugged in
> they can conflict..
>
>
> > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> > git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
> > eeprom:[A335BNLT00C02916BBBK1556]
> > model:[TI_AM335x_BeagleBone_Black]
> > dogtag:[BeagleBoard.org Debian Image 2018-10-07]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2018.09-2-g0b54a51eee]:[location: dd MBR]
>
> That's too old..
>
> sudo /opt/scripts/tools/developers/update_bootloader.sh
>
> > kernel:[4.14.71-ti-r80]
> > nodejs:[v6.14.4]
> > uboot_overlay_options:[enable_uboot_overlays=1]
> >
> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
> > uboot_overlay_options:[enable_uboot_cape_universal=1]
> > uboot_overlay_options:[dtb_overlay=/lib/firmware/BB-RTC-02-00A0.dtbo]
> > pkg check: to individually upgrade run: [sudo apt install --only-upgrade
> ]
> > pkg:[bb-cape-overlays]:[4.4.20181106.0-0rcnee0~stretch+20181110]
>
> That's too old..
>
> sudo apt update ; sudo apt install --only-upgrade bb-cape-overlays
>
> > pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
> > pkg:[kmod]:[23-2rcnee1~stretch+20171005]
> > pkg:[librobotcontrol]:[1.0.4-git20181108.0-0rcnee0~stretch+20181110]
> > pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
> > groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
> plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep
> admin spi tisdk weston-launch xenomai]
> > cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
> root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait
> uboot_detected_capes=BB-BONE-LCD4-01, coherent_pool=1M net.ifnames=0 quiet]
> > dmesg | grep pinctrl-single
> > [1.134653] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800
> size 568
> > dmesg | grep gpio-of-helper
> > [1.146518] gpio-of-helper ocp:cape-universal: ready
> > END
> > debian@beaglebone:~$
>
> 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/CAHmciaaKzFXi%2BfUq2sSwAWQP0Cuw0rt%2Bt5WdTAbnU0qnarufOw%40mail.gmail.com.

Re: [beagleboard] recipe to make the RTC on BBB work

[Harke Smits]

Thanks Robert for your attention. I replaced the line in uEnv.txt and it 
indeed installs the rtc. But it also uninstalled my display (4D Systems), 
so I outcommented it.
This is what I see with the line as recommended active:

debian@beaglebone:~$ ls -al /dev/rtc*
lrwxrwxrwx 1 root root  4 Feb  5 16:20 /dev/rtc -> rtc1
crw--- 1 root root 252, 0 Feb  5 16:20 /dev/rtc0
crw--- 1 root root 252, 1 Feb  5 16:46 /dev/rtc1
debian@beaglebone:~$ sudo nano /boot/uEnv.txt---> line outcommented


After reboot:

debian@beaglebone:~$ ls -al /dev/rtc*
lrwxrwxrwx 1 root root  4 Nov  3  2016 /dev/rtc -> rtc0
crw--- 1 root root 252, 0 Nov  3  2016 /dev/rtc0

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
eeprom:[A335BNLT00C02916BBBK1556]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
2018.09-2-g0b54a51eee]:[location: dd MBR]
kernel:[4.14.71-ti-r80]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
uboot_overlay_options:[dtb_overlay=/lib/firmware/BB-RTC-02-00A0.dtbo]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
]
pkg:[bb-cape-overlays]:[4.4.20181106.0-0rcnee0~stretch+20181110]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20181108.0-0rcnee0~stretch+20181110]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep 
admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait 
uboot_detected_capes=BB-BONE-LCD4-01, coherent_pool=1M net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[1.134653] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 
568
dmesg | grep gpio-of-helper
[1.146518] gpio-of-helper ocp:cape-universal: ready
END
debian@beaglebone:~$

Please advise.
Best regards,
Harke



On Wednesday, 5 February 2020 16:01:39 UTC+1, RobertCNelson wrote:
>
> On Wed, Feb 5, 2020 at 8:39 AM Harke Smits > 
> wrote: 
> > 
> > Hello, 
> > 
> > Is there a recipe that works to install the RTC (DS3231/1307)? I googled 
> and tried a lot of things but can not make it work. I succeeded on older 
> Debian versions but now I am lost. 
> > I have Debian 2018-10-07. The hw works as proved by i2cdetect -y -r 2. 
> At address 0x68. "echo ds1307 0x68 
> >/sys/class/i2c-adapter/i2c-2/new_device" gives: permission denied. 
> > Looks like I need to do something with overlay files? But uEnv.txt does 
> not need to be modified, right? ls -al /dev/rtc*: only gives two entries 
> for rtc0. 
> > Please help. 
>
> Which DS* device? we have an overlay for both devices.. 
>
> So assuming DS1307 and i2c2: 
>
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-I2C2-RTC-DS1307.dts
>  
>
> uboot_overlay_addr0=/lib/firmware/BB-I2C2-RTC-DS1307.dtbo 
>
> and this swaps the Beagle RTC0 with this one, so normal linux tools 
> will use the DS1307 as rtc0 
>
> If it doesn't work, please run and report: 
>
> sudo /opt/scripts/tools/version.sh 
>
> So we can see what's "old" with your setup.. 
>
> 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/89cf7781-94f4-47db-bee5-6e94ed3d46e6%40googlegroups.com.

[beagleboard] recipe to make the RTC on BBB work

[Harke Smits]

Hello,

Is there a recipe that works to install the RTC (DS3231/1307)? I googled 
and tried a lot of things but can not make it work. I succeeded on older 
Debian versions but now I am lost.
I have Debian 2018-10-07. The hw works as proved by i2cdetect -y -r 2. At 
address 0x68. "echo ds1307 0x68 >/sys/class/i2c-adapter/i2c-2/new_device" 
gives: permission denied.
Looks like I need to do something with overlay files? But uEnv.txt does not 
need to be modified, right? ls -al /dev/rtc*: only gives two entries for 
rtc0.
Please help.
Many thanks in advance,
Harke

 

-- 
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/a26e99be-1c89-4bf9-bfb0-5d9188b23500%40googlegroups.com.

Re: [beagleboard] Re: LXQT autostart problem

[Harke Smits]

Hello Seth, and others interested,

Yes the .service file for the rtc works fine.
But my LXQT Autostart problem is getting strange. I have three versions of
basically the same Python script. V 3.6: using digital  I/O bits. V4.6 and
V5.6 use two pwm bits as well. And guess what: only V3.6 starts
automatically (on the same system) via Autostart. I can manually start the
other versions without any errors whatsoever. I tried different pwm pins,
no success. On another system v4.6 starts in autostart.

Its really puzzling. And taking a lot of time.
Will resume later unless you have a brilliant idea?
Best regards,
Harke




On Sun, 10 Feb 2019 at 18:41, Mala Dies  wrote:

> Yea. Harke,
>
> Hello...I think you need to update the entire image if you want to work w/
> a fixed/new bugs in the kernel. Anyway:
> https://wiki.qt.io/BeagleBone_Black_Beginners_Guide. That guide is
> something I found locally on this wiki/group.
>
> Seth
>
> P.S. I know that you are having trouble w/ the .service file for starting
> services on boot w/ QT. Do you have your .service file or a rendition?
>
> On Sunday, February 10, 2019 at 7:41:47 AM UTC-6, Harke Smits wrote:
>>
>> Hi Seth,
>>
>> Yes, the autorun problem is still there.
>> Going from old Debian releases to the latest one (9.5) gave me a couple
>> of surprises. My Python application proved to be portable but a lot needed
>> to be modified. One was the repacement of i2c-1 by i2c-2, while i2c-1 was
>> no longer accessible, by default. It took a while to understand what was
>> going on. I opened a topic elsewhere on this site but no response. Then
>> I applied the latest Adafruit rtc recipe (adapted for i2c-2!) and could
>> make the rtc work, in a way. I even managed to make a rtc installation
>> service work! Though the learning curve is steep at times, I am still no
>> expert and I doubt that the i2c issues has an influence on the aurorun
>> problem.
>> I am not familiar with .profile entries.
>> Thanks (again) for your efforts, Seth!
>> Cheers,
>> H
>>
>> On Sun, 10 Feb 2019 at 06:30, Mala Dies  wrote:
>>
>>> What about the .profile entries?
>>>
>>> Seth
>>>
>>> On Tuesday, February 5, 2019 at 3:41:10 AM UTC-6, Harke Smits wrote:
>>>>
>>>> Hello,
>>>>
>>>> I have a strange LXQT autostart problem. I have 4 BBB's all running the
>>>> latest image (Debian 9.5). My python application runs fine on all of them
>>>> (from QTerminal). On two of these systems I can make LXQT-Autostart my
>>>> application work (LXQT settings-Session settings-Application Autostart,
>>>> under LXQT Autostart). On the other two nothing runs automatically.  The
>>>> .desktop files are all the same, their names as well. I tried everything I
>>>> could think of, I even re-installed the image. No luck. This already took
>>>> me days. Please help  me out or give me a pointer where to look.
>>>> Thanks a lot.
>>>> Harke  .
>>>>
>>> --
>>> 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/SdeWndpLKck/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/8727de25-7917-4293-aab0-5d83112cabf4%40googlegroups.com
>>> <https://groups.google.com/d/msgid/beagleboard/8727de25-7917-4293-aab0-5d83112cabf4%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/SdeWndpLKck/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/2ec5e916-0da2-4836-9e24-c4c4b29cf094%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/2ec5e916-0da2-4836-9e24-c4c4b29cf094%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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/CAHmciaY1V5HSsir_r%3DyPZXy7%3Dxvd7kXR9VNt0oDgtZ1zfn0cWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: LXQT autostart problem

[Harke Smits]

Hi Seth,

Yes, the autorun problem is still there.
Going from old Debian releases to the latest one (9.5) gave me a couple of
surprises. My Python application proved to be portable but a lot needed to
be modified. One was the repacement of i2c-1 by i2c-2, while i2c-1 was no
longer accessible, by default. It took a while to understand what was going
on. I opened a topic elsewhere on this site but no response. Then I
applied the latest Adafruit rtc recipe (adapted for i2c-2!) and could make
the rtc work, in a way. I even managed to make a rtc installation service
work! Though the learning curve is steep at times, I am still no expert and
I doubt that the i2c issues has an influence on the aurorun problem.
I am not familiar with .profile entries.
Thanks (again) for your efforts, Seth!
Cheers,
H

On Sun, 10 Feb 2019 at 06:30, Mala Dies  wrote:

> What about the .profile entries?
>
> Seth
>
> On Tuesday, February 5, 2019 at 3:41:10 AM UTC-6, Harke Smits wrote:
>>
>> Hello,
>>
>> I have a strange LXQT autostart problem. I have 4 BBB's all running the
>> latest image (Debian 9.5). My python application runs fine on all of them
>> (from QTerminal). On two of these systems I can make LXQT-Autostart my
>> application work (LXQT settings-Session settings-Application Autostart,
>> under LXQT Autostart). On the other two nothing runs automatically.  The
>> .desktop files are all the same, their names as well. I tried everything I
>> could think of, I even re-installed the image. No luck. This already took
>> me days. Please help  me out or give me a pointer where to look.
>> Thanks a lot.
>> Harke  .
>>
> --
> 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/SdeWndpLKck/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/8727de25-7917-4293-aab0-5d83112cabf4%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/8727de25-7917-4293-aab0-5d83112cabf4%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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/CAHmciabKzTv_6sxCop8ABY9C1L02QjokDZJL5%2BAtGUf9a0Y-CQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: LXQT autostart problem

[Harke Smits]

Hello Seth,

Thanks for coming back to me. I am definitively no expert in this field but
I guess I see what you mean. The dtbo refered to deals with i2c-1. I
assumed as in the past I need i2c-1 to enable the RTC. It turns out not to
be and with respect to my LXQT problem can be ignored, I think. Now I have
the rtc enabled on i2c-2, more or less.. (I hate changing these things
without good docs.). Please correct me if I am wrong.
I guess its something in the LXQT shell that works differently.
Cheers,
H


On Thu, 7 Feb 2019 at 17:34, Mala Dies  wrote:

> Hello Harke,
>
> Seth here. I see that you have a .dtbo file in the BBB that does work.
>
> See line on the broken config. from above:
> uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C1-00A0.dtbo]
>
> If you are messing w/ overlays instead of managing the config-pin utility.
> This may prove valuable.
>
> Seth
>
> P.S. Try adding this device tree blob object file to your boards that do
> not work. If I am correct, the .dtbo file is the only difference in those
> two ./version.sh cmds listed.
>
> On Thursday, February 7, 2019 at 6:52:39 AM UTC-6, Harke Smits wrote:
>>
>> Hello Seth,
>>
>> Thanks for coming back to me, again.
>> All systems work with flashed os. No SD card inserted.
>> This from a non working system:
>>
>> Last login: Thu Feb  7 11:18:52 2019 from
>> 2001:982:c7c1:1:48cb:8340:1675:32fa
>> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
>> [sudo] password for debian:
>> git:/opt/scripts/:[974401727fdcbd58751bd99456a7baa6bd6891a0]
>> eeprom:[A335BNLT00C02916BBBK1556]
>> model:[TI_AM335x_BeagleBone_Black]
>> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
>> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
>> 2018.09-2-g0b54a51eee]:[location: dd MBR]
>> kernel:[4.14.71-ti-r80]
>> nodejs:[v6.14.4]
>> uboot_overlay_options:[enable_uboot_overlays=1]
>> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-
>>   00A0.dtbo]
>> uboot_overlay_options:[enable_uboot_cape_universal=1]
>> pkg check: to individually upgrade run: [sudo apt install --only-upgrade
>> ]
>> pkg:[bb-cape-overlays]:[4.4.20181106.0-0rcnee0~stretch+20181110]
>> pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
>> pkg:[kmod]:[23-2rcnee1~stretch+20171005]
>> pkg:[librobotcontrol]:[1.0.4-git20181108.0-0rcnee0~stretch+20181110]
>> pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
>> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
>> plugdev users systemd-journal i2c bluetooth netdev
>> cloud9ide gpio pwm eqep admin spi tisdk weston-launch
>> xenomai]
>> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
>> root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait
>> uboot_detected_capes=BB-BONE-LCD4-01, coherent_pool=1M
>> net.ifnames=0 quiet]
>> dmesg | grep pinctrl-single
>> [1.130498] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800
>> size 568
>> dmesg | grep gpio-of-helper
>> [1.142379] gpio-of-helper ocp:cape-universal: ready
>> END
>>
>> I did perform the github comand.
>>
>> This is from a working system:
>>
>> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
>> [sudo] password for debian:
>> git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
>> eeprom:[A335BNLT00C00816BBBK0459]
>> model:[TI_AM335x_BeagleBone_Black]
>> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
>> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
>> 2018.09-2-g0b54a51eee]:[location: dd MBR]
>> kernel:[4.14.71-ti-r80]
>> nodejs:[v6.14.4]
>> uboot_overlay_options:[enable_uboot_overlays=1]
>>
>> uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C1-00A0.dtbo]
>>
>> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
>> uboot_overlay_options:[enable_uboot_cape_universal=1]
>> pkg check: to individually upgrade run: [sudo apt install --only-upgrade
>> ]
>> pkg:[bb-cape-overlays]:[4.4.20181120.0-0rcnee0~stretch+20181120]
>> pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
>> pkg:[kmod]:[23-2rcnee1~stretch+20171005]
>> pkg:[librobotcontrol]:[1.0.4-git20181108.0-0rcnee0~stretch+20181110]
>> pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
>> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
>> plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep
>&

Re: [beagleboard] Re: LXQT autostart problem

[Harke Smits]

Hello Seth,

Thanks for coming back to me, again.
All systems work with flashed os. No SD card inserted.
This from a non working system:

Last login: Thu Feb  7 11:18:52 2019 from
2001:982:c7c1:1:48cb:8340:1675:32fa
debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[974401727fdcbd58751bd99456a7baa6bd6891a0]
eeprom:[A335BNLT00C02916BBBK1556]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2018.09-2-g0b54a51eee]:[location: dd MBR]
kernel:[4.14.71-ti-r80]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-
  00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade
]
pkg:[bb-cape-overlays]:[4.4.20181106.0-0rcnee0~stretch+20181110]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20181108.0-0rcnee0~stretch+20181110]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
plugdev users systemd-journal i2c bluetooth netdev
cloud9ide gpio pwm eqep admin spi tisdk weston-launch
xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait
uboot_detected_capes=BB-BONE-LCD4-01, coherent_pool=1M
net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[1.130498] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size
568
dmesg | grep gpio-of-helper
[1.142379] gpio-of-helper ocp:cape-universal: ready
END

I did perform the github comand.

This is from a working system:

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
eeprom:[A335BNLT00C00816BBBK0459]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2018.09-2-g0b54a51eee]:[location: dd MBR]
kernel:[4.14.71-ti-r80]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C1-00A0.dtbo]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade
]
pkg:[bb-cape-overlays]:[4.4.20181120.0-0rcnee0~stretch+20181120]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20181108.0-0rcnee0~stretch+20181110]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep
admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait
uboot_detected_capes=BB-BONE-LCD4-01,BBORG_MOTOR, coherent_pool=1M
net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[1.132913] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size
568
[1.601249] pinctrl-single 44e10800.pinmux: pin PIN19 already requested
by 48302200.pwm; cannot claim for gpio_keys
[1.612024] pinctrl-single 44e10800.pinmux: pin-19 (gpio_keys) status -22
[1.619036] pinctrl-single 44e10800.pinmux: could not request pin 19
(PIN19) from group pinmux_bb_lcd_keymap_pins  on device pinctrl-single
dmesg | grep gpio-of-helper
[1.144987] gpio-of-helper ocp:cape-universal: ready
END
debian@beaglebone:~$

I hope two examples are enough for the diagnosis. A third ystem, working
good, is gone with his owner, who needed it obviously. The systems are not
100% identical, but my knowledge of Debion/BBB is too limited to understand
its implications.
Many thanks in advance,
Harke



On Thu, 7 Feb 2019 at 06:40, Mala Dies  wrote:

>
> Hello,
>
> Seth here, again. Are you running your board(s) w/ SD Card or on the eMMC
> of the BBBs? I know this is happening over and over again but my ideas
> remain the same. Try to, if you are using SD Card, update your eMMC or
> erase the contents of the eMMC.
>
> U-Boot overlays need to be updated. If you are using the eMMC on all the
> BBBs, I will think of something else.
>
> Seth
>
> P.S. Please list the info. from this command: sudo ./version.sh | grep
> bootloader. First apply a *git pull* in /opt/scripts/tools/developers/
> directory. For each board, please reply w/ the version of your bootloader.
> You can label them 1. to 4. w/ the relevant info.
>
>
>
> On T

[beagleboard] LXQT autostart problem

[Harke Smits]

Hello,

I have a strange LXQT autostart problem. I have 4 BBB's all running the 
latest image (Debian 9.5). My python application runs fine on all of them 
(from QTerminal). On two of these systems I can make LXQT-Autostart my 
application work (LXQT settings-Session settings-Application Autostart, 
under LXQT Autostart). On the other two nothing runs automatically.  The 
.desktop files are all the same, their names as well. I tried everything I 
could think of, I even re-installed the image. No luck. This already took 
me days. Please help  me out or give me a pointer where to look.
Thanks a lot.
Harke  . 

-- 
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/2f84d3e9-9e22-4c9d-a34e-beec85a17d95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

WOW! You made my day! This works! I am working about two weeks to get
this going but I was completely at the wrong track!
Thank you so much for your advice.
IOU!
Best regards, enjoy the weekend,
Harke

On Fri, 7 Dec 2018 at 14:04, Tarmo Kuuse  wrote:

> Hi Harke,
>
>
>> No problem, I can do that, in fact I have done that many times with the
 same results. I can enter: cd /home/debian/eme/ and then: python aceme.py
 or I can enter: python /home/debian/eme/aceme.py. That works in both ways
 exactly the same. When run under the bash it gives an error saying that
 Tkinter does not work because of a $Display error. When run under QTerminal
 in LXQT it works fine. This is the reason that I must be sure in the
 service file that the graphics modules are loaded first. In fact this is
 the (only) way to start the application.
 Conclusion: the command line: python /home/debian/eme/aceme.py works
 perfectly. However, this is not what I need to put after: ExecStart (as far
 as I understand). Now I have: ExecStart=/home/debian/eme/aceme.py. And
 I made aceme.py executable.
 I do not know bash scripts so if necessary please help me here.
 I hope this helps in the analysis.

>>>
> Do I understand correctly that your application, which you're trying to
> run on boot, displays a GUI? I strongly suspect systemd cannot launch GUI
> programs. It's meant for daemons which work in the background and don't
> display anything.
>
> Not having done this personally on a Beagle, I'd try to go for something
> like this:
>
> 1. Ensure Beagle starts a graphical environment (LXQT or which ever you
> prefer)
> 2. LXQT automatically logs in with your user and brings up the desktop
> 3. LXQT autostart mechanism triggers your application.
>
> Somebody has written instructions for step 3 here:
> https://wiki.archlinux.org/index.php/LXQt#Autostart
>
> --
> Kind regards,
> Tarmo
>
> --
> 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/goOORlttd2c/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/1b9386b7-9f25-4ed7-b5ac-373a1287bdd6%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/CAHmciaYVTjM4c_A-ghqUMZ9E9Ksa%2Bn0x6zckUr1RkTeiWtCtLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

I am really lost here. I have a working application on the BBB platform
running Debian from a couple of years ago. It was not easy but I got it
completely running, automatically. Now I am trying for two weeks to upgrade
to Debian 9.5 and I find the i2c busses are interchanged and hard to use,
the autorun does not work anymore and it was pretty hard to get a standard
display (4D Systems) working in the first place.
To run automatically an application crontab is the wrong way, that is
clear, so I tried Services. Services are also not working. Is there any
alternative? Do I really waste my time trying to use a BBB?
I was not planning to get a PhD in programming. I am a RF user/amateur
willing to learn, but this is too hard for me.
Sorry if I sound a bit frustrated but this is where I got.
I hope some newer version of Debian will all rectify this.
Anyway, thanks for your time Jim! Many people are willing to help but in
this case it seems without result.
Best regards,
Harke



On Thu, 6 Dec 2018 at 18:48, Jim F  wrote:

> I was actually thinking you should make sure you run the exact same
> python. So if your exec start line says /usr/bin/python2.7 aceme.py then
> you should run that. Then pay attention to the comments about the
> pythonpath in my previous email.
>
> But your other descriptions are not promising. I don't think you should be
> using a systemd service to start an interactive application with a display.
> Usually systemd services are headless. Perhaps I am mistaken there. It
> certainly is not typically used that way.
>
> Jim
>
> On Thu, Dec 6, 2018, 3:57 AM Harke Smits  wrote:
>
>> Hi Jim,
>>
>> No problem, I can do that, in fact I have done that many times with the
>> same results. I can enter: cd /home/debian/eme/ and then: python aceme.py
>> or I can enter: python /home/debian/eme/aceme.py. That works in both ways
>> exactly the same. When run under the bash it gives an error saying that
>> Tkinter does not work because of a $Display error. When run under QTerminal
>> in LXQT it works fine. This is the reason that I must be sure in the
>> service file that the graphics modules are loaded first. In fact this is
>> the (only) way to start the application.
>> Conclusion: the command line: python /home/debian/eme/aceme.py works
>> perfectly. However, this is not what I need to put after: ExecStart (as far
>> as I understand). Now I have: ExecStart=/home/debian/eme/aceme.py. And
>> I made aceme.py executable.
>> I do not know bash scripts so if necessary please help me here.
>> I hope this helps in the analysis.
>> Best regards,
>> Harke
>>
>>
>>
>>
>> On Wed, 5 Dec 2018 at 21:46, Jim F  wrote:
>>
>>> Harke,
>>>
>>> You should try running your script from the cli using the exact same
>>> command you use for the exec start line in your service file. It should
>>> give you the same errors you are seeing. That would be good. If not, the
>>> problem is that your environment doesn't match. It will probably end up
>>> being your PYTHONPATH. In that case you may want to write a short bash
>>> script which sets the path and runs your python script, and using that for
>>> your exec start command.
>>>
>>> Fundamentally your python doesn't know where the libraries you want are
>>> installed. PYTHONPATH is the environment variable which tends python where
>>> to look. Copy the one from your environment and export it in your bash
>>> script.
>>>
>>> Jim
>>>
>>> On Wed, Dec 5, 2018, 2:50 PM Harke Smits  wrote:
>>>
>>>> login as: debian
>>>> debian@Beaglebone's password:
>>>>
>>>> The programs included with the Debian GNU/Linux system are free
>>>> software;
>>>> the exact distribution terms for each program are described in the
>>>> individual files in /usr/share/doc/*/copyright.
>>>>
>>>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>>>> permitted by applicable law.
>>>> Last login: Wed Dec  5 18:01:26 2018 from
>>>> 2001:982:c7c1:1:a96e:5bfc:cb2a:81a7
>>>> debian@beaglebone:~$ sudo systemctl status aceme
>>>> [sudo] password for debian:
>>>> ● aceme.service - to invoke aceme.py automatically
>>>>Loaded: loaded (/etc/systemd/system/aceme.service; enabled; vendor
>>>> preset: enabled)
>>>>Active: failed (Result: exit-code) since Wed 2018-12-05 19:39:44
>>>> UTC; 3min 50s ago
>>>>   Process: 986 ExecStart=/home/debian/eme/acemev35.py (code=exited,
>>>> status=1/FAILURE)
>>

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

Hi Jim,

No problem, I can do that, in fact I have done that many times with the
same results. I can enter: cd /home/debian/eme/ and then: python aceme.py
or I can enter: python /home/debian/eme/aceme.py. That works in both ways
exactly the same. When run under the bash it gives an error saying that
Tkinter does not work because of a $Display error. When run under QTerminal
in LXQT it works fine. This is the reason that I must be sure in the
service file that the graphics modules are loaded first. In fact this is
the (only) way to start the application.
Conclusion: the command line: python /home/debian/eme/aceme.py works
perfectly. However, this is not what I need to put after: ExecStart (as far
as I understand). Now I have: ExecStart=/home/debian/eme/aceme.py. And
I made aceme.py executable.
I do not know bash scripts so if necessary please help me here.
I hope this helps in the analysis.
Best regards,
Harke




On Wed, 5 Dec 2018 at 21:46, Jim F  wrote:

> Harke,
>
> You should try running your script from the cli using the exact same
> command you use for the exec start line in your service file. It should
> give you the same errors you are seeing. That would be good. If not, the
> problem is that your environment doesn't match. It will probably end up
> being your PYTHONPATH. In that case you may want to write a short bash
> script which sets the path and runs your python script, and using that for
> your exec start command.
>
> Fundamentally your python doesn't know where the libraries you want are
> installed. PYTHONPATH is the environment variable which tends python where
> to look. Copy the one from your environment and export it in your bash
> script.
>
> Jim
>
> On Wed, Dec 5, 2018, 2:50 PM Harke Smits  wrote:
>
>> login as: debian
>> debian@Beaglebone's password:
>>
>> The programs included with the Debian GNU/Linux system are free software;
>> the exact distribution terms for each program are described in the
>> individual files in /usr/share/doc/*/copyright.
>>
>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>> permitted by applicable law.
>> Last login: Wed Dec  5 18:01:26 2018 from
>> 2001:982:c7c1:1:a96e:5bfc:cb2a:81a7
>> debian@beaglebone:~$ sudo systemctl status aceme
>> [sudo] password for debian:
>> ● aceme.service - to invoke aceme.py automatically
>>Loaded: loaded (/etc/systemd/system/aceme.service; enabled; vendor
>> preset: enabled)
>>Active: failed (Result: exit-code) since Wed 2018-12-05 19:39:44 UTC;
>> 3min 50s ago
>>   Process: 986 ExecStart=/home/debian/eme/acemev35.py (code=exited,
>> status=1/FAILURE)
>>  Main PID: 986 (code=exited, status=1/FAILURE)
>>
>> Dec 05 19:39:40 beaglebone systemd[1]: Started to invoke aceme.py
>> automatically.
>> Dec 05 19:39:44 beaglebone python[986]: Adafruit_BBIO: version 
>> initialized
>> Dec 05 19:39:44 beaglebone acemev35.py[986]: Traceback (most recent call
>> last):
>> Dec 05 19:39:44 beaglebone acemev35.py[986]:   File
>> "/home/debian/eme/acemev35.py", line 21, in 
>> Dec 05 19:39:44 beaglebone acemev35.py[986]: import serial
>># serial control module
>> Dec 05 19:39:44 beaglebone acemev35.py[986]: ImportError: No module named
>> serial
>> Dec 05 19:39:44 beaglebone systemd[1]: aceme.service: Main process
>> exited, code=exited, status=1/FAILURE
>> Dec 05 19:39:44 beaglebone systemd[1]: aceme.service: Unit entered failed
>> state.
>> Dec 05 19:39:44 beaglebone systemd[1]: aceme.service: Failed with result
>> 'exit-code'.
>> debian@beaglebone:~$
>>
>>
>> here is the status of aceme.service immediately after booting. It is
>> clear that serial is loaded on my system, as I use it extensively in the
>> same program script loaded.
>> login as: debian
>> debian@Beaglebone's password:
>>
>> The programs included with the Debian GNU/Linux system are free software;
>> the exact distribution terms for each program are described in the
>> individual files in /usr/share/doc/*/copyright.
>>
>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>> permitted by applicable law.
>> Last login: Wed Dec  5 18:01:26 2018 from
>> 2001:982:c7c1:1:a96e:5bfc:cb2a:81a7
>> debian@beaglebone:~$ sudo systemctl status aceme
>> [sudo] password for debian:
>> ● aceme.service - to invoke aceme.py automatically
>>Loaded: loaded (/etc/systemd/system/aceme.service; enabled; vendor
>> preset: enabled)
>>Active: failed (Result: exit-code) since Wed 2018-12-05 19:39:44 UTC;
>> 3min 50s ago
>>   Process: 986 ExecStart=/home/debian/eme/acemev35.py (code=e

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

w...that example, like w/ what Jim F was typing out, is an example not
>> for your use. You will need to replace all the software w/ your software
>> but do use the first line.
>>
>> Oh...here is an example of that file above in Python in a .service file
>> w/ the name Pluck.py as the file name. Oh and let us call the .service file
>> Pluck.service.
>>
>> [Unit]
>> Description=Some Amount of Understanding for Your File
>>
>> [Service]
>> ExecStart=/home/debian/Pluck.py
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> Now...try to run your .service file that should be saved in
>> /etc/systemd/system/ as Pluck.service.
>>
>> ...
>>
>> Then, type this command: sudo systemctl enable Pluck.service
>>
>> Then, type this command: sudo systemctl start Pluck.service
>>
>> That should do it!
>>
>> If not, please reply w/ any relative ideas that are preventing your use
>> of a file on boot, e.g. errors and why the started .service file is not
>> working on boot.
>>
>> Seth
>>
>>
>>
>> On Tuesday, December 4, 2018 at 3:24:25 AM UTC-6, Harke Smits wrote:
>>>
>>> Looks like we are close. But the error codes are persistent. I can not
>>> copy/paste but serial does not load. Whatever I place in the first line of
>>> the python file.
>>> I tried: #!/bin/env/python and other shebangs (I learn!) but the error
>>> remains exactly the same. Btw: I use python2.x
>>> Any clue what to try next please?
>>> Cheers,
>>> Harke
>>>
>>>
>>> On Mon, 3 Dec 2018 at 23:18, Mala Dies  wrote:
>>>
>>>> Harke,
>>>>
>>>> Did you, in the software example you created, add #!/usr/bin/python3 to
>>>> the top of your program and then use this command: sudo chmod a+x
>>>> YourFile.py? Now, you should be able to run your .service file like before
>>>> from the example I had given.
>>>>
>>>> Seth
>>>>
>>>> On Monday, December 3, 2018 at 6:28:19 AM UTC-6, Harke Smits wrote:
>>>>>
>>>>> Thank you for your support Seth! I do not think I am running anything
>>>>> special. Just one Python script, 400 lines of my code, many thousends in
>>>>> libs, I guess. From QTerminal command line it runs perfectly. From within 
>>>>> a
>>>>> service not.
>>>>> Looking at your proposal: do you really intend to write: ExecStart=
>>>>> /path/myprog.py instead of: ExecStart=python /path/myprog.py
>>>>> That wonders me.
>>>>>  I "sudo nano" the service file and then write it in the
>>>>> /etc/systemd/system/ folder. Nothing else I do.
>>>>> Is that sufficient?
>>>>> Thanks a lot again.
>>>>> Regards,
>>>>> Harke
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, 3 Dec 2018 at 05:17, Mala Dies  wrote:
>>>>>
>>>>>> Hello Harke,
>>>>>>
>>>>>> Seth here. Um, are you trying to run a specific piece of software
>>>>>> only or are you trying to run multiple pieces of software?
>>>>>>
>>>>>> Seth
>>>>>>
>>>>>> P.S. I know you have to make a file accessible at
>>>>>> /etc/systemd/system/ w/ the proper instructions 
>>>>>> in
>>>>>> that .service file. Now, to make it run should be easy, i.e. if this is
>>>>>> just one piece of software.
>>>>>>
>>>>>> [Unit]
>>>>>> Description=More of what will happen!
>>>>>>
>>>>>> [Service]
>>>>>> ExecStart= /your/path/to/the/.py/file.py
>>>>>>
>>>>>> [Install]
>>>>>> WantedBy=multi-user.target
>>>>>>
>>>>>> ^
>>>>>> |
>>>>>> |
>>>>>>
>>>>>> Try this!
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Saturday, December 1, 2018 at 5:48:51 AM UTC-6, Harke Smits wrote:
>>>>>>>
>>>>>>> Hi Seth,
>>>>>>>
>>>>>>> In the meantime I think I tried just about any combination I can
>>>>>>> think of.
>>>>>>> Mostly I get the following error codes after dema

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

Hello Jim and Seth,

Thank you for your support. The service test scripts all run fine. My own
scripts persist in the error given above. My own service loads but aborts
at import serial, which, I guess, has not so much to do with serial, as
with something else. I will try and upload the relevant data and errors.
Keep you posted.
Thanks again (it getting very annoying though), cheers,
Harke


On Wed, 5 Dec 2018 at 05:16, Jim F  wrote:

> I actually think what you need to do is something along the following
> line. I don't think the shebang line makes a difference (rather, I know
> this) if you pass the python script directly to the python binary.
>
> ExecStart=/usr/bin/python2.7 /path/to/my_file.py
>
> You should post your errors if Seth's or my comments don't get you on
> track.
>
> Jim
>
> On Wed, Dec 5, 2018 at 12:23 AM Mala Dies  wrote:
>
>> Okay and Hello Once More,
>>
>> Seth here. I think (know) Jim F was on to something w/ your software and
>> setting up .service files for running on boot.
>>
>> For example: Here is another test example to try out to learn more about
>> .service files and starting files on boot on the BBB (or other related
>> bbb.io boards).
>>
>> ...
>>
>> #!/usr/bin/python
>>
>> import Adafruit_BBIO.GPIO as GPIO
>> import time
>>
>> #your awesome software
>>
>> ...
>>
>> Now...that example, like w/ what Jim F was typing out, is an example not
>> for your use. You will need to replace all the software w/ your software
>> but do use the first line.
>>
>> Oh...here is an example of that file above in Python in a .service file
>> w/ the name Pluck.py as the file name. Oh and let us call the .service file
>> Pluck.service.
>>
>> [Unit]
>> Description=Some Amount of Understanding for Your File
>>
>> [Service]
>> ExecStart=/home/debian/Pluck.py
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> Now...try to run your .service file that should be saved in
>> /etc/systemd/system/ as Pluck.service.
>>
>> ...
>>
>> Then, type this command: sudo systemctl enable Pluck.service
>>
>> Then, type this command: sudo systemctl start Pluck.service
>>
>> That should do it!
>>
>> If not, please reply w/ any relative ideas that are preventing your use
>> of a file on boot, e.g. errors and why the started .service file is not
>> working on boot.
>>
>> Seth
>>
>>
>>
>> On Tuesday, December 4, 2018 at 3:24:25 AM UTC-6, Harke Smits wrote:
>>>
>>> Looks like we are close. But the error codes are persistent. I can not
>>> copy/paste but serial does not load. Whatever I place in the first line of
>>> the python file.
>>> I tried: #!/bin/env/python and other shebangs (I learn!) but the error
>>> remains exactly the same. Btw: I use python2.x
>>> Any clue what to try next please?
>>> Cheers,
>>> Harke
>>>
>>>
>>> On Mon, 3 Dec 2018 at 23:18, Mala Dies  wrote:
>>>
>>>> Harke,
>>>>
>>>> Did you, in the software example you created, add #!/usr/bin/python3 to
>>>> the top of your program and then use this command: sudo chmod a+x
>>>> YourFile.py? Now, you should be able to run your .service file like before
>>>> from the example I had given.
>>>>
>>>> Seth
>>>>
>>>> On Monday, December 3, 2018 at 6:28:19 AM UTC-6, Harke Smits wrote:
>>>>>
>>>>> Thank you for your support Seth! I do not think I am running anything
>>>>> special. Just one Python script, 400 lines of my code, many thousends in
>>>>> libs, I guess. From QTerminal command line it runs perfectly. From within 
>>>>> a
>>>>> service not.
>>>>> Looking at your proposal: do you really intend to write: ExecStart=
>>>>> /path/myprog.py instead of: ExecStart=python /path/myprog.py
>>>>> That wonders me.
>>>>>  I "sudo nano" the service file and then write it in the
>>>>> /etc/systemd/system/ folder. Nothing else I do.
>>>>> Is that sufficient?
>>>>> Thanks a lot again.
>>>>> Regards,
>>>>> Harke
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, 3 Dec 2018 at 05:17, Mala Dies  wrote:
>>>>>
>>>>>> Hello Harke,
>>>>>>
>>>>>> Seth here. Um, are you trying to run a specific piece of softwar

[beagleboard] I2C busses mixed up?

[Harke Smits]

Hello Learned group,

I have an I2C problem that I confuses me: I have activated I2C1 in 
uEnv.txt. That works. Now i2cdetect -y -r i (for i = 0,1,2) gives a quick 
response. However, i2c2 behaves like i2c1. i=1 shows nothing connected, 0 
shows some UU's and 2 shows devices I can recognise: I can see the 
addresses for the rtc and the motor cape. These are designed to work with 
i2c1, so the rtc and motor cape do not work. 
What happens here and how can I resolve that?
Many thanks in advance,
Harke

-- 
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/8ccfec38-f530-4f5d-a949-07c4a0874613%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

Looks like we are close. But the error codes are persistent. I can not
copy/paste but serial does not load. Whatever I place in the first line of
the python file.
I tried: #!/bin/env/python and other shebangs (I learn!) but the error
remains exactly the same. Btw: I use python2.x
Any clue what to try next please?
Cheers,
Harke


On Mon, 3 Dec 2018 at 23:18, Mala Dies  wrote:

> Harke,
>
> Did you, in the software example you created, add #!/usr/bin/python3 to
> the top of your program and then use this command: sudo chmod a+x
> YourFile.py? Now, you should be able to run your .service file like before
> from the example I had given.
>
> Seth
>
> On Monday, December 3, 2018 at 6:28:19 AM UTC-6, Harke Smits wrote:
>>
>> Thank you for your support Seth! I do not think I am running anything
>> special. Just one Python script, 400 lines of my code, many thousends in
>> libs, I guess. From QTerminal command line it runs perfectly. From within a
>> service not.
>> Looking at your proposal: do you really intend to write: ExecStart=
>> /path/myprog.py instead of: ExecStart=python /path/myprog.py
>> That wonders me.
>>  I "sudo nano" the service file and then write it in the
>> /etc/systemd/system/ folder. Nothing else I do.
>> Is that sufficient?
>> Thanks a lot again.
>> Regards,
>> Harke
>>
>>
>>
>>
>> On Mon, 3 Dec 2018 at 05:17, Mala Dies  wrote:
>>
>>> Hello Harke,
>>>
>>> Seth here. Um, are you trying to run a specific piece of software only
>>> or are you trying to run multiple pieces of software?
>>>
>>> Seth
>>>
>>> P.S. I know you have to make a file accessible at
>>> /etc/systemd/system/ w/ the proper instructions in
>>> that .service file. Now, to make it run should be easy, i.e. if this is
>>> just one piece of software.
>>>
>>> [Unit]
>>> Description=More of what will happen!
>>>
>>> [Service]
>>> ExecStart= /your/path/to/the/.py/file.py
>>>
>>> [Install]
>>> WantedBy=multi-user.target
>>>
>>> ^
>>> |
>>> |
>>>
>>> Try this!
>>>
>>>
>>>
>>> On Saturday, December 1, 2018 at 5:48:51 AM UTC-6, Harke Smits wrote:
>>>>
>>>> Hi Seth,
>>>>
>>>> In the meantime I think I tried just about any combination I can think
>>>> of.
>>>> Mostly I get the following error codes after demanding the status;
>>>> Loaded
>>>> Active: failed
>>>> Process: 1002 ... code = exited, status=203/EXEC
>>>> Main PID: 1002.
>>>>
>>>> In short; no luck so far
>>>> I am doing something fundamentally wrong I think... Or it is just
>>>> impossible.
>>>> I am lost here..
>>>> Cheers,
>>>> Harke
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, 30 Nov 2018 at 22:46, Mala Dies  wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> When you type under [Service], use only the PATH. Try that idea first.
>>>>> I may be able to help out a bit.
>>>>>
>>>>> Seth
>>>>>
>>>>> P.S. For instance, say I have a Python file in this dir:
>>>>> /home/debian/LoveBone/. I would simply put, under the [Service] tag,
>>>>> ExecStart=/home/debain/LoveBone/MultipleIdeas.py for my PATH. Try that 
>>>>> idea
>>>>> and think about moving that [Unit] option for Requires=graphical.target.
>>>>> Try that section under your [Install] section.
>>>>>
>>>>> On Friday, November 30, 2018 at 10:50:15 AM UTC-6, Harke Smits wrote:
>>>>>>
>>>>>> Hello Seth,
>>>>>>
>>>>>> Thanks a lot for your reaction. I already digested these pages (as
>>>>>> good as I could, I am an RF engineer, not a programmer). Unfortunately 
>>>>>> this
>>>>>> does not help me much. The service file is at the correct location.
>>>>>> I hope to get some clue where I am doing something wrong.
>>>>>> Thanks again, regards,
>>>>>> Harke
>>>>>>
>>>>>>
>>>>>> On Friday, 30 November 2018 12:18:26 UTC+1, Mala Dies wrote:
>>>>>>>
>>>>>>> Hello Again Harke,
>>>>>>>
>>>>>>> Seth here. You need

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

Hello jim,

Many thanks for chiming in! I copied your example, only close, and then got
an error that I need to provide the complete path for python as well. It
never occured to me as I thought I can invoke Python just from about
everywhere. No way. Now it loads the proper way. Unfortunately my
application still does not start correctly: after importing several other
libraries (like Adafruit) the import of serial (pyserial) goes wrong and
the service halts. I have no idea what goes wrong this time. When I invoke
python from the command line in QTerminal the application starts correctly,
so included the import of serial and other libraries
Is this a python issue or what?
Maybe time for another topic?
Anyway: Seth and Jim thanks again for your time and effort. Well
appreciated!
Best regards.
Harke


On Mon, 3 Dec 2018 at 17:55, Jim F  wrote:

> Hi Harke,
>
> I am hoping to build up some good will to get an answer to my question, so
> let me see if I can pitch in. Plus I wanted to get a systemd service
> working anyway, which I did successfully this morning. Here are the steps I
> took.
>
> 1) Create the application. I wrote a stupid python program:
>
> #!/bin/env python
> import sys
> print('It ran once.')
> sys.exit(0)
>
> 2) Create the service file
>  - Two ways to do this. First you can create a file in
> /etc/systemd/system/test.service (or whatever name you like) and edit it
> manually. Or you can run systemctl edit --force test.service to do the same
> thing.
>  - The file shall have 644 permissions, root:root owner.
>  - Paste the following simple service file
>
> [Unit]
> Description=Test
>
> [Service]
> ExecStart=/usr/bin/python /home/debian/test.py
>
> [Install]
> WantedBy=multi-user.target
>
> 3. Enable the service file. Run:  systemctl enable test
>   - Response will be:  Created symlink
> /etc/systemd/system/multi-user.target.wants/test.service →
> /etc/systemd/system/test.service.
>
> 4. Check status. Run:  systemctl status test
>   - Response should be:
> ● test.service - Test
>Loaded: loaded (/etc/systemd/system/test.service; enabled; vendor
> preset: enabled)
>Active: inactive (dead) since Mon 2018-12-03 14:18:33 UTC; 1s ago
>   Process: 2853 ExecStart=/usr/bin/python /home/debian/test.py
> (code=exited, status=0/SUCCESS)
>  Main PID: 2853 (code=exited, status=0/SUCCESS)
>
> Dec 03 14:18:33 beaglebone systemd[1]: Started Test.
> Dec 03 14:18:33 beaglebone python[2853]: It ran once.
>
>
> 5. Now that you have something stupid working, change the files and
> increase level of complexity. Replace my idiotic test.py program with your
> real one. In editing the service file ensure you use absolute path. Update
> the test.service script and make sure that you run:  systemctl
> daemon-reload   whenever you change the service files.
>
> Hope that helps. It worked for me.
>
> Best,
>
> Jim
>
> On Mon, Dec 3, 2018 at 7:28 AM Harke Smits  wrote:
>
>> Thank you for your support Seth! I do not think I am running anything
>> special. Just one Python script, 400 lines of my code, many thousends in
>> libs, I guess. From QTerminal command line it runs perfectly. From within a
>> service not.
>> Looking at your proposal: do you really intend to write: ExecStart=
>> /path/myprog.py instead of: ExecStart=python /path/myprog.py
>> That wonders me.
>>  I "sudo nano" the service file and then write it in the
>> /etc/systemd/system/ folder. Nothing else I do.
>> Is that sufficient?
>> Thanks a lot again.
>> Regards,
>> Harke
>>
>>
>>
>>
>> On Mon, 3 Dec 2018 at 05:17, Mala Dies  wrote:
>>
>>> Hello Harke,
>>>
>>> Seth here. Um, are you trying to run a specific piece of software only
>>> or are you trying to run multiple pieces of software?
>>>
>>> Seth
>>>
>>> P.S. I know you have to make a file accessible at
>>> /etc/systemd/system/ w/ the proper instructions in
>>> that .service file. Now, to make it run should be easy, i.e. if this is
>>> just one piece of software.
>>>
>>> [Unit]
>>> Description=More of what will happen!
>>>
>>> [Service]
>>> ExecStart= /your/path/to/the/.py/file.py
>>>
>>> [Install]
>>> WantedBy=multi-user.target
>>>
>>> ^
>>> |
>>> |
>>>
>>> Try this!
>>>
>>>
>>>
>>> On Saturday, December 1, 2018 at 5:48:51 AM UTC-6, Harke Smits wrote:
>>>>
>>>> Hi Seth,
>>>>
>>>> In the meantime I think I tried just about any combination I can think
>>>&g

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

Thank you for your support Seth! I do not think I am running anything
special. Just one Python script, 400 lines of my code, many thousends in
libs, I guess. From QTerminal command line it runs perfectly. From within a
service not.
Looking at your proposal: do you really intend to write: ExecStart=
/path/myprog.py instead of: ExecStart=python /path/myprog.py
That wonders me.
 I "sudo nano" the service file and then write it in the
/etc/systemd/system/ folder. Nothing else I do.
Is that sufficient?
Thanks a lot again.
Regards,
Harke




On Mon, 3 Dec 2018 at 05:17, Mala Dies  wrote:

> Hello Harke,
>
> Seth here. Um, are you trying to run a specific piece of software only or
> are you trying to run multiple pieces of software?
>
> Seth
>
> P.S. I know you have to make a file accessible at
> /etc/systemd/system/ w/ the proper instructions in
> that .service file. Now, to make it run should be easy, i.e. if this is
> just one piece of software.
>
> [Unit]
> Description=More of what will happen!
>
> [Service]
> ExecStart= /your/path/to/the/.py/file.py
>
> [Install]
> WantedBy=multi-user.target
>
> ^
> |
> |
>
> Try this!
>
>
>
> On Saturday, December 1, 2018 at 5:48:51 AM UTC-6, Harke Smits wrote:
>>
>> Hi Seth,
>>
>> In the meantime I think I tried just about any combination I can think of.
>> Mostly I get the following error codes after demanding the status;
>> Loaded
>> Active: failed
>> Process: 1002 ... code = exited, status=203/EXEC
>> Main PID: 1002.
>>
>> In short; no luck so far
>> I am doing something fundamentally wrong I think... Or it is just
>> impossible.
>> I am lost here..
>> Cheers,
>> Harke
>>
>>
>>
>>
>> On Fri, 30 Nov 2018 at 22:46, Mala Dies  wrote:
>>
>>> Hello,
>>>
>>> When you type under [Service], use only the PATH. Try that idea first. I
>>> may be able to help out a bit.
>>>
>>> Seth
>>>
>>> P.S. For instance, say I have a Python file in this dir:
>>> /home/debian/LoveBone/. I would simply put, under the [Service] tag,
>>> ExecStart=/home/debain/LoveBone/MultipleIdeas.py for my PATH. Try that idea
>>> and think about moving that [Unit] option for Requires=graphical.target.
>>> Try that section under your [Install] section.
>>>
>>> On Friday, November 30, 2018 at 10:50:15 AM UTC-6, Harke Smits wrote:
>>>>
>>>> Hello Seth,
>>>>
>>>> Thanks a lot for your reaction. I already digested these pages (as good
>>>> as I could, I am an RF engineer, not a programmer). Unfortunately this does
>>>> not help me much. The service file is at the correct location.
>>>> I hope to get some clue where I am doing something wrong.
>>>> Thanks again, regards,
>>>> Harke
>>>>
>>>>
>>>> On Friday, 30 November 2018 12:18:26 UTC+1, Mala Dies wrote:
>>>>>
>>>>> Hello Again Harke,
>>>>>
>>>>> Seth here. You need to put your .service files in
>>>>> /etc/systemd/system/. I am pretty sure.
>>>>>
>>>>> Seth
>>>>>
>>>>> On Monday, November 26, 2018 at 5:49:16 AM UTC-6, Harke Smits wrote:
>>>>>>
>>>>>> Hello learned group,
>>>>>>
>>>>>> I have a Python application that I'd like to see start up on boot. It
>>>>>> uses Tkinter, so it needs the graphical environment.
>>>>>> Running: python /home/debian/eme/myprog.py from the QTerminal command
>>>>>> line works as expected. Not outside the LXQT environment, which is 
>>>>>> normal I
>>>>>> think.
>>>>>> I made a service file: myprog.service like this:
>>>>>> [Unit]
>>>>>> Description=to invoke myprog automatically on boot
>>>>>> Requires=graphical.target
>>>>>> [Service]
>>>>>> Type=simple
>>>>>> WorkingDirectory=/home/debian/eme/
>>>>>> ExecStart=python /home/debian/eme/myprog.py
>>>>>> [Install]
>>>>>> WantedBy=multi-user.target
>>>>>>
>>>>>> Service file is located at both: /etc/systemd/system/ and
>>>>>> /lib/systemd/system/ as I am unsure where it actually belongs. Of course 
>>>>>> I
>>>>>> already spend a lot of time at internet to find a solution. Only succes
>>>>>> storie

Re: [beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

Hi Seth,

In the meantime I think I tried just about any combination I can think of.
Mostly I get the following error codes after demanding the status;
Loaded
Active: failed
Process: 1002 ... code = exited, status=203/EXEC
Main PID: 1002.

In short; no luck so far
I am doing something fundamentally wrong I think... Or it is just
impossible.
I am lost here..
Cheers,
Harke




On Fri, 30 Nov 2018 at 22:46, Mala Dies  wrote:

> Hello,
>
> When you type under [Service], use only the PATH. Try that idea first. I
> may be able to help out a bit.
>
> Seth
>
> P.S. For instance, say I have a Python file in this dir:
> /home/debian/LoveBone/. I would simply put, under the [Service] tag,
> ExecStart=/home/debain/LoveBone/MultipleIdeas.py for my PATH. Try that idea
> and think about moving that [Unit] option for Requires=graphical.target.
> Try that section under your [Install] section.
>
> On Friday, November 30, 2018 at 10:50:15 AM UTC-6, Harke Smits wrote:
>>
>> Hello Seth,
>>
>> Thanks a lot for your reaction. I already digested these pages (as good
>> as I could, I am an RF engineer, not a programmer). Unfortunately this does
>> not help me much. The service file is at the correct location.
>> I hope to get some clue where I am doing something wrong.
>> Thanks again, regards,
>> Harke
>>
>>
>> On Friday, 30 November 2018 12:18:26 UTC+1, Mala Dies wrote:
>>>
>>> Hello Again Harke,
>>>
>>> Seth here. You need to put your .service files in /etc/systemd/system/.
>>> I am pretty sure.
>>>
>>> Seth
>>>
>>> On Monday, November 26, 2018 at 5:49:16 AM UTC-6, Harke Smits wrote:
>>>>
>>>> Hello learned group,
>>>>
>>>> I have a Python application that I'd like to see start up on boot. It
>>>> uses Tkinter, so it needs the graphical environment.
>>>> Running: python /home/debian/eme/myprog.py from the QTerminal command
>>>> line works as expected. Not outside the LXQT environment, which is normal I
>>>> think.
>>>> I made a service file: myprog.service like this:
>>>> [Unit]
>>>> Description=to invoke myprog automatically on boot
>>>> Requires=graphical.target
>>>> [Service]
>>>> Type=simple
>>>> WorkingDirectory=/home/debian/eme/
>>>> ExecStart=python /home/debian/eme/myprog.py
>>>> [Install]
>>>> WantedBy=multi-user.target
>>>>
>>>> Service file is located at both: /etc/systemd/system/ and
>>>> /lib/systemd/system/ as I am unsure where it actually belongs. Of course I
>>>> already spend a lot of time at internet to find a solution. Only succes
>>>> stories here
>>>> I entered the following;
>>>> sudo systemctl enable myprog.service: nothing special
>>>> sudo systemctl start myprog.service: service is not loaded properly.
>>>> sudo systemctl status myprog.service: error (invalid argument),
>>>> inactive (dead).
>>>>
>>>> Both from bash or within QTerminal: behaviour is the same.
>>>>
>>>> Please help me out what to do.
>>>> Kind regards,
>>>> Harke
>>>>
>>>> --
> 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/goOORlttd2c/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/91cdcefd-06b6-4d68-96fe-a95b7dcd4573%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/91cdcefd-06b6-4d68-96fe-a95b7dcd4573%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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/CAHmciaZDo3h_tWvXBRJHG7Gc%2B77n3MjD4MQn%3DU4%3DUpqFwnYyBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Debian 9: autorun on boot with systemd does not work

[Harke Smits]

Hello Seth,

Thanks a lot for your reaction. I already digested these pages (as good as 
I could, I am an RF engineer, not a programmer). Unfortunately this does 
not help me much. The service file is at the correct location.
I hope to get some clue where I am doing something wrong.
Thanks again, regards,
Harke


On Friday, 30 November 2018 12:18:26 UTC+1, Mala Dies wrote:
>
> Hello Again Harke,
>
> Seth here. You need to put your .service files in /etc/systemd/system/. I 
> am pretty sure.
>
> Seth
>
> On Monday, November 26, 2018 at 5:49:16 AM UTC-6, Harke Smits wrote:
>>
>> Hello learned group,
>>
>> I have a Python application that I'd like to see start up on boot. It 
>> uses Tkinter, so it needs the graphical environment. 
>> Running: python /home/debian/eme/myprog.py from the QTerminal command 
>> line works as expected. Not outside the LXQT environment, which is normal I 
>> think. 
>> I made a service file: myprog.service like this:
>> [Unit]
>> Description=to invoke myprog automatically on boot
>> Requires=graphical.target
>> [Service]
>> Type=simple
>> WorkingDirectory=/home/debian/eme/
>> ExecStart=python /home/debian/eme/myprog.py
>> [Install]
>> WantedBy=multi-user.target
>>
>> Service file is located at both: /etc/systemd/system/ and 
>> /lib/systemd/system/ as I am unsure where it actually belongs. Of course I 
>> already spend a lot of time at internet to find a solution. Only succes 
>> stories here
>> I entered the following;
>> sudo systemctl enable myprog.service: nothing special
>> sudo systemctl start myprog.service: service is not loaded properly.
>> sudo systemctl status myprog.service: error (invalid argument), inactive 
>> (dead).
>>  
>> Both from bash or within QTerminal: behaviour is the same.
>>
>> Please help me out what to do.
>> Kind regards,
>> Harke
>>
>>

-- 
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/a80b6dbf-8740-4d42-94f6-c34714f99e05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Debian 9: autorun on boot with systemd does not work

[Harke Smits]

Hello learned group,

I have a Python application that I'd like to see start up on boot. It uses 
Tkinter, so it needs the graphical environment. 
Running: python /home/debian/eme/myprog.py from the QTerminal command line 
works as expected. Not outside the LXQT environment, which is normal I 
think. 
I made a service file: myprog.service like this:
[Unit]
Description=to invoke myprog automatically on boot
Requires=graphical.target
[Service]
Type=simple
WorkingDirectory=/home/debian/eme/
ExecStart=python /home/debian/eme/myprog.py
[Install]
WantedBy=multi-user.target

Service file is located at both: /etc/systemd/system/ and 
/lib/systemd/system/ as I am unsure where it actually belongs. Of course I 
already spend a lot of time at internet to find a solution. Only succes 
stories here
I entered the following;
sudo systemctl enable myprog.service: nothing special
sudo systemctl start myprog.service: service is not loaded properly.
sudo systemctl status myprog.service: error (invalid argument), inactive 
(dead).
 
Both from bash or within QTerminal: behaviour is the same.

Please help me out what to do.
Kind regards,
Harke

-- 
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/dab4147a-f93e-4225-982e-3acad401ed64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4D Systems display does now work with latest Debian release

[Harke Smits]

Thats it! It already works with count =10 but I made a typo, sorry. I can
now flash this version to internal memory, I guess?
Not being an expert, as you already suspect, this is quite a difficult
platform. I like it, but I need a lot of help. Fortunately there a are a
lot if helpful people out there.
Thanks a lot Robert!


On Sun, 18 Nov 2018 at 21:54, Robert Nelson  wrote:

> On Sun, Nov 18, 2018 at 2:49 PM Harke Smits  wrote:
> >
> > here you are...
> > debian@beaglebone:/var/lib/cloud9$ sudo /opt/scripts/tools/version.sh
> > [sudo] password for debian:
> > git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
> > eeprom:[A335BNLT00C00816BBBK0459]
> > model:[TI_AM335x_BeagleBone_Black]
> > dogtag:[BeagleBoard.org Debian Image 2018-10-07]
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
> 2018.09-2-g0b54a51eee]:[location: dd MBR]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2017.01-6-gb2bbabfe41]:[location: dd MBR]
>
> Still there... so let's try 100Mb intead of 10Mb..
>
> sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100
>
> and reboot.
>
> 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/CAHmciabak_haPgv%3DwrX5V7f2v-BFgjffYV4spa7jgcx58%3D0Ygg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4D Systems display does now work with latest Debian release

[Harke Smits]

here you are...
debian@beaglebone:/var/lib/cloud9$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
eeprom:[A335BNLT00C00816BBBK0459]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
2018.09-2-g0b54a51eee]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2017.01-6-gb2bbabfe41]:[location: dd MBR]
kernel:[4.14.71-ti-r80]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade
]
pkg:[bb-cape-overlays]:[4.4.20181106.0-0rcnee0~stretch+20181110]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20181108.0-0rcnee0~stretch+20181110]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep
admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[1.062762] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size
568
[1.382918] pinctrl-single 44e10800.pinmux: pin PIN40 already requested
by panel; cannot claim for 0-0070
[1.392690] pinctrl-single 44e10800.pinmux: pin-40 (0-0070) status -22
[1.399299] pinctrl-single 44e10800.pinmux: could not request pin 40
(PIN40) from group nxp_hdmi_bonelt_pins  on device pinctrl-single
dmesg | grep gpio-of-helper
[1.064364] gpio-of-helper ocp:cape-universal: ready
END
debian@beaglebone:/var/lib/cloud9$
BR,
Harke

On Sun, 18 Nov 2018 at 21:39, Robert Nelson  wrote:

> On Sun, Nov 18, 2018 at 2:35 PM Harke Smits  wrote:
> >
> > Thank you for your help, Robert.
> > Unfortunately this does not change anything with respect to the display.
>
> please run
>
> sudo /opt/scripts/tools/version.sh
>
> again
>
> 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/CAHmciabEOfoahTybcyWbaaNSsqVMjZ0H8cbCuKbL4kMpG6iXng%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4D Systems display does now work with latest Debian release

[Harke Smits]

Thank you for your help, Robert.
Unfortunately this does not change anything with respect to the display.
Please advise.
Best regards,
Harke

On Sun, 18 Nov 2018 at 21:17, Robert Nelson  wrote:

> On Sun, Nov 18, 2018 at 1:30 PM Harke Smits  wrote:
> >
> > This is what I get:
> > debian@beaglebone:/var/lib/cloud9$ sudo /opt/scripts/tools/version.sh
> > [sudo] password for debian:
> > git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
> > eeprom:[A335BNLT00C00816BBBK0459]
> > model:[TI_AM335x_BeagleBone_Black]
> > dogtag:[BeagleBoard.org Debian Image 2018-10-07]
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
> 2018.09-2-g0b54a51eee]:[location: dd MBR]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2017.01-6-gb2bbabfe41]:[location: dd MBR]
>
> Your version of u-boot in the eMMC is too old, thus blocking u-boot
> overlays from working..
>
> Just run:
>
> sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10
>
> and reboot.
>
> 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/CAHmciab6jDO7vNJM_2jS8K-Sijh1c7Zi-0T9Hdf%2BrypHd3U4ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4D Systems display does now work with latest Debian release

[Harke Smits]

This is what I get:
debian@beaglebone:/var/lib/cloud9$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
eeprom:[A335BNLT00C00816BBBK0459]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
2018.09-2-g0b54a51eee]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2017.01-6-gb2bbabfe41]:[location: dd MBR]
kernel:[4.14.71-ti-r80]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade
]
pkg:[bb-cape-overlays]:[4.4.20181106.0-0rcnee0~stretch+20181110]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.4-git20181108.0-0rcnee0~stretch+20181110]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video
plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep
admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[1.062794] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size
568
[1.382856] pinctrl-single 44e10800.pinmux: pin PIN40 already requested
by panel; cannot claim for 0-0070
[1.392593] pinctrl-single 44e10800.pinmux: pin-40 (0-0070) status -22
[1.399186] pinctrl-single 44e10800.pinmux: could not request pin 40
(PIN40) from group nxp_hdmi_bonelt_pins  on device pinctrl-single
dmesg | grep gpio-of-helper
[1.064403] gpio-of-helper ocp:cape-universal: ready
END
debian@beaglebone:/var/lib/cloud9$

Thansk a lot in advance,
Harke

On Sun, 18 Nov 2018 at 19:19, Robert Nelson  wrote:

> On Sun, Nov 18, 2018 at 9:14 AM Harke Smits  wrote:
> >
> > I have a BBB with a 4D Systems display cape. Boots and works fine with
> Debian 2017-01-22, flashed in on board memory. I have Debian 2018-10-07 on
> a uSD card. Inserting this card and booting gives the correct Debian
> version, but the display does not work. All verified via LAN interface. I
> checked uEnv.txt but I can not find a corresponding code line (to
> enable...). Do I miss something here? What needs to be done to make this
> system work, please? Thanks in advance, Harke
>
> Well run this command so we can see what you are actually dealing with:
>
> sudo /opt/scripts/tools/version.sh
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>

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

[beagleboard] 4D Systems display does now work with latest Debian release

[Harke Smits]

I have a BBB with a 4D Systems display cape. Boots and works fine with 
Debian 2017-01-22, flashed in on board memory. I have Debian 2018-10-07 on 
a uSD card. Inserting this card and booting gives the correct Debian 
version, but the display does not work. All verified via LAN interface. I 
checked uEnv.txt but I can not find a corresponding code line (to 
enable...). Do I miss something here? What needs to be done to make this 
system work, please? Thanks in advance, Harke

-- 
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/34bce5e0-ce73-4da2-876a-0c6890723208%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] "no display name and no $display environment variable"

[Harke Smits]

Thanks for your comments. The f/ph type was quickly solved. (thanks!).
But then it still does not work. After a couple of days experimenting and
googling  I get lost. I know most systemd commend by heart now ;-). Now
I get the error: ac.service is not loaded properly. Error: invalid
argument. My service is now:
[Unit]
Description 
After = graphical.target
[Service]
Type = idle
Environment="DISPLAY=:0"
XAUTHORITY *{no arguments needed?}*
ExecStart = /home/debian/eme {*etc to run Python script and make log file}*
[Install]
WantedBy=default.target

I do hope you can get me going.
Thanks in advance,
Harke
PS: I considered using autostart that works perfect on my two year old
Debian on another system with LXDE. Now LXQT is used and I can not find
this anymore.

On 15 August 2017 at 09:25, 'Roberts Maria' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

>
> 
> On Tue, 8/15/17, Przemek Klosowski <przemek.klosow...@gmail.com> wrote:
>
>  Subject: Re: [beagleboard] "no display name and no $display environment
> variable"
>  To: beagleboard@googlegroups.com
>  Date: Tuesday, August 15, 2017, 5:04 AM
>
>
>
>  On Mon,
>  Aug 14, 2017 at 6:23 AM, Harke Smits <yrra...@gmail.com>
>  wrote:
>  Thank you
>  very much, I keep on learning. My application now runs fine
>  manually from XTerminal. Now I want  to run the application
>  on boot. I figured out a systemd service is problably the
>  way to go. I managed to define that (ac.service) and run it
>  on boot up. I wrote:[Unit]After =
>  grafical.target[Service]Type =
>  idleExecStart = /home/debian/eme {etc to run
>  Python script and make log
>  file}[Install]WantedBy=multi-user.target
>  This sort of works but the
>  application does not start: the log file gives the famous
>  $DISPLAY error. I try to start my application last, so after
>  the X server has been started. Maybe the
>  "WantedBy" statement is wrong?
>  The default setup
>  in systemd starts the graphical target (btw, graphical not
>  grafical), and runs the login manager which then runs
>  graphical desktop manager which allows you to run your
>  app.The simplest way to handle it is to use the
>  'autostart' feature of the display
>  manager. You can replace the whole setup in
>  systemd by doing what you are doing, but you have to take
>  out the display/login manager. You will also
>  need to
>  addEnvironment="DISPLAY=:0" and
>  maybe XAUTHORITY to the [Service}
>  section
>
>
>
>  --
>
>  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%3D1GgHE3pQKSpH4gq1V2N_PJWiZVoZMFtgT0FjOUdGP_GtebQ%
> 40mail.gmail.com.
>
>  For more options, visit https://groups.google.com/d/optout.
>  n numele unei asa-zise ascutiri a luptei de clasa  a organizarii si
> manifestarii dictaturiiproletariatului din teoria marxist leninista   au
> fost incalcate brutal drepturi si libertati democratice elementare ale
> oamenilor. Orice forma de opozitie a fost reprimata violent. Sub acuzatia
> imaginara de tradare   sabotaj  sau agenti ai imperialismului  a fost
> profund afectat tot corpul de elita al vietii politice si culturale
> interbelice. intre 1947-1952 au fost inscenate numeroase procese politice
> ca cel impotriva liderilor Partidului National taranesc - luliu Maniu si
> Ion Mihalache si altele  ce s-au soldat cu pedepse grele la inchisoare sau
> lagare de munca  unde au pierit multi adversari ai comunistilor. Au fost
> lichidate  cu brutalitate  incercarile de rezistenta armata din zona
> muntilor Bucegi  Fagaras. S-a manifestat totusi  desi firav  o rezistenta
> militara la instaurarea regimului comunist. Au actionat  astfel  grupuri
> inarmate  ca de exemplu in Banat -Tanase  lonescu  Blanaru  Spiru  in
> Oltenia -maiorul Dumitriu in Arges - Traian Marinescu  Fagaras - general
> Arsanescu si fratii Arnautoiu. in cadrul constituirii noului aparat de
> stat  intre 1948-1949 s-au creat Securitatea si Militia populara.
> Securitatea a devenit un instrument de teroare si represiune  indreptat
> impotriva oricarui opozant al noului regim. Ea era coordonata de generali
> dintre care unii erau agenti ai serviciilor de spionaj  ca A. Nikolski  P.
> Bodnarenko. in 1952 si-a inceput activitatea de reprimare Alexandru
> Draghici  devenit ulterior ministru de interne.
>
> --
> For more options, visi

Re: [beagleboard] "no display name and no $display environment variable"

[Harke Smits]

Thank you very much, I keep on learning. My application now runs fine
manually from XTerminal. Now I want  to run the application on boot. I
figured out a systemd service is problably the way to go. I managed to
define that (ac.service) and run it on boot up. I wrote:
[Unit]
After = grafical.target
[Service]
Type = idle
ExecStart = /home/debian/eme {*etc to run Python script and make log file}*
[Install]
WantedBy=multi-user.target

This sort of works but the application does not start: the log file gives
the famous $DISPLAY error. I try to start my application last, so after the
X server has been started. Maybe the "WantedBy" statement is wrong?
Thanks a lot in advance, best regards,
Harke




On 13 August 2017 at 22:42, Przemek Klosowski <przemek.klosow...@gmail.com>
wrote:

>
>
> On Sat, Aug 12, 2017 at 6:13 AM, Harke Smits <yrra...@gmail.com> wrote:
>
>>  I have a stand alone Beagleboard system, keyboard/mouse connected via
>> usb dongle. The system starts up normally, in grafics mode, I can invoke
>> internet, no problem, LAN connected. Going to XTerm I get the linux prompt,
>> still in grafics mode. A simple TKInter test program works.
>>
>
> OK, this is normal
>
> Going to linux (XTRL/ALT/F1) I can invoke startx that brings me back were
>> I came from: the grafics environment (LXDE).
>>
>
> Now, this is not needed---you already have X running, and you should run
> all your GUI programs from the Xterm like your TKInter test above. There's
> no need to 'go to linux' again. Perhaps you are mislead by the fact that
> after you run a graphical program from the shell prompt in XTerm you don't
> get the prompt back---but that's easily fixed by running the command in the
> background by adding the ampersand to the end of the command:
> tesst &
>
> When you go to the text console and do startx again, you have dueling X
> servers, and I am not sure what is the expected result of that. Don't do
> that---use the original X by either running in background with &, or
> creating a new xterm, or arranging for your app icon to be visible so that
> you can run it by doubleclicking the icon.
>
> Starting the TKInter test program from the Linux prompt gives me the
>> famous error message in the title. In Xterminal "echo $DISPLAY" renders :1,
>> in plain linux: a blank line.  Starting my application in XTerm gives a
>> fully blank screen.
>>
>> --
> 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/s5Qhhc75e1c/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/CAC%3D1GgH_1i-X_bGVYUE9vEv2uBO%
> 3DMZ3dzV08wU2ix%3D36c8_s0A%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgH_1i-X_bGVYUE9vEv2uBO%3DMZ3dzV08wU2ix%3D36c8_s0A%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> 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/CAHmciaaE-7y%2BAVPztLWJVqDLfrtt0YL-fhWQ%3Du0X98SMrzQYNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] "no display name and no $display environment variable"

[Harke Smits]

Hello Przemek,

Thanks for your reaction. I am by no means an expert so I may have the
terminology wrong. I have a stand alone Beagleboard system, keyboard/mouse
connected via usb dongle. The system starts up normally, in grafics mode, I
can invoke internet, no problem, LAN connected. Going to XTerm I get the
linux prompt, still in grafics mode. A simple TKInter test program works.
Going to linux (XTRL/ALT/F1) I can invoke startx that brings me back were I
came from: the grafics environment (LXDE). Starting the TKInter test
program from the Linux prompt gives me the famous error message in the
title. In Xterminal "echo $DISPLAY" renders :1, in plain linux: a blank
line.  Starting my application in XTerm gives a fully blank screen.
Still very puzzling...
I hope you or someone else can bring me further.
Kind regards,
Harke

On 11 August 2017 at 15:26, Przemek Klosowski <przemek.klosow...@gmail.com>
wrote:

>
>
> On Fri, Aug 11, 2017 at 6:33 AM, Harke Smits <yrra...@gmail.com> wrote:
>
>> Hello Learned group,
>>
>> I have a BBB with Debian version 2017-03-19, the latest release as far as
>> I know, with a 4D systems display. I have made a Python script using
>> TkInter, running fine on another BBB system with an older Debian version.
>>
> OK, so you are interacting with your BBB directly, not from another
> computer via SSH or serial, right?
>
>
>> I made a simple testscript using TkInter as well. Running the testscript
>> form XTerm or UXTerm (what is the difference?) works: a simple window pops
>> up.
>> Running the same from Debian bash directly displays the well known error
>> above. I googled a lot but no answer found yet.
>>
> What do you mean by 'from the debian bash'? Normally, you're sitting in
> front of a graphical desktop (i.e. running the X server or Wayland)
> displaying a terminal emulator (e.g. XTerm) that runs a shell (e.g. bash).
> The shell command (e.g. xclock) starts the process that issues X11 commands
> that go to the current $DISPLAY and show up as windows.
> If you're not running the X server, i.e. sitting at the raw text terminal
> console (all black screen with white text), you cannot and will  not see
> graphics.
>
> The older system with similar software runs fine from autostart. Maybe I
>> need to do here as well? I can not find autostart in the lastest Debian
>> version: it must be in a different directory that I know of.
>> Finally: if I run the original script (running fine on the older system)
>> I just get a blank screen and system halts.
>>
> If you want to use your system in graphics mode you should autostart X.
> Usually it is done by asking it to go to the graphical run state (5 in the
> old sysV init scripts, graphical.target in systemd)
> For debugging, you can type 'startx' to start X manually.
>
> --
> 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/s5Qhhc75e1c/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/CAC%3D1GgEwLf4sHO_iA%2BwGg3-
> 8YCNjy%3DJL5OZxv4prH5bPLn0Y9A%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgEwLf4sHO_iA%2BwGg3-8YCNjy%3DJL5OZxv4prH5bPLn0Y9A%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> 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/CAHmciaZapXVRMnh_mTXpKx7nyfEdK01LG%2Bi6131dQ%2BGhkpWYRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: after flashing to Debian 8.6 no gui anymore

[Harke Smits]

The gui is present if you load the Debian version indicated above. You have
to modify the uEnv.txt file. Look here:
https://mail.google.com/mail/u/0/?shva=1#inbox/159e9f22d12d2eb3
Still my current script does not work as expected in this version but the
normal gui functions do. I need to look further.
Good luck,
Harke


On 12 March 2017 at 03:37, evilwulfie <evilwul...@gmail.com> wrote:

> So install your favorite GUI.
>
> On 3/11/2017 12:28 AM, beeke...@gmail.com wrote:
>
> I am curious how you ended up on beaglebone. I had two I bought some time
> back. I flashed them both with the 8.6 and both have exactly what you
> describe. I can ssh via USB.  No GUI. I put a monitor / keybard with
> nothing.   What did you learn and what would you suggest?  I really just
> want to play with the boards. I have a Rapberry pi cluster configured and
> wanted to have the beaglebone in the mix somehow...  Anyways curious what
> you learned? did? etc.
>
> On Sunday, December 18, 2016 at 10:23:33 AM UTC-5, Harke Smits wrote:
>>
>> Dear all,
>>
>> I managed to flash a recent purchased BBB to Debian 8.6
>> (BBB-blank-debian8.6-lxqt-4gb-2016-11-27).It works (partly) as I can see
>> via Cloud 9 acces. But the gui is gone. I no longer have a graphical
>> display (4D systems) nor keyboard/mouse access (via usb dongle). The
>> display is fully lit. The board is completely accessable via Cloud9 and
>> normal linux commands work via this interface. I did an update (sudo
>> apt-get update) followed by reboot but no succes. Do I miss something?
>> Please advise. Many thanks in advance,
>> Harke
>> Btw: the Debian version of 2015-11-03 works great! (I still have the SD
>> card)
>>
> --
> 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/b160dfe7-53c2-4ea8-92f7-cdc3adf95504%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/b160dfe7-53c2-4ea8-92f7-cdc3adf95504%40googlegroups.com?utm_medium=email_source=footer>
> .
> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/beagleboard/B_qLqwXwEwo/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/17807c6e-ca1c-bd9d-cddd-ed2e2ba0db7d%40gmail.com
> <https://groups.google.com/d/msgid/beagleboard/17807c6e-ca1c-bd9d-cddd-ed2e2ba0db7d%40gmail.com?utm_medium=email_source=footer>
> .
>
> 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/CAHmciabSRj2AqF%2BPPPjM6okSmS8o6hyYvuaFEj7YX2HgXko6ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

Thanks Robert,

Now it works. I modified uEnv.txt at two places; one for the display to
work end another for the UART's to work.
Back to the application.
Regards,
Harke

On 30 January 2017 at 22:02, Robert Nelson <robertcnel...@gmail.com> wrote:

> On Mon, Jan 30, 2017 at 2:41 PM, Harke Smits <yrra...@gmail.com> wrote:
> > OK I got it working manually;
> > Fist:
> >
> > debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
> >  0: PF  -1 4D cape display variables
> >  1: PF  -1
> >  2: PF  -1
> >  3: PF  -1
> >
> > Than:
> >
> > sudo sh -c "echo 'BB-UART2' > /sys/devices/platform/bone_capemgr/slots"
> >
> > Again:
> >
> > debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
> >  0: PF  -1 etc...
> >  1: PF  -1
> >  2: PF  -1
> >  3: PF  -1
> >  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-UART2
> >
> > My testscript using UART2 now works. However, after a reboot all needs
> to be
> > done again. Not very satisfactory.
> > How can I get it installed on boot?
>
> open /boot/uEnv.txt
>
> cape_enable=bone_capemgr.enable_partno=BB-UART2
>
> 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/CAHmciaYQW2DnmR8cTj08eoOySEAazWgSFttwHJP2DLFhs4sL%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

OK I got it working manually;
Fist:

debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1 4D cape display variables
 1: PF  -1
 2: PF  -1
 3: PF  -1

Than:

sudo sh -c "echo 'BB-UART2' > /sys/devices/platform/bone_capemgr/slots"

Again:

debian@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1 etc...
 1: PF  -1
 2: PF  -1
 3: PF  -1
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-UART2

My testscript using UART2 now works. However, after a reboot all needs to
be done again. Not very satisfactory.
How can I get it installed on boot?
Please advise!
Regards,
Harke


On 29 January 2017 at 23:35, Harke Smits <yrra...@gmail.com> wrote:

> I repeated everything: same problem. BBB does not boot anymore!? Did I do
> something wrong here?
> Please advise, regards,
> Harke
>
> On 29 January 2017 at 21:36, Harke Smits <yrra...@gmail.com> wrote:
>
>> Unfortunately that crashes the system. all four blue leds on
>> I will try and reflash from mem card.
>> H
>>
>> On 29 January 2017 at 21:13, Robert Nelson <robertcnel...@gmail.com>
>> wrote:
>>
>>> On Sun, Jan 29, 2017 at 2:04 PM, Harke Smits <yrra...@gmail.com> wrote:
>>> > Hello Robert,
>>> >
>>> > Thanks for your reaction. I understand /dev/ttyOx has been replaced by
>>> > /dev/ttySx (x from 0-5). However the rest is far beyond my level of
>>> skill. I
>>> > do not know what dt overlay I load. I just flashed the latest Debian
>>> > version. And then updated all (sudo apt-get update). I do not
>>> understand C,
>>> > just a bit of Python. I need to use the UARTs 2 and 4. and of course a
>>> > number of I/O bits. I hope that is still the same? I can and are
>>> prepared to
>>> > move to the latest versions, just need to know what to do
>>>
>>> btw, you can also just do:
>>>
>>> cd /opt/scripts/tools/
>>> git pull
>>> sudo ./update_kernel.sh --bone-channel --stable
>>> sudo reboot
>>>
>>> and then you can return to the classic 3.8.13 based kernel you are use
>>> too..
>>>
>>> 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/CAHmciaYy3Bs2tO9TqS9tXvnPx-6eLWcb9Wx_Krk-YCxJwfc5WA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

I repeated everything: same problem. BBB does not boot anymore!? Did I do
something wrong here?
Please advise, regards,
Harke

On 29 January 2017 at 21:36, Harke Smits <yrra...@gmail.com> wrote:

> Unfortunately that crashes the system. all four blue leds on
> I will try and reflash from mem card.
> H
>
> On 29 January 2017 at 21:13, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>
>> On Sun, Jan 29, 2017 at 2:04 PM, Harke Smits <yrra...@gmail.com> wrote:
>> > Hello Robert,
>> >
>> > Thanks for your reaction. I understand /dev/ttyOx has been replaced by
>> > /dev/ttySx (x from 0-5). However the rest is far beyond my level of
>> skill. I
>> > do not know what dt overlay I load. I just flashed the latest Debian
>> > version. And then updated all (sudo apt-get update). I do not
>> understand C,
>> > just a bit of Python. I need to use the UARTs 2 and 4. and of course a
>> > number of I/O bits. I hope that is still the same? I can and are
>> prepared to
>> > move to the latest versions, just need to know what to do
>>
>> btw, you can also just do:
>>
>> cd /opt/scripts/tools/
>> git pull
>> sudo ./update_kernel.sh --bone-channel --stable
>> sudo reboot
>>
>> and then you can return to the classic 3.8.13 based kernel you are use
>> too..
>>
>> 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/CAHmciaYAMNbeW%2BzHUyMr35JwYu05wyWY44T2XOj0VfyrcJFptg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

Unfortunately that crashes the system. all four blue leds on
I will try and reflash from mem card.
H

On 29 January 2017 at 21:13, Robert Nelson <robertcnel...@gmail.com> wrote:

> On Sun, Jan 29, 2017 at 2:04 PM, Harke Smits <yrra...@gmail.com> wrote:
> > Hello Robert,
> >
> > Thanks for your reaction. I understand /dev/ttyOx has been replaced by
> > /dev/ttySx (x from 0-5). However the rest is far beyond my level of
> skill. I
> > do not know what dt overlay I load. I just flashed the latest Debian
> > version. And then updated all (sudo apt-get update). I do not understand
> C,
> > just a bit of Python. I need to use the UARTs 2 and 4. and of course a
> > number of I/O bits. I hope that is still the same? I can and are
> prepared to
> > move to the latest versions, just need to know what to do
>
> btw, you can also just do:
>
> cd /opt/scripts/tools/
> git pull
> sudo ./update_kernel.sh --bone-channel --stable
> sudo reboot
>
> and then you can return to the classic 3.8.13 based kernel you are use
> too..
>
> 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/CAHmciabCvHYP4FxDHO0550Tyapb0qwZKMeiTOx5hgMdOtpwZNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

Hello Robert,

Thanks for your reaction. I understand /dev/ttyOx has been replaced by
/dev/ttySx (x from 0-5). However the rest is far beyond my level of skill.
I do not know what dt overlay I load. I just flashed the latest Debian
version. And then updated all (sudo apt-get update). I do not understand C,
just a bit of Python. I need to use the UARTs 2 and 4. and of course a
number of I/O bits. I hope that is still the same? I can and are prepared
to move to the latest versions, just need to know what to do
Regards,
Harke

On 29 January 2017 at 20:03, Robert Nelson <robertcnel...@gmail.com> wrote:

> On Sun, Jan 29, 2017 at 12:50 PM, Harke Smits <yrra...@gmail.com> wrote:
> > Hello Dennis,
> >
> > That is a very relevant reaction! Thanks a lot! Now I have to find out
> what
> > port is connected with UART 2 (and others I need). I found ttyO0 and
> > ttyO3 working, i.e. no errors reported. But also no idea to what UART
> they
> > are connected. Definitely not UART2, I am using.
> > Apart from the fact that I cannot believe that someone deliberately
> messed
> > up with the serial ports. Compatibility with earlier scripts is
> > completely gone!
> > Can anyone supply me with the altest UART mapping? Or better yet:
> re-install
> > the old mapping?
>
> Well, userspace changed from: /dev/ttyOx -> /dev/ttySx, by default we
> have a udev rule setup to allow you to use /dev/ttyOx
>
> However if you are loading a device tree overlay from the 3.8.13 era,
> you need to update the device tree node name.
>
> for example usart 2: (today)
>
> https://github.com/beagleboard/bb.org-overlays/
> blob/master/src/arm/BB-UART2-00A0.dts#L47
>
> usart2 (yesterday with 3.8.13)
>
> https://github.com/beagleboard/linux/blob/3.8/
> firmware/capes/BB-UART2-00A0.dts#L41
>
> As you might have other issues causing the blockage, please add the output
> off
>
> dmesg | grep bone
>
> 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/CAHmciabhdh92RjbOCgcq-wiyuN7fOf%3D%3DVy-MoXf_Td_7vYYTLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: pyserial stopped working after Debian update?

[Harke Smits]

Hello Dennis,

That is a very relevant reaction! Thanks a lot! Now I have to find out what
port is connected with UART 2 (and others I need). I found ttyO0 and
ttyO3 working, i.e. no errors reported. But also no idea to what UART they
are connected. Definitely not UART2, I am using.
Apart from the fact that I cannot believe that someone deliberately messed
up with the serial ports. Compatibility with earlier scripts is
completely gone!
Can anyone supply me with the altest UART mapping? Or better yet:
re-install the old mapping?
Cheers!
Harke

On 29 January 2017 at 17:04, Dennis Lee Bieber <wlfr...@ix.netcom.com>
wrote:

> On Sun, 29 Jan 2017 03:17:51 -0800 (PST), Harke Smits
> <yrra...@gmail.com> declaimed the following:
>
>
> >pyserial, if necessary. Now my old script does not work anymore. It leaves
> >me with error; Errno 2: could not open port /dev/ttyO2. No such file or
> >directory. Do I miss something here? What else do I need to do?
>
> Well, first thing: do you HAVE a ttyO2 in /dev? I don't -- using a
> "Wheezy" image from last summer, I'll dig up the SD card with "Jessie" in a
> moment... (apologies for the bad wrapping)
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 3.8.13-bone80 #1 SMP Wed Jun 15 17:03:55 UTC 2016 armv7l
> GNU/Linux
> debian@beaglebone:~$ ls /dev/tty*
> /dev/tty/dev/tty16  /dev/tty24  /dev/tty32  /dev/tty40  /dev/tty49
> /dev/tty57  /dev/tty8
> /dev/tty0   /dev/tty17  /dev/tty25  /dev/tty33  /dev/tty41  /dev/tty5
> /dev/tty58  /dev/tty9
> /dev/tty1   /dev/tty18  /dev/tty26  /dev/tty34  /dev/tty42  /dev/tty50
> /dev/tty59  /dev/ttyGS0
> /dev/tty10  /dev/tty19  /dev/tty27  /dev/tty35  /dev/tty43  /dev/tty51
> /dev/tty6   /dev/ttyO0
> /dev/tty11  /dev/tty2   /dev/tty28  /dev/tty36  /dev/tty44  /dev/tty52
> /dev/tty60  /dev/ttyS0
> /dev/tty12  /dev/tty20  /dev/tty29  /dev/tty37  /dev/tty45  /dev/tty53
> /dev/tty61  /dev/ttyS1
> /dev/tty13  /dev/tty21  /dev/tty3   /dev/tty38  /dev/tty46  /dev/tty54
> /dev/tty62  /dev/ttyS2
> /dev/tty14  /dev/tty22  /dev/tty30  /dev/tty39  /dev/tty47  /dev/tty55
> /dev/tty63  /dev/ttyS3
> /dev/tty15  /dev/tty23  /dev/tty31  /dev/tty4   /dev/tty48  /dev/tty56
> /dev/tty7
> debian@beaglebone:~$
>
> I show ttyS0 .. ttyS3
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l
> GNU/Linux
> debian@beaglebone:~$ ls /dev/tty*
> /dev/tty/dev/tty17  /dev/tty26  /dev/tty35  /dev/tty44  /dev/tty53
> /dev/tty62   /dev/ttyS0
> /dev/tty0   /dev/tty18  /dev/tty27  /dev/tty36  /dev/tty45  /dev/tty54
> /dev/tty63   /dev/ttyS1
> /dev/tty1   /dev/tty19  /dev/tty28  /dev/tty37  /dev/tty46  /dev/tty55
> /dev/tty7/dev/ttyS2
> /dev/tty10  /dev/tty2   /dev/tty29  /dev/tty38  /dev/tty47  /dev/tty56
> /dev/tty8/dev/ttyS3
> /dev/tty11  /dev/tty20  /dev/tty3   /dev/tty39  /dev/tty48  /dev/tty57
> /dev/tty9/dev/ttyS4
> /dev/tty12  /dev/tty21  /dev/tty30  /dev/tty4   /dev/tty49  /dev/tty58
> /dev/ttyGS0  /dev/ttyS5
> /dev/tty13  /dev/tty22  /dev/tty31  /dev/tty40  /dev/tty5   /dev/tty59
> /dev/ttyO0
> /dev/tty14  /dev/tty23  /dev/tty32  /dev/tty41  /dev/tty50  /dev/tty6
> /dev/ttyO1
> /dev/tty15  /dev/tty24  /dev/tty33  /dev/tty42  /dev/tty51  /dev/tty60
> /dev/ttyO2
> /dev/tty16  /dev/tty25  /dev/tty34  /dev/tty43  /dev/tty52  /dev/tty61
> /dev/ttyO4
> debian@beaglebone:~$
>
>
> Interesting -- Jessie (from last fall) shows both ttyO0/1/2/4 AND
> ttyS0/1/2/3/4/5
>
> debian@beaglebone:~$ ls -l /dev/ttyO*
> lrwxrwxrwx 1 root root 5 Dec 10 12:31 /dev/ttyO0 -> ttyS0
> lrwxrwxrwx 1 root root 5 Jan 29 10:57 /dev/ttyO1 -> ttyS1
> lrwxrwxrwx 1 root root 5 Jan 29 10:57 /dev/ttyO2 -> ttyS2
> lrwxrwxrwx 1 root root 5 Jan 29 10:57 /dev/ttyO4 -> ttyS4
> debian@beaglebone:~$ ls -l /dev/ttyS*
> crw--w 1 root tty 4, 64 Dec 10 12:32 /dev/ttyS0
> crw-rw 1 root dialout 4, 65 Jan 29 10:57 /dev/ttyS1
> crw-rw 1 root dialout 4, 66 Jan 29 10:57 /dev/ttyS2
> crw-rw 1 root dialout 4, 67 Dec 10 12:32 /dev/ttyS3
> crw-rw 1 root dialout 4, 68 Jan 29 10:57 /dev/ttyS4
> crw-rw 1 root dialout 4, 69 Dec 10 12:32 /dev/ttyS5
>
> Though the ttyO* are just links to the ttyS*
>
> Maybe in a month or so I'll have time to flash the eMMC up to
> Jessie,
> and set the SD cards to newer releases. (I prefer to keep the eMMC on an
> older working config)
>
> --
> Wulfraed Dennis Lee Bieber AF6VN
> wlfr...@ix.netcom.comHTTP://wlfraed.home.netcom.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
>

[beagleboard] pyserial stopped working after Debian update?

[Harke Smits]

Learned group,

Recently I updated (flashed) my Debian version from 2015-11-12 to Debian 
2017-01-22. The hw rest unchanged: BBB, 4D systems display and a universal 
board only to interface a simple N8M GPS receiver. I have a very simple 
Python script to read UART2 connected to the GPS receiver and show some 
lines of NMEA. In the old Debian version this (and my other applications) 
work good. At first the display did not work either, but I found I had to 
uncomment a line in uEnv.txt. The gui apparently has been changed. So 
far so good. I also did: sudo apt-get update and installed Adafruit and 
pyserial, if necessary. Now my old script does not work anymore. It leaves 
me with error; Errno 2: could not open port /dev/ttyO2. No such file or 
directory. Do I miss something here? What else do I need to do?
Please advise.
Thanks in advance,
Harke

-- 
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/396f0ce1-a593-4d48-8ee2-01681b32dd71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] after flashing to Debian 8.6 no gui anymore

[Harke Smits]

Dear all,

I managed to flash a recent purchased BBB to Debian 8.6 
(BBB-blank-debian8.6-lxqt-4gb-2016-11-27).It works (partly) as I can see 
via Cloud 9 acces. But the gui is gone. I no longer have a graphical 
display (4D systems) nor keyboard/mouse access (via usb dongle). The 
display is fully lit. The board is completely accessable via Cloud9 and 
normal linux commands work via this interface. I did an update (sudo 
apt-get update) followed by reboot but no succes. Do I miss something? 
Please advise. Many thanks in advance,
Harke
Btw: the Debian version of 2015-11-03 works great! (I still have the SD 
card)

-- 
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/6ddc0b75-55a2-4428-b982-9d7ef883fdba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB, Debian, Chipsee display: Tkinter gives error

[Harke Smits]

Hello David and John,

Thanks for your reactions. Sorry for the delay, was occupied with some
other duties like skiing
echo $DISPLAY from the debian command line returns nothing (a blank line).
The same command form the debian command line coming from the LXDE
interface gives: :0. So I issue the sudo python myprog.py command after the
LXDE shell has been loaded: that works for me.I need sudo because of the
Adafruit library, but I suppose that is another story.
Would be great to run the program without LXDE but I guess that will not
work.
The next problem is: how to run the program automatically upon start-up. I
prefer without LXDE but I am afraid that is not possible. So I need to
start myprog.py form a kind of start-up script
Btw: what is X11? The link is not terribly clear for me as a novice...

Best regards,
Harke


On Sat, Mar 26, 2016 at 10:01 PM, David Good <david.go...@gmail.com> wrote:

> It looks like you need to set the DISPLAY environment variable so that
> tkinter knows which display to use.
>
> Is X11 installed on the BBB?
>
> On my linux machine, when I try echo $DISPLAY, I get ":0.0" without the
> quotes.
>
> What happens if you run that command?
>
> You might check out some of the info on this page as well.
>
>
> http://unix.stackexchange.com/questions/17255/is-there-a-command-to-list-all-open-displays-on-a-machine
>
> --David
>
> On Sat, Mar 26, 2016 at 1:59 PM, John Baker <bakerengineerin...@gmail.com>
> wrote:
>
>> Harke:
>> Another in the Learned Group, I think it was Steve Plant but I can't find
>> the post, suggested connecting a keyboard and mouse to the BBB and running
>> the Python program with 'sudo python your_python_program'. That worked
>> great for me. I never would have thought of it. My code is a GUI with
>> buttons, text boxes and an animation graph running Tkinter and also running
>> PyBBIO for PWM output and ADC inputs.
>> John
>> johnbakeree.blogspot.com
>>
>> On Saturday, February 13, 2016 at 3:07:04 AM UTC-8, Harke Smits wrote:
>>>
>>> Hello Learned Group,
>>>
>>> I have a BBB running Debian (2015-11-03 version) with a Chipsee 4.3
>>> display. It works great, so far so good: both in graphic mode and text. I
>>> try to script an application requiring a GUI, so I loaded Tkinter and
>>> entered a test program.
>>> This is the result:
>>>
>>> Traceback (most recent call last):
>>>   File "testtk.py", line 2, in 
>>> root = Tkinter.Tk()
>>>   File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1712, in __init__
>>> self.tk = _tkinter.create(screenName, baseName, className,
>>> interactive, wantobjects, useTk, sync, use)
>>> _tkinter.TclError: no display name and no $DISPLAY environment variable
>>> root@beaglebone:/home/apptest#
>>>
>>> Its the same whether I run from BBB via bash or via another pc with
>>> Cloud9.
>>>
>>> I googled a lot and the error is not uncommon, but could not find a clue
>>> for my case.
>>>
>>> Please advise, regards,
>>> Harke
>>>
>> --
>> 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.
>> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/w7vDlQctKD8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB, Debian, Chipsee display: Tkinter gives error

[Harke Smits]

Hello Learned Group,

I have a BBB running Debian (2015-11-03 version) with a Chipsee 4.3 
display. It works great, so far so good: both in graphic mode and text. I 
try to script an application requiring a GUI, so I loaded Tkinter and 
entered a test program.
This is the result:

Traceback (most recent call last):
  File "testtk.py", line 2, in 
root = Tkinter.Tk()
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1712, in __init__
self.tk = _tkinter.create(screenName, baseName, className, interactive, 
wantobjects, useTk, sync, use)
_tkinter.TclError: no display name and no $DISPLAY environment variable
root@beaglebone:/home/apptest# 

Its the same whether I run from BBB via bash or via another pc with Cloud9.

I googled a lot and the error is not uncommon, but could not find a clue 
for my case. 

Please advise, regards,
Harke

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

[beagleboard] Beaglebone Black, Chipsee and Python

[Harke Smits]

Dear experienced group,

I am looking for control software in Python for a 4.3 inch Chipsee display. 
I have installed Debian 7.9 LXDE 2015-11-03, that works very well, with the 
display (the browser works great, touching works, reset button works) and 
with other I/O control software, from me in Python. For my application I 
want to control the display via Python. I googled but found not very 
usefull info. It looks like the manufacturer has provided an old version of 
the os, but as my current version works well, and I have lost a lot of time 
with older versions, I am very reluctant to change the Debian version. Even 
then I see no Python support at all. Is there a more generic solution?
What is the best way to proceed?
Any help greatly appreciated,
Harke

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

Re: [beagleboard] Re: no acces to UART* anymore after flashing new Debian version

[Harke Smits]

Hello,

Thanks for your comment.
Its getting exciting. I tried to follow the recipe. I started with sudo -i to 
have all rights. Then I loaded the dtb library in the rebuilder folder. Works. 
Then nano am335x-boneblack.dts, but I do not know enough of C. #include is 
comment or not? So i left the file unmodified. I run make, no problem. I run 
make install, no problem either, but, I reboot and the BBB stucks with all leds 
on.
Then I remount the usd card and reload the os. That runs fine after a while. I 
can repeat this of course but does not bring me further..
So please explain to me what I need to do with the amdts file and please 
explain what make does ( I expect short for dtc??) . 
Do hope you can help me out?
I owe you one!

Harke

(Send from my iPad4)

 Op 22 mei 2015 om 22:54 heeft glsl...@gmail.com het volgende geschreven:
 
 You need to edit the file to uncomment the includes for the serial devices 
 (ttyO1 and so on). git status should then give you the difference of your 
 edits against the repository.
 
 On Friday, May 22, 2015 at 11:49:49 AM UTC+1, Harke Smits wrote:
 Thanks a lot for the pointer! Yes, I'm afraid, I need that. As a newbie I 
 was not aware that upgrading the OS was so invasive
 I followed the recipe and after:
 git status,  I get: (something like) nothing to commit.
 I could find the file am335x-boneblack.dts but then I get lost.
 Getting exiting.
 Can someone clear me up in newbie language?
 Thanks a lot in advance! (I need serial data for my project)
 Harke
 
 
 
  
 
 On Wed, May 20, 2015 at 11:57 PM, gls...@gmail.com wrote:
 I may have misunderstood but have a look here on how to enable UARTs for 
 Jessie.
 
 https://theunemployablekoder.wordpress.com/
 
 
 On Wednesday, May 20, 2015 at 1:10:00 PM UTC+1, Harke Smits wrote:
 I recently had to re-install Debian. After some trials it flashed 
 correctly. But now I have no access to the UARTs anymore. Not via uEnv.txt 
 (located in /boot and not in /boot/uboot, for this version), nor via 
 Python. Both have worked fine before. Do I also need a newer version of 
 Adafruit, maybe? Or something else I have overlooked?
 
 I hope one of you can help me out.
 
 Cheers,
 Harke
 
 -- 
 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/JBVNPDCavlc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 beagleboard...@googlegroups.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 a topic in the Google 
 Groups BeagleBoard group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/beagleboard/JBVNPDCavlc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: no acces to UART* anymore after flashing new Debian version

[Harke Smits]

Thanks a lot for the pointer! Yes, I'm afraid, I need that. As a newbie I
was not aware that upgrading the OS was so invasive
I followed the recipe and after:
git status,  I get: (something like) nothing to commit.
I could find the file am335x-boneblack.dts but then I get lost.

Can someone clear me up in newbie language?
Thanks a lot in advance! (I need serial data for my project)
Harke





On Wed, May 20, 2015 at 11:57 PM, glsl...@gmail.com wrote:

 I may have misunderstood but have a look here on how to enable UARTs for
 Jessie.

 https://theunemployablekoder.wordpress.com/


 On Wednesday, May 20, 2015 at 1:10:00 PM UTC+1, Harke Smits wrote:

 I recently had to re-install Debian. After some trials it flashed
 correctly. But now I have no access to the UARTs anymore. Not via uEnv.txt
 (located in /boot and not in /boot/uboot, for this version), nor via
 Python. Both have worked fine before. Do I also need a newer version of
 Adafruit, maybe? Or something else I have overlooked?

 I hope one of you can help me out.

 Cheers,
 Harke

  --
 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/JBVNPDCavlc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] no acces to UART* anymore after flashing new Debian version

[Harke Smits]

I recently had to re-install Debian. After some trials it flashed 
correctly. But now I have no access to the UARTs anymore. Not via uEnv.txt 
(located in /boot and not in /boot/uboot, for this version), nor via 
Python. Both have worked fine before. Do I also need a newer version of 
Adafruit, maybe? Or something else I have overlooked?

I hope one of you can help me out.

Cheers,
Harke

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

Re: [beagleboard] Re: Beaglebone root access

[Harke Smits]

I guess so too. I did in fact (with some trouble) and sudo -i works as
before.

Thanks!
Harke

On Mon, May 18, 2015 at 6:11 PM, William Hermans yyrk...@gmail.com wrote:

 Sounds like it is time for you to try out a new image . . .

 On Mon, May 18, 2015 at 8:50 AM, Harke Smits yrra...@gmail.com wrote:

 sudo -i also does not work anymore.


 On Monday, 18 May 2015 15:07:29 UTC+2, Harke Smits wrote:

 Hello,

 I must have done something stupid because all of a sudden /root is no
 longer existing or better probably: no more accessible.
 The ls command result starts with /bin . ends with /usr. But no
 /root anymore.
 Very annoying of course. I also no longer have access to IO pins.

 Please help.

 Thanks in advance
 Harke




  --
 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.
 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 a topic in the
 Google Groups BeagleBoard group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/beagleboard/nJPMi1n2WIg/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 beagleboard+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone root access

[Harke Smits]

Hello,

I must have done something stupid because all of a sudden /root is no 
longer existing or better probably: no more accessible. 
The ls command result starts with /bin . ends with /usr. But no /root 
anymore.
Very annoying of course. I also no longer have access to IO pins.

Please help.

Thanks in advance
Harke


  

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

[beagleboard] Re: Beaglebone root access

[Harke Smits]

sudo -i also does not work anymore.

On Monday, 18 May 2015 15:07:29 UTC+2, Harke Smits wrote:

 Hello,

 I must have done something stupid because all of a sudden /root is no 
 longer existing or better probably: no more accessible. 
 The ls command result starts with /bin . ends with /usr. But no /root 
 anymore.
 Very annoying of course. I also no longer have access to IO pins.

 Please help.

 Thanks in advance
 Harke


   


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