[beagleboard] How can remove the write-protection on the BeagleBone ?

[Ichrak Mansour]

I'm using the Beaglebone in IoT mode with the latest debian image.

I tried to modify the name of the Beaglebone disk and modifying its icon, 
as I need to modify start.htm, when I try to modify it or copy an image, an 
alert is displayed this disk is write-protected, 

so how can I remove this protection? and how can Ichange start.htm?

-- 
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/895ca350-e5bf-4968-b349-02a2cb6ee63c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Linux Kernel failed to build: ERROR: no certificate subject alternative name matches

[not you]

I am following this guide to install Linaro on my Ubuntu 18.04 machine:
https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-ARMCrossCompiler:GCC
 


Thanks to Robert's help, I got Linaro 7.3.1 successfully installed.  I am 
now stuck at building the Linux Kernel.  I checked out the long term / 
real-time branch using:

git checkout origin/am33x-rt-v4.9 -b tmp

And proceed to building it:

./build_kernel.sh

It failed to build, giving out these status report:

+ Detected build host [Ubuntu 18.04.1 LTS]
+ host: [x86_64]
+ git HEAD commit: [3a7726562a52a27d7712b5eb4cbe4a2f31890ac6]
Installing: 
-
--2018-08-30 15:32:01--  
https://releases.linaro.org/components/toolchain/binaries/6.4-2018.05/arm-linux-gnueabihf/gcc-linaro-6.4.1-2018.05-x86_64_arm-linux-gnueabihf.tar.xz
Resolving releases.linaro.org (releases.linaro.org)... 13.228.101.204
Connecting to releases.linaro.org 
(releases.linaro.org)|13.228.101.204|:443... connected.
ERROR: no certificate subject alternative name matches
requested host name ‘releases.linaro.org’.
To connect to releases.linaro.org insecurely, use `--no-check-certificate'.
--2018-08-30 15:32:01--  
https://releases.linaro.org/archive/components/toolchain/binaries/6.4-2018.05/arm-linux-gnueabihf/gcc-linaro-6.4.1-2018.05-x86_64_arm-linux-gnueabihf.tar.xz
Resolving releases.linaro.org (releases.linaro.org)... 13.228.101.204
Connecting to releases.linaro.org 
(releases.linaro.org)|13.228.101.204|:443... connected.
ERROR: no certificate subject alternative name matches
requested host name ‘releases.linaro.org’.
To connect to releases.linaro.org insecurely, use `--no-check-certificate'.

So I got a few questions:
1. It installs Linaro 6.4.1 tho I already have 7.3.1.  Why does this 
happen? 
2. What should I do to get it built?

-- 
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/fbae6ff8-49e5-45de-a7cb-107234c70278%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Need a HELP ! How to remove the write protection of Beaglebone ?

[Ichrak Mansour]

Hello,
I need a help please, I want to change the name of the label of my 
BeagleBone when I connect it with PC and edit the file start.htm.

I try that, but it have a protection of write, how can I remove this 
protection or have you another solution to be able writing on the 
beaglebone ? 


-- 
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/6306520d-246b-4602-9eac-1bb392e9572f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beagle bone, comms issue

[Shak Jamil]

I am using Node red to program the beagle bone and now not getting any data 
to the dashboard after connecting the DC supply along with the USB cable. 
Does anyone know if this would cause damage to the unit ?


-- 
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/2fde487c-feb4-4ac1-b9da-71192352bad1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beagle bone, comms issue

[evilwulfie]

normally not. unless there is something wrong with your grounding or
power supply

On 8/30/2018 5:00 AM, Shak Jamil wrote:
> I am using Node red to program the beagle bone and now not getting any
> data to the dashboard after connecting the DC supply along with the
> USB cable. Does anyone know if this would cause damage to the unit ?
>
>
> -- 
> 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/2fde487c-feb4-4ac1-b9da-71192352bad1%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/8bb5e252-a631-8606-a914-1ab942e603e1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Linux Kernel failed to build: ERROR: no certificate subject alternative name matches

[Robert Nelson]

On Thu, Aug 30, 2018 at 3:48 AM not you  wrote:
>
> I am following this guide to install Linaro on my Ubuntu 18.04 machine:
> https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-ARMCrossCompiler:GCC
>
> Thanks to Robert's help, I got Linaro 7.3.1 successfully installed.  I am now 
> stuck at building the Linux Kernel.  I checked out the long term / real-time 
> branch using:
>
> git checkout origin/am33x-rt-v4.9 -b tmp
>
> And proceed to building it:
>
> ./build_kernel.sh
>
> It failed to build, giving out these status report:
>
> + Detected build host [Ubuntu 18.04.1 LTS]
> + host: [x86_64]
> + git HEAD commit: [3a7726562a52a27d7712b5eb4cbe4a2f31890ac6]
> Installing:
> -
> --2018-08-30 15:32:01--  
> https://releases.linaro.org/components/toolchain/binaries/6.4-2018.05/arm-linux-gnueabihf/gcc-linaro-6.4.1-2018.05-x86_64_arm-linux-gnueabihf.tar.xz
> Resolving releases.linaro.org (releases.linaro.org)... 13.228.101.204
> Connecting to releases.linaro.org 
> (releases.linaro.org)|13.228.101.204|:443... connected.
> ERROR: no certificate subject alternative name matches
> requested host name ‘releases.linaro.org’.
> To connect to releases.linaro.org insecurely, use `--no-check-certificate'.
> --2018-08-30 15:32:01--  
> https://releases.linaro.org/archive/components/toolchain/binaries/6.4-2018.05/arm-linux-gnueabihf/gcc-linaro-6.4.1-2018.05-x86_64_arm-linux-gnueabihf.tar.xz
> Resolving releases.linaro.org (releases.linaro.org)... 13.228.101.204
> Connecting to releases.linaro.org 
> (releases.linaro.org)|13.228.101.204|:443... connected.
> ERROR: no certificate subject alternative name matches
> requested host name ‘releases.linaro.org’.
> To connect to releases.linaro.org insecurely, use `--no-check-certificate'.
>
> So I got a few questions:
> 1. It installs Linaro 6.4.1 tho I already have 7.3.1.  Why does this happen?

How does it know you have 7.3.1 installed?

> 2. What should I do to get it built?

Read system.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/CAOCHtYj%2B44dq%2BNGzZe_%3DuRstMb4bkM7jmntLatfa2LG2nhKYhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Need a HELP ! How to remove the write protection of Beaglebone ?

[Robert Nelson]

On Thu, Aug 30, 2018 at 6:41 AM Ichrak Mansour
 wrote:
>
> Hello,
> I need a help please, I want to change the name of the label of my BeagleBone 
> when I connect it with PC and edit the file start.htm.
>
> I try that, but it have a protection of write, how can I remove this 
> protection or have you another solution to be able writing on the beaglebone ?

Which of your 3 emails should i reply to?

Yes, it's RO but the answer is complex, to change it, i want to make
sure i reply to the correct thread, that way users can use the search
functionality to find the answer on their own...

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

Re: [beagleboard] Linux Kernel failed to build: ERROR: no certificate subject alternative name matches

[not you]

On Thursday, August 30, 2018 at 9:04:37 PM UTC+7, RobertCNelson wrote:
>
> > 1. It installs Linaro 6.4.1 tho I already have 7.3.1.  Why does this 
> happen? 
>
> How does it know you have 7.3.1 installed? 


I did the first part and get Linaro 7.3.1 instead.  Testing with ${CC}gcc 
succeeded, so I suppose that is the case.   Am I doing it wrong?

-- 
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/f189d6f9-3815-45d7-ba40-b7baeff9b5bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Linux Kernel failed to build: ERROR: no certificate subject alternative name matches

[Robert Nelson]

>> > 1. It installs Linaro 6.4.1 tho I already have 7.3.1.  Why does this 
>> > happen?
>>
>> How does it know you have 7.3.1 installed?
>
> I did the first part and get Linaro 7.3.1 instead.  Testing with ${CC}gcc 
> succeeded, so I suppose that is the case.   Am I doing it wrong?

That was for building u-boot... Currently the kernel build script does
not parse the environment variable CC.. I suppose it "could" with some
patches written, but today NOPE..

So if you want to bypass the pre-choosen compiler you need to open
"system.sh" and see the examples, then correctly add your's..

#ARM GCC CROSS Compiler:
#if CC is not set, a known working linaro based gcc compiler will be
downloaded and utilized.
#CC=/bin/arm-none-eabi-
#CC=/bin/arm-linux-gnueabi-
#CC=/bin/arm-linux-gnueabihf-

It has some error detection, so if you don't properly set the
path/etc, it will just default to the build-in version..

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

Re: [beagleboard] BeagleBone Black GPS PPS and Chrony for time sync

[Thomas]

I have re-imaged my BBB and made the correction to the typo in my overlay file. 
 However, it appears as if I am having the same issue.  When I install the 
overlay in the uEnv.txt file and reboot, I am never able to ssh back into the 
BBB.  

My file is below for your review.  I can't seem to find any problems with it, 
and seem to be stuck again.  Do you have any recommendations on how to proceed?

/dts-v1/;
/plugin/;

#include 
#include 
#include 

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black", 
"ti,beaglebone-green";

/* identification */
part-number = "CLOCK";
version = "00A0";

exclusive-use =
"P9.12", "P9.24", "P9.26", "uart1"; // gps and pps

fragment@0 {
target = <&ocp>;
__overlay__ {
P9_12_pinmux { status = "disabled"; };
P9_24_pinmux { status = "disabled"; };
P9_26_pinmux { status = "disabled"; };
};
};

fragment@1 {
target = <&am33xx_pinmux>;
__overlay__ {
bb_uart4_pins: pinmux_bb_uart1_pins {
pinctrl-single,pins = <
BONE_P9_24 (PIN_OUTPUT | MUX_MODE6)
BONE_P9_26 (PIN_INPUT | MUX_MODE6)
>;
};

bb_gps_pps_pins: pinmux_bb_gps_pps_pins {
pinctrl-single,pins = <
BONE_P9_12 (PIN_INPUT_PULLDOWN | 
MUX_MODE7)
>;
};

};
};

fragment@2 {
target = <&uart1>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&bb_uart1_pins>;
   };
};

fragment@3 {
target-path = "/";
__overlay__ {
gps_pps {
status = "okay";
compatible = "pps-gpio";
pinctrl-names = "default";
pinctrl-0 = <&bb_gps_pps_pins>;
gpios = <&gpio1 16 0>;
};
};
};

};


  On Wed, 29 Aug 2018 21:11:29 -0500 Robert Nelson 
 wrote  
 > 
 > 
 > On Wed, Aug 29, 2018, 9:05 PM Pablo Rodriguez  wrote:
 > Hi. Is posible to boot from an microsd and modify the uEnv  file on the emmc 
 > after mounting it?Sorry if i misunderstood the problem
 > Good point, yeah it is...
 > Regards,  
 >   -- 
 >  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/Qu78BPEdTtQ/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/CAOCHtYji9WG0P%3Dzg1g7-FmUkL%3DKLLKL%2Bs8V-BFeoh3KDfYPK5Q%40mail.gmail.com.
 >  For more options, visit https://groups.google.com/d/optout.
 >  


DISCLAIMER:
 This e-mail and any attachment(s) sent with it are intended exclusively for 
the addressee(s), and may not be used by, opened by, passed on to, or made 
available for use to, any person other than the addressee(s). LoneStar Tracking 
LLC rules out any and all liabilities resulting from any electronic 
transmission.
  

-- 
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/1658b483b81.11937f209417083.430832608307976159%40lonestartracking.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Black GPS PPS and Chrony for time sync

[Robert Nelson]

On Thu, Aug 30, 2018 at 10:18 AM Thomas  wrote:
>
> I have re-imaged my BBB and made the correction to the typo in my overlay 
> file.  However, it appears as if I am having the same issue.  When I install 
> the overlay in the uEnv.txt file and reboot, I am never able to ssh back into 
> the BBB.
>
> My file is below for your review.  I can't seem to find any problems with it, 
> and seem to be stuck again.  Do you have any recommendations on how to 
> proceed?

Your very close, just change one "4" to a "1".. ;)


>
> fragment@1 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> bb_uart4_pins: pinmux_bb_uart1_pins {

These don't match..

> pinctrl-0 = <&bb_uart1_pins>;

just change:

bb_uart1_pins: pinmux_bb_uart1_pins {

Then it loads correctly..

uboot_overlays: [fdt_buffer=0x6] ...
uboot_overlays: loading /lib/firmware/CLOCK.dtbo ...
1607 bytes read in 377 ms (3.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1440 bytes read in 272 ms (4.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
5127 bytes read in 149 ms (33.2 KiB/s)
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
711 bytes read in 77 ms (8.8 KiB/s)
uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo ...
3513 bytes read in 459 ms (6.8 KiB/s)

debian@beaglebone:~$ dmesg | grep pps
[0.617569] pps_core: LinuxPPS API ver. 1 registered
[0.617576] pps_core: Software ver. 5.3.6 - Copyright 2005-2007
Rodolfo Giometti 
[   40.470657] pps pps0: new PPS source gps_pps.-1
[   40.470808] pps pps0: Registered IRQ 115 as PPS source


debian@beaglebone:~$ ls /dev/pps0
/dev/pps0
debian@beaglebone:~$ sudo ppstest /dev/pps0
trying PPS source "/dev/pps0"
found PPS source "/dev/pps0"
ok, found 1 source(s), now start fetching data...
time_pps_fetch() error -1 (Connection timed out)
^C

(i don't have anything wired, so it'll time out)

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

Re: [beagleboard] BeagleBone Black GPS PPS and Chrony for time sync

[Robert Nelson]

On Thu, Aug 30, 2018 at 12:26 PM Thomas  wrote:
>
> Robert,
> I can't thank you enough for helping me through this.  There is very little 
> information available online regarding this procedure with this kernel 
> version...
>
> First, I made the edit that you recommended..  Now, the BBB reboots and I can 
> see NEMA data coming from the GPS chip.  However, when  I run PPSTEST on 
> /dev/pps0, I get the following:
>
> trying PPS source "/dev/pps0"
> found PPS source "/dev/pps0"
> ok, found 1 source(s), now start fetching data...
> time_pps_fetch() error -1 (Connection timed out)
> time_pps_fetch() error -1 (Connection timed out)
> time_pps_fetch() error -1 (Connection timed out)
> ^C
>
>
> I just measured the P9_12 pin, and I see 2.2v and a 100ms pulse width square 
> wave coming from the Adafruit GPS receiver.  Any other thoughts as to what 
> might be causing the timeout?


Just looked it up, in the pps node you have:

gpios = <&gpio1 16 0>;

However P9_12 is:

gpio1 28

So swap the 16 for 28

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

[beagleboard] new bbb eeproms

[evilwulfie]

here is something a bit different i found in one board

eeprom:[A335BNLT000C1821BBBG1067]

-- 
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/d92d2058-605b-faf6-e769-eaa536c75bc1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] new bbb eeproms

[Robert Nelson]

On Thu, Aug 30, 2018 at 1:09 PM evilwulfie  wrote:
>
> here is something a bit different i found in one board
>
> eeprom:[A335BNLT000C1821BBBG1067]

That's a GHI BeagleBone Black, made week 21 of 2018, # 1067

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

Re: [beagleboard] BeagleBone Black GPS PPS and Chrony for time sync

[Thomas]

Robert,
I can't thank you enough for helping me through this.  There is very little 
information available online regarding this procedure with this kernel 
version...

First, I made the edit that you recommended..  Now, the BBB reboots and I can 
see NEMA data coming from the GPS chip.  However, when  I run PPSTEST on 
/dev/pps0, I get the following:

trying PPS source "/dev/pps0"
found PPS source "/dev/pps0"
ok, found 1 source(s), now start fetching data...
time_pps_fetch() error -1 (Connection timed out)
time_pps_fetch() error -1 (Connection timed out)
time_pps_fetch() error -1 (Connection timed out)
^C


I just measured the P9_12 pin, and I see 2.2v and a 100ms pulse width square 
wave coming from the Adafruit GPS receiver.  Any other thoughts as to what 
might be causing the timeout?




  On Thu, 30 Aug 2018 10:28:46 -0500 Robert Nelson 
 wrote  
 > On Thu, Aug 30, 2018 at 10:18 AM Thomas  
 > wrote: 
 > > 
 > > I have re-imaged my BBB and made the correction to the typo in my overlay 
 > > file.  However, it appears as if I am having the same issue.  When I 
 > > install the overlay in the uEnv.txt file and reboot, I am never able to 
 > > ssh back into the BBB. 
 > > 
 > > My file is below for your review.  I can't seem to find any problems with 
 > > it, and seem to be stuck again.  Do you have any recommendations on how to 
 > > proceed? 
 >  
 > Your very close, just change one "4" to a "1".. ;) 
 >  
 >  
 > > 
 > > fragment@1 { 
 > > target = <&am33xx_pinmux>; 
 > > __overlay__ { 
 > > bb_uart4_pins: pinmux_bb_uart1_pins { 
 >  
 > These don't match.. 
 >  
 > > pinctrl-0 = <&bb_uart1_pins>; 
 >  
 > just change: 
 >  
 > bb_uart1_pins: pinmux_bb_uart1_pins { 
 >  
 > Then it loads correctly.. 
 >  
 > uboot_overlays: [fdt_buffer=0x6] ... 
 > uboot_overlays: loading /lib/firmware/CLOCK.dtbo ... 
 > 1607 bytes read in 377 ms (3.9 KiB/s) 
 > uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ... 
 > 1440 bytes read in 272 ms (4.9 KiB/s) 
 > uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ... 
 > 5127 bytes read in 149 ms (33.2 KiB/s) 
 > uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ... 
 > 711 bytes read in 77 ms (8.8 KiB/s) 
 > uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo ... 
 > 3513 bytes read in 459 ms (6.8 KiB/s) 
 >  
 > debian@beaglebone:~$ dmesg | grep pps 
 > [0.617569] pps_core: LinuxPPS API ver. 1 registered 
 > [0.617576] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 
 > Rodolfo Giometti  
 > [   40.470657] pps pps0: new PPS source gps_pps.-1 
 > [   40.470808] pps pps0: Registered IRQ 115 as PPS source 
 >  
 >  
 > debian@beaglebone:~$ ls /dev/pps0 
 > /dev/pps0 
 > debian@beaglebone:~$ sudo ppstest /dev/pps0 
 > trying PPS source "/dev/pps0" 
 > found PPS source "/dev/pps0" 
 > ok, found 1 source(s), now start fetching data... 
 > time_pps_fetch() error -1 (Connection timed out) 
 > ^C 
 >  
 > (i don't have anything wired, so it'll time out) 
 >  
 > Regards, 
 >  
 > --  
 > Robert Nelson 
 > https://rcn-ee.com/ 
 > 


DISCLAIMER:
 This e-mail and any attachment(s) sent with it are intended exclusively for 
the addressee(s), and may not be used by, opened by, passed on to, or made 
available for use to, any person other than the addressee(s). LoneStar Tracking 
LLC rules out any and all liabilities resulting from any electronic 
transmission.
  

-- 
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/1658bdf5ae1.fdceb56d442129.8075900310927319563%40lonestartracking.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] new bbb eeproms

[evilwulfie]

nice to know a few were programmed correctly

On 8/30/2018 11:17 AM, Robert Nelson wrote:
> On Thu, Aug 30, 2018 at 1:09 PM evilwulfie  wrote:
>> here is something a bit different i found in one board
>>
>> eeprom:[A335BNLT000C1821BBBG1067]
> That's a GHI BeagleBone Black, made week 21 of 2018, # 1067
>
> Regards,
>

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

Re: [beagleboard] BeagleBone Black GPS PPS and Chrony for time sync

[Thomas]

Perfect!  That seems to have fixed my issues!  Ill be sure to add a post on the 
web describing the procedures we went through to help others!

I do have one other question for you.  If this is out of scope, Ill ask it on 
another forum, but I figured I would start here...

Now I have confirmed that I see NEMA messages on /dev/ttyS1 and I have pps data 
on /dev/pps0.  

I next installed gpsd via apt-get and also chrony via apt-get.  

using cgps, I do have a fix, but at the bottom it flashes pps:false

32","activated":"2018-08-30T19:35:48.716Z","flags":1,"native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00,"mincycle":0.20}]}
{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false}
{

Not sure about that one, so I checked chronyc sources, and get the following:
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===
#? NMEA  0   41723   +217ms[ +217ms] +/-  109ms
#? PPS   0   4 0 - +0ns[   +0ns] +/-0ns

Any thoughts as to why chrony and/or gpsd are not seeing the pps signal?

I never told gpsd where to look for the /dev/pps0 device, but I did tell chrony 
to look at:  

# get NMEA data from gpsd over shared memory
refclock SHM 0 offset 0.395 delay 0.2 refid NMEA noselect
# get PPS data from pps-gpio, summarize every 16 seconds, prefer it
refclock PPS /dev/pps0 refid PPS poll 4 prefer


Thanks!

  On Thu, 30 Aug 2018 12:26:35 -0500 Thomas  
wrote  
 > Robert, 
 > I can't thank you enough for helping me through this.  There is very little 
 > information available online regarding this procedure with this kernel 
 > version... 
 >  
 > First, I made the edit that you recommended..  Now, the BBB reboots and I 
 > can see NEMA data coming from the GPS chip.  However, when  I run PPSTEST on 
 > /dev/pps0, I get the following: 
 >  
 > trying PPS source "/dev/pps0" 
 > found PPS source "/dev/pps0" 
 > ok, found 1 source(s), now start fetching data... 
 > time_pps_fetch() error -1 (Connection timed out) 
 > time_pps_fetch() error -1 (Connection timed out) 
 > time_pps_fetch() error -1 (Connection timed out) 
 > ^C 
 >  
 >  
 > I just measured the P9_12 pin, and I see 2.2v and a 100ms pulse width square 
 > wave coming from the Adafruit GPS receiver.  Any other thoughts as to what 
 > might be causing the timeout? 
 >  
 >  
 >  
 >  
 >   On Thu, 30 Aug 2018 10:28:46 -0500 Robert Nelson 
 >  wrote   
 >  > On Thu, Aug 30, 2018 at 10:18 AM Thomas  
 > wrote:  
 >  > >  
 >  > > I have re-imaged my BBB and made the correction to the typo in my 
 > overlay file.  However, it appears as if I am having the same issue.  When I 
 > install the overlay in the uEnv.txt file and reboot, I am never able to ssh 
 > back into the BBB.  
 >  > >  
 >  > > My file is below for your review.  I can't seem to find any problems 
 > with it, and seem to be stuck again.  Do you have any recommendations on how 
 > to proceed?  
 >  >   
 >  > Your very close, just change one "4" to a "1".. ;)  
 >  >   
 >  >   
 >  > >  
 >  > > fragment@1 {  
 >  > > target = <&am33xx_pinmux>;  
 >  > > __overlay__ {  
 >  > > bb_uart4_pins: pinmux_bb_uart1_pins {  
 >  >   
 >  > These don't match..  
 >  >   
 >  > > pinctrl-0 = <&bb_uart1_pins>;  
 >  >   
 >  > just change:  
 >  >   
 >  > bb_uart1_pins: pinmux_bb_uart1_pins {  
 >  >   
 >  > Then it loads correctly..  
 >  >   
 >  > uboot_overlays: [fdt_buffer=0x6] ...  
 >  > uboot_overlays: loading /lib/firmware/CLOCK.dtbo ...  
 >  > 1607 bytes read in 377 ms (3.9 KiB/s)  
 >  > uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...  
 >  > 1440 bytes read in 272 ms (4.9 KiB/s)  
 >  > uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...  
 >  > 5127 bytes read in 149 ms (33.2 KiB/s)  
 >  > uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...  
 >  > 711 bytes read in 77 ms (8.8 KiB/s)  
 >  > uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo 
 > ...  
 >  > 3513 bytes read in 459 ms (6.8 KiB/s)  
 >  >   
 >  > debian@beaglebone:~$ dmesg | grep pps  
 >  > [0.617569] pps_core: LinuxPPS API ver. 1 registered  
 >  > [0.617576] pps_core: Software ver. 5.3.6 - Copyright 2005-2007  
 >  > Rodolfo Giometti   
 >  > [   40.470657] pps pps0: new PPS source gps_pps.-1  
 >  > [   40.470808] pps pps0: Registered IRQ 115 as PPS source  
 >  >   
 >  >   
 >  > debian@beaglebone:~$ ls /dev/pps0  
 >  > /dev/pps0  
 >  > debian@beaglebone:~$ sudo ppstest /dev/pps0  
 >  > trying PPS source "/dev/pps0"  
 >  > found PPS source "/dev/pps0"  
 >  > ok, found 1 source(s), now start fetching data...  
 >  > time_pps_fetch() error -1 (Connection timed out)  
 >  > ^C  
 >  >   

Re: [beagleboard] BeagleBone Black GPS PPS and Chrony for time sync

[tremmert]

First off, Thanks Robert for all your help.  Looks like we are up and 
running!

Next, I wanted to post a few notes in case others run into the issues that 
I had.  

1) From a clean install, apt-get update then apt-get upgrade
2) git clone https://github.com/beagleboard/bb.org-overlays.git
3) cd bb.org-overlays/src/arm
4) Create your *.dbs file in this directory (above in thread)
5) back up two levels to /bb.org-overlays/   and issue ./install.sh
6) edit /boot/uEnv.txt and add:  
uboot_overlay_addr0=/lib/firmware/DD-GPS-00A0.dtbo
7) reboot
8) Here is some short python code to check your NMEA stream:

import serial
import Adafruit_BBIO.UART as UART
GPS = serial.Serial('/dev/ttyS1', 9600)
while(1):
while GPS.inWaiting()==0:
pass
NMEA=GPS.readline()
print NMEA

If all is well, you will see a stream of NMEA data coming across.  
9) Run pps-test /dev/pps0  to confirm you have a good pps signal
10) install gpsd from apt-get
11) gpsd -D 5 -n -N /dev/ttyS1 /dev/pps0
12) then  run cgps.  You should see a valid fix and also in the raw data at 
the bottom, several lines about pps.
13) install chrony from apt-get
14) edit config:

# change the clock slower for less jitter
minsamples 10
# get NMEA data from gpsd over shared memory
refclock SHM 0 offset 0.395 delay 0.2 refid NMEA noselect
# get PPS data from pps-gpio, summarize every 16 seconds, prefer it
#refclock PPS /dev/pps0 refid PPS poll 4 prefer
refclock PPS /dev/pps0 lock NMEA
keyfile /etc/chrony/chrony.keys
commandkey 1
driftfile /var/lib/chrony/chrony.drift
log tracking measurements statistics
logdir /var/log/chrony
maxupdateskew 100.0
dumponexit
dumpdir /var/lib/chrony
# if local stratum is configured and there's a local clock issue, the PPS 
changes stratum to match this stratum
#local stratum 10
allow
logchange 0.5
rtconutc
# change this to the proper country code
#pool us.pool.ntp.org iburst offline

Make sure you start gpsd before chronyd.

Then run chronyc sources and you should be good to go!

Thanks again for all the help!


On Thursday, August 30, 2018 at 1:45:11 PM UTC-5, Thomas wrote:
>
> Robert, 
> I can't thank you enough for helping me through this.  There is very 
> little information available online regarding this procedure with this 
> kernel version... 
>
> First, I made the edit that you recommended..  Now, the BBB reboots and I 
> can see NEMA data coming from the GPS chip.  However, when  I run PPSTEST 
> on /dev/pps0, I get the following: 
>
> trying PPS source "/dev/pps0" 
> found PPS source "/dev/pps0" 
> ok, found 1 source(s), now start fetching data... 
> time_pps_fetch() error -1 (Connection timed out) 
> time_pps_fetch() error -1 (Connection timed out) 
> time_pps_fetch() error -1 (Connection timed out) 
> ^C 
>
>
> I just measured the P9_12 pin, and I see 2.2v and a 100ms pulse width 
> square wave coming from the Adafruit GPS receiver.  Any other thoughts as 
> to what might be causing the timeout? 
>
>
>
>
>   On Thu, 30 Aug 2018 10:28:46 -0500 Robert Nelson <
> robertcnel...@gmail.com> wrote  
>  > On Thu, Aug 30, 2018 at 10:18 AM Thomas  
> wrote: 
>  > > 
>  > > I have re-imaged my BBB and made the correction to the typo in my 
> overlay file.  However, it appears as if I am having the same issue.  When 
> I install the overlay in the uEnv.txt file and reboot, I am never able to 
> ssh back into the BBB. 
>  > > 
>  > > My file is below for your review.  I can't seem to find any problems 
> with it, and seem to be stuck again.  Do you have any recommendations on 
> how to proceed? 
>  >   
>  > Your very close, just change one "4" to a "1".. ;) 
>  >   
>  >   
>  > > 
>  > > fragment@1 { 
>  > > target = <&am33xx_pinmux>; 
>  > > __overlay__ { 
>  > > bb_uart4_pins: pinmux_bb_uart1_pins { 
>  >   
>  > These don't match.. 
>  >   
>  > > pinctrl-0 = <&bb_uart1_pins>; 
>  >   
>  > just change: 
>  >   
>  > bb_uart1_pins: pinmux_bb_uart1_pins { 
>  >   
>  > Then it loads correctly.. 
>  >   
>  > uboot_overlays: [fdt_buffer=0x6] ... 
>  > uboot_overlays: loading /lib/firmware/CLOCK.dtbo ... 
>  > 1607 bytes read in 377 ms (3.9 KiB/s) 
>  > uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ... 
>  > 1440 bytes read in 272 ms (4.9 KiB/s) 
>  > uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ... 
>  > 5127 bytes read in 149 ms (33.2 KiB/s) 
>  > uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ... 
>  > 711 bytes read in 77 ms (8.8 KiB/s) 
>  > uboot_overlays: loading 
> /lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo ... 
>  > 3513 bytes read in 459 ms (6.8 KiB/s) 
>  >   
>  > debian@beaglebone:~$ dmesg | grep pps 
>  > [0.617569] pps_core: LinuxPPS API ver. 1 registered 
>  > [0.617576] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 
>  > Rodolfo Giometti  
>  > [   40.470657] pps pps0: new PPS source gps_pps.-1 
>  > [   40.470808] pp

[beagleboard] Bluetooth connection problem

[F Stanford]

Out of the box I am having great difficulty connecting my beaglebone blue 
to any other device via bluetooth using the command line bluetoothctl 
module. 

In brief, from the command line I can go into the bluetoothctl utility. 
>From there I have been able to successfully pair to my phone. I can then 
momentarily connect to my phone with this command: 
[bluetooth]# connect AC:37:43:80:C5:DD

after I verify the confirmation code from both phone and beaglebone it 
initially connects giving me this line: 
[CHG] Device AC:37:43:80:C5:DD Connected: yes

Then 10 seconds later it notifies me that I have been disconnected with 
this line: 
[CHG] Device AC:37:43:80:C5:DD Connected: no


Typing: 
[bluetooth]# info AC:37:43:80:C5:DD
Gives: 
Device AC:37:43:80:C5:DD
Name: Pixel
Alias: Pixel
Class: 0x5a020c
Icon: phone
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: OBEX Object Push  
(1105--1000-8000-00805f9b34fb)
UUID: Audio Source  
(110a--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target 
(110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control
(110e--1000-8000-00805f9b34fb)
UUID: Headset AG
(1112--1000-8000-00805f9b34fb)
UUID: PANU  
(1115--1000-8000-00805f9b34fb)
UUID: NAP  
 (1116--1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway  
 (111f--1000-8000-00805f9b34fb)
UUID: SIM Access
(112d--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server  
 (112f--1000-8000-00805f9b34fb)
UUID: Message Access Server
 (1132--1000-8000-00805f9b34fb)
UUID: PnP Information  
 (1200--1000-8000-00805f9b34fb)
UUID: Generic Access Profile
(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile 
(1801--1000-8000-00805f9b34fb)
Modalias: bluetooth:v00E0p1200d1436

I've tried to connect to a couple of different devices with the same 
results.

Linux beaglebone 4.4.59-ti-r96 #1 SMP Tue Apr 4 17:39:20 UTC 2017 armv7l 
GNU/Linux
Bluetoothctl version 5.23

I ended trying the latest June 2018 beaglebone image along with the latest 
Bluetoothctl version. But that didn't work either. I was getting 'no 
controller available' messages when I issued any command within 
bluetoothctl. 

I welcome any and all suggestions for getting through this...

Thanks. 

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

Re: [beagleboard] Re: battery power for PocketBeagle?

[Fred Kerr]

It runs well with the soldered implementation. My breadboards are a little 
cheap.

The attached minicom_20180830b.cap shows a boot with microUSB power from a 
wall wart (from my rpi3), then a boot with the battery circuit. I left both 
RX and TX attached; I'll play with disconnecting them another time.

I'll look into getting some "telemetry" info from the pocket beagle. I'm 
open to suggestions about things to add/log, etc. Also, I think this pocket 
beagle doesn't have a fix that I got before - after the shutdown, things 
panic.

If anything else jumps out from the log file, please let me know!

On Wednesday, August 29, 2018 at 10:59:03 AM UTC-7, Fred Kerr wrote:
>
> I'll try again soon with my more stable circuit (*soldered), also with RX 
> disconnected so I just get output from the Pocket Beagle and the only power 
> input is from the battery circuit. 
>
> (*Soldered, so no loose breadboard connections, better current carrying 
> capacity, etc.)
>
> What is a good way to share log files? Mine can get verbose! I could store 
> it somewhere and post a link - suggestions welcomed! I have a lot of 
> possibilities, but just let me know what works best for you.
>
> On Tuesday, August 28, 2018 at 12:51:23 PM UTC-7, Fred Kerr wrote:
>>
>> Yes, it ran quite a lot longer on the 1F, but still hung.
>>
>> I wired this up (see pic) to be more stable than the breadboard mess I 
>> had. The led on 1.8k resistor is gonna run a lot longer than I'll take at 
>> lunch!!!
>>
>> Can I isolate RX and TX or...oh I just need TX from the beagle for 
>> visibility!
>>
>> 1F 5.5v supercap (that battery was discharged to 3.96v). This one has 
>> more charge. Also put a 1000uf electrolytic on the soldered version, 
>> "because".
>>
>> Fred Kerr (mobile)
>>
>> On Tue, Aug 28, 2018, 12:13 PM Jason Kridner  wrote:
>>
>>>
>>>
>>> On Monday, August 27, 2018 at 11:15:36 PM UTC-4, Fred Kerr wrote:

 Hello all,

 I'm being just a little bit careful here:

 I'm about to try this, but I will connect up the serial terminal first, 
 so I can see output and interact with the board. (Graceful shutdown!)

>>>
>>> Don't connect the power or RX (ie., serial cable to PocketBeagle) 
>>> signals to avoid them interfering. Great thing to monitor.
>>>  
>>>

 I will test the serial connection first with just a micro USB charging 
 cable rather than USB to a computer. (Simplify!)

>>>
>>> Not sure what you are testing here. Are you just saying you'll power via 
>>> the microUSB connection and not connect to a computer, just to see the 
>>> behavior? You are monitoring with a serial connection?
>>>  
>>>

 It's my understanding that LiPo charging is disabled or not present in 
 the firmware. (I'll give you the "uname -a" and other info the next time I 
 fire it up. Just let me know what and how to check.)

>>>
>>> It is not enabled by default. There is a flag in the PMIC that needs to 
>>> be enabled. We've been playing with a driver to set the flag, but there are 
>>> other bugs in that driver not related to actually charging.
>>>  
>>>

 Also, it's not clear (without reading the data sheet :) ) about the 
 resistor values for the thermistor and the parallel (linearizing?) 
 resistor.

 If you have a 10K thermistor, do you put it in parallel with a 10K 
 resistor, or likewise 100K thermistor in parallel with a 100K resistor? Do 
 you put the thermistor anywhere in contact with the (e.g., 18650) LiPo?

>>>
>>> Looking at the TPS65217 datasheet says to put a 75kohm resistor in 
>>> parallel.
>>>
>>> I'm not sure, but I believe the actual thermal resistor should be 
>>> something like 
>>> https://www.ametherm.com/blog/thermistors/thermistors-ntc-thermistor-temperature-sensors-provide-li-ion-battery-safety/
>>> . 
>>>  
>>>

 From the prior thread, it seems to be sufficient (if even necessary) 
 just to connect a 10K resistor from TS (P2-16) to ground (P2-15).

>>>
>>> Yes, that is supposed to work, ignoring the battery temperature.
>>>  
>>>

 10uF cap from battery (P2-14) to ground (P2-15).

 (Tangent/future: What about larger cap, perhaps using a 5.5V supercap, 
 detect supercap discharging (lipo voltage to ~min input voltage on vbat) 
 and give an interrupt to shut the board down?)


 Thanks in advance for your help, and to the original thread authors!


 Other posts that I found:

 Safely power down the PocketBeagle supplied by a battery (no replies?):
 https://groups.google.com/d/msg/beagleboard/dDSD89DGzpU/j2WzZyA2CgAJ

>>>
>>> I threw in a reply.
>>>  
>>>


 Supplying two ICs from the PocketBeagle powered by a Lipo battery
 https://groups.google.com/d/msg/beagleboard/B7Zyf97hvzY/z8cOt0MHBwAJ

 I want to do some excessive self-telemetry, both internal and external. 
 I plan to scale the raw battery voltage by 1/11 with an op amp before 

[beagleboard] Re: Simple schematic editor as intuitive as grease pencil on quadrule?

[Fred Kerr]

Thanks - I've started trying fritzing. I haven't seen where the pocket 
beagle is in the core parts. Do I need to do something to install it?

I also have gEDA/gschem on my list.

Thanks!

-fek

On Wednesday, August 22, 2018 at 2:08:26 PM UTC-7, Chris Green wrote:
>
> Fred Kerr > wrote: 
> > [-- multipart/alternative, encoding 7bit, 64 lines --] 
> > 
> > [-- text/plain, encoding 7bit, charset: UTF-8, 25 lines --] 
> > 
> > Hello, 
> > 
> > Hey, Jason - your reference to the Engineer's Notebook (re: elciot18 / 
> ale) 
> > really hit a chord with me as I've thought about an electronics blog 
> > inspired by it but updated to 3.3V and 1.8V logic and other things. I 
> > haven't had bandwidth to work on it until lately, and of course, other 
> > things are starting to hop now, too! 
> > 
> > I need a really simple schematics editor, and an upgrade path after I 
> hit 
> > its limits. 
> > 
> > Do you or anyone have any suggestions? I might just use a stylus on my 
> 2in1 
> > laptop, but it would be nice to work at a slightly higher level! 
> > 
> After many years looking for something both functional adn reasonably 
> easy to use I've settled on gschem which is part of geda. 
>
> -- 
> Chris Green 
> · 
>
>

-- 
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/b40e3719-8d8b-4557-a5a7-5342875d8c8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Welcome the Fall 2018 Embedded Linux Class to this group

[Howletmj]

Hi Dr. Yoder,
I am looking forward to this quarter and seeing what we can do with the 
BeagleBone!

--Matt Howlett

On Monday, August 27, 2018 at 8:28:04 AM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *Green Wireless.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/79f8aebf-bd34-45d4-8b38-a8b00ce212c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Run Qt on Boot up

[sam . abbas3]

Hi Robert,

I am able to get it working on beagleboard using slim and openbox, but its 
not working on my beagle clone. As in my beagle clone I don't have the HDMI 
display connected at the startup, and slim does not launch. How can I get 
slim to launch even if nothing is connected at HDMI, the way lightdm does?

Thank you

On Wednesday, August 29, 2018 at 7:44:17 PM UTC-6, RobertCNelson wrote:
>
> On Wed, Aug 29, 2018 at 8:29 PM > wrote: 
> > 
> > 
> > Hi All, 
> > 
> > I am trying to run Qt program binary on boot up. I followed this 
> process: 
> https://www.stuffaboutcode.com/2012/06/raspberry-pi-run-program-at-start-up.html
>  
> > and made a script. I am able to start and stop the script and it works 
> fine, but when I enter the command "sudo update-rc.d NameOfYourScript 
> defaults"  and restart my board, it does not run at boot up. 
> > How can I make my script run at boot up? 
> > 
> > I would really appreciate any help. 
>
> Just use slim and openbox, see what i did here: 
>
>
> https://www.digikey.com/eewiki/display/linuxonarm/FLIR+Lepton+on+BeagleBone+Black+and+Green
>  
>
> Once tuned correctly, your qt app will be up within 15seconds of power 
> on.. 
>
> 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/1fde0ae4-c909-4995-969b-3b148651777e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Linux Kernel failed to build: ERROR: no certificate subject alternative name matches

[not you]

I edited system.sh to have the full link to Linaro 7.3.1.  When building 
the kernel, there is a blue screen coming up.  What should I do with it?

-- 
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/ae514548-910a-4991-a6e5-909822cb6ea2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.