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

[Mala Dies]

Hello,

Look 
here: 
https://www.freedesktop.org/software/systemd/man/systemd.service.html#Examples. 
I think you may need to rummage around in that site to look up your 
particular need but I am sure you can find what you are looking to gain on 
that site.

Seth

P.S. If you are having complications still, please reply. I will look up 
some items on your reply transmission. Okay! I hope to hear from you soon. 

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/4ca5d799-3368-4782-bbd7-9ee40403cf33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Mala Dies]

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/3affb214-a656-48bd-9517-c112cd88f0fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Minecraft Server

[youbick2018]

I just got a free Minecraft code from https://freeminecraft.cc

On Tuesday, November 6, 2018 at 8:04:31 AM UTC-8, fika...@gmail.com wrote:
>
> https://www.youtube.com/watch?v=2x6gBc9qKjM&t=9s
>
> On Saturday, May 12, 2012 at 11:30:11 PM UTC+7, Soranne wrote:
>>
>> Does anyone know if it is possible to run a Minecraft Server on the 
>> beaglebone? and how?
>> I mean the server needs a lot of RAM, is there anyway to compile java for 
>> arm so that is quicker on anything like that?
>> Because i know that some people have managed to run one on the raspberry 
>> pi...
>>
>> Thank you
>>
>

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

Re: [beagleboard] How to use P9_19 / disable i2c2?

[Robert Nelson]

On Fri, Nov 30, 2018 at 12:30 AM Ken Shirriff  wrote:
>
> Thanks, Robert. The make worked, but I can't seem to get an overlay to load 
> at all using u-boot. I had moved to a modern u-boot kernel and the overlay I 
> put into dtb_overlay in /boot/uEnv.txt doesn't get loaded, but I don't see 
> any errors in the log either. How do I debug this in the post-capemgr world? 
> I've tried a bunch of different overlays and settings but nothing seems to 
> work. Is there some trick to loading an overlay with u-boot?
>
> Next, I reinstalled the kernel in case I'd messed up something along the way. 
> Now when I try to install a simple overlay with 
> "uboot_overlay_addr4=/lib/firmware/TEST-00A0.dtbo", it completely hangs 
> during boot, so I'm making negative progress here. Now I get a bunch of 
> overlay errors during boot:
> loading /boot/dtbs/4.14.71-ti-r80/am335x-boneblack-uboot-univ.dtb ...
> 161723 bytes read in 80 ms (1.9 MiB/s)
> uboot_overlays: [fdt_buffer=0x6] ...
> uboot_overlays: loading /lib/firmware/TEST-00A0.dtbo ...
> 824 bytes read in 449 ms (1000 Bytes/s)
> failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND

Hi Ken,

This usually means you are referencing a node that doesn't exist in the
current live device tree blob...

Let's see your overlay..

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/CAOCHtYi0cyFnuoLOjg2-yJnSsrsCag%2BydqXT2YxycowkDZSndA%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.

Re: [beagleboard] How to use P9_19 / disable i2c2?

[Ken Shirriff]

Thanks, Robert. You were correct - I had a typo in my node name and now it 
works.

Ken

On Friday, November 30, 2018 at 7:52:39 AM UTC-8, RobertCNelson wrote:
>
> On Fri, Nov 30, 2018 at 12:30 AM Ken Shirriff  > wrote: 
> > 
> > Thanks, Robert. The make worked, but I can't seem to get an overlay to 
> load at all using u-boot. I had moved to a modern u-boot kernel and the 
> overlay I put into dtb_overlay in /boot/uEnv.txt doesn't get loaded, but I 
> don't see any errors in the log either. How do I debug this in the 
> post-capemgr world? I've tried a bunch of different overlays and settings 
> but nothing seems to work. Is there some trick to loading an overlay with 
> u-boot? 
> > 
> > Next, I reinstalled the kernel in case I'd messed up something along the 
> way. Now when I try to install a simple overlay with 
> "uboot_overlay_addr4=/lib/firmware/TEST-00A0.dtbo", it completely hangs 
> during boot, so I'm making negative progress here. Now I get a bunch of 
> overlay errors during boot: 
> > loading /boot/dtbs/4.14.71-ti-r80/am335x-boneblack-uboot-univ.dtb ... 
> > 161723 bytes read in 80 ms (1.9 MiB/s) 
> > uboot_overlays: [fdt_buffer=0x6] ... 
> > uboot_overlays: loading /lib/firmware/TEST-00A0.dtbo ... 
> > 824 bytes read in 449 ms (1000 Bytes/s) 
> > failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND 
>
> Hi Ken, 
>
> This usually means you are referencing a node that doesn't exist in the 
> current live device tree blob... 
>
> Let's see your overlay.. 
>
> 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/3c27667a-cc81-4135-9c60-74d67189be45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Beaglebone Black won't boot when gpio connections made

[Mike Brandon]

I have a device plugged in via GPIO to the following gpio pins:

48
49
115
117

If my device is connected at boot, the BB will not boot.

I am booting from eMMC. Any idea why this is occurring? I am using the 
attached custom overlay which is essentially the univ-emmc overlay with 
some modifications on GPIOs not listed above.

Mike


-- 
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/bbf65703-a19c-446f-a962-6baa15deff82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Gerald Coley]

Yep, you are changing the boot mode of the processor. A big no no.

https://www.elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Pin_Usage

Gerald


From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Mike Brandon
Sent: Friday, November 30, 2018 2:52 PM
To: BeagleBoard 
Subject: [beagleboard] Beaglebone Black won't boot when gpio connections made

I have a device plugged in via GPIO to the following gpio pins:

48
49
115
117

If my device is connected at boot, the BB will not boot.

I am booting from eMMC. Any idea why this is occurring? I am using the attached 
custom overlay which is essentially the univ-emmc overlay with some 
modifications on GPIOs not listed above.

Mike


--
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/bbf65703-a19c-446f-a962-6baa15deff82%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/f99a156b0ddf4c44a73f8fcaf3fccd8b%40winhexbeus11.winus.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Mike Brandon]

Gerald,

Thanks for pointing me to that information but I don't see where I am 
utilizing one of the 16 boot pins on the expansion header.

Also, my external device that is connected to the GPIO listed above is not 
powered up at boot.

Am I missing another key point in the reference you pointed me to?

Mike

On Friday, November 30, 2018 at 3:54:42 PM UTC-5, gcoley1 wrote:
>
> Yep, you are changing the boot mode of the processor. A big no no.
>
>  
>
>
> https://www.elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Pin_Usage
>
>  
>
> Gerald
>
>  
>
>  
>
> *From:* beagl...@googlegroups.com  [mailto:
> beagl...@googlegroups.com ] *On Behalf Of *Mike Brandon
> *Sent:* Friday, November 30, 2018 2:52 PM
> *To:* BeagleBoard >
> *Subject:* [beagleboard] Beaglebone Black won't boot when gpio 
> connections made
>
>  
>
> I have a device plugged in via GPIO to the following gpio pins:
>
>  
>
> 48
>
> 49
>
> 115
>
> 117
>
>  
>
> If my device is connected at boot, the BB will not boot.
>
>  
>
> I am booting from eMMC. Any idea why this is occurring? I am using the 
> attached custom overlay which is essentially the univ-emmc overlay with 
> some modifications on GPIOs not listed above.
>
>  
>
> Mike
>
>  
>
>  
>
> -- 
> 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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/bbf65703-a19c-446f-a962-6baa15deff82%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/338ac43f-50e8-4130-83d6-a4e85050a802%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Gerhard Hoffmann]

Yes. And sys_reset_n is just a RC-delayed version of the 3V3 supply. It 
is not debounced


if activated by the reset switch and rises slowly in the classic 
1-e-function style.


You need a Schmidt-trigger if you want to use it as a logic signal.

That sys_reset_n is high does not mean that you may drive some pins

(in my case P8. 39-46, the 8 pins accessible to PRU1 and also used by 
the LCD.)


I found that I had to use an 74LVC244 for isolation; the 3stated pins of a

Xilinx Coolrunner II were not high-impedance enough.


When sys_reset_n goes away, the processor just starts; it has not yet 
made up


its mind where to boot from.

I used a time constant of 3 times sys_reset_n to enable the 74lvc244.

regards, Gerhard




Am 30.11.18 um 21:54 schrieb Gerald Coley:


Yep, you are changing the boot mode of the processor. A big no no.

https://www.elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Pin_Usage

Gerald

*From:*beagleboard@googlegroups.com 
[mailto:beagleboard@googlegroups.com] *On Behalf Of *Mike Brandon

*Sent:* Friday, November 30, 2018 2:52 PM
*To:* BeagleBoard 
*Subject:* [beagleboard] Beaglebone Black won't boot when gpio 
connections made


I have a device plugged in via GPIO to the following gpio pins:





--
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/28140862-156d-cfaa-2f94-96e9f0530920%40hoffmann-hochfrequenz.de.
For more options, visit https://groups.google.com/d/optout.

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

[Mala Dies]

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 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/91cdcefd-06b6-4d68-96fe-a95b7dcd4573%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Gerald Coley]

It just take on boot pin to mess up the boot process. If it is not powered on 
it still presents a load. It still affects the boot pins.

Key point…DO NOT PUT ANYTHNING on GPIO pins that share the boot function on 
power up.

Gerald


From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Mike Brandon
Sent: Friday, November 30, 2018 3:07 PM
To: BeagleBoard 
Subject: Re: [beagleboard] Beaglebone Black won't boot when gpio connections 
made

Gerald,

Thanks for pointing me to that information but I don't see where I am utilizing 
one of the 16 boot pins on the expansion header.

Also, my external device that is connected to the GPIO listed above is not 
powered up at boot.

Am I missing another key point in the reference you pointed me to?

Mike

On Friday, November 30, 2018 at 3:54:42 PM UTC-5, gcoley1 wrote:
Yep, you are changing the boot mode of the processor. A big no no.

https://www.elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Pin_Usage

Gerald


From: beagl...@googlegroups.com 
[mailto:beagl...@googlegroups.com] On Behalf Of Mike Brandon
Sent: Friday, November 30, 2018 2:52 PM
To: BeagleBoard >
Subject: [beagleboard] Beaglebone Black won't boot when gpio connections made

I have a device plugged in via GPIO to the following gpio pins:

48
49
115
117

If my device is connected at boot, the BB will not boot.

I am booting from eMMC. Any idea why this is occurring? I am using the attached 
custom overlay which is essentially the univ-emmc overlay with some 
modifications on GPIOs not listed above.

Mike


--
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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/bbf65703-a19c-446f-a962-6baa15deff82%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/338ac43f-50e8-4130-83d6-a4e85050a802%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/178633782848495caa6ca61ffe512dde%40winhexbeus11.winus.mail.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] 1-wire on BB Blue

[jimfriel]

Hi,

I have several questions and hope someone can help. I'm trying to figure 
out how to configure ports on a beaglebone, generically. I haven't found a 
good site which describes any of this thanks to the relatively recent 
changes in how device tree overlays are handled. I'd like to be able to 
configure ports differently from how they ship, so I'm looking to develop 
generic understanding as well as to figure out my specific problem on how 
to configure a port differently:

I'm trying to configure 1-wire on a Beaglebone Blue using the latest iot 
build on beaglebone.org. The BB Blue has 6 free GPIOs which are pinned to 
connectors. Of the 6, looking at the dtb-rebuilder repo it seems that 
GPIO1_25 has the fewest number of hits there so perhaps this one is least 
likely to be used elsewhere. I've modified a dts file from bb-overlays.org 
repository, and guessed my way to the correct offset value for what I think 
should be PIN57 and produced and compiled the following dts:

/dts-v1/;
/plugin/;

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

/* identification */
part-number = "BB-W1-P1.25";
version = "00A0";

/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P1.25";

/*
 * Free up the pins used by the cape from the pinmux helpers.
 */
fragment@0 {
target = <&ocp>;
__overlay__ {
P1_25_pinmux { status = "disabled"; };
};
};

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

dallas_w1_pins: pinmux_dallas_w1_pins {
pinctrl-single,pins = <
0x0e4 0x37
>;
};
};
};

fragment@2 {
target-path="/";
__overlay__ {

onewire {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&dallas_w1_pins>;

compatible = "w1-gpio";
gpios = <&gpio1 25 0>;
};
};
};
};


In compiling this I get the following warnings, which don't mean much to me 
yet:
dtc -O dtb -o BB-W1-P1.25-00A0.dtb BB-W1-P1.25-00A0.dts -@
BB-W1-P1.25-00A0.dtb: Warning (unit_address_vs_reg): Node /fragment@0 has a 
unit name, but no reg property
BB-W1-P1.25-00A0.dtb: Warning (unit_address_vs_reg): Node /fragment@1 has a 
unit name, but no reg property
BB-W1-P1.25-00A0.dtb: Warning (unit_address_vs_reg): Node /fragment@2 has a 
unit name, but no reg property

In my /boot/uEnv.txt I have made the following changes, on the suspicion 
that there may be some sharing of the pin with video features:
uboot_overlay_addr0=/home/debian/BB-W1-P1.25-00A0.dtb
disable_uboot_overlay_video=1

Finally:
root@beaglebone:/opt/scripts/tools# ./version.sh
git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
eeprom:[A335BNLTBLA21722EL002623]
model:[TI_AM335x_BeagleBone_Blue]
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.05-rc1-2-g35aecb]:[location: dd MBR]
kernel:[4.14.71-ti-r80]
nodejs:[v6.15.0]
device-tree-override:[uboot_overlay_addr0=/home/debian/BB-W1-P1.25-00A0.dtb]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr0=/home/debian/BB-W1-P1.25-00A0.dtb]
uboot_overlay_options:[disable_uboot_overlay_video=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.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-git20181123.0-0rcnee0~stretch+20181124]
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.089162] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 
568
[   30.947099] pinctrl-single 44e10800.pinmux: pin PIN57 already requested 
by ocp:helper; cannot claim for onewire
[   31.202623] pinctrl-single 44e10800.pinmux: p

Re: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Mike Brandon]

But which gpio am I using that is a boot pin? In the reference manual, the 16 
boot pins are on the P8 header... I'm using gpios on the P9 header.


On Friday, November 30, 2018 at 5:03:42 PM UTC-5, gcoley1 wrote:
> It just take on boot pin to mess up the boot process. If it is not powered on 
> it still presents a load. It still affects the boot pins.
> 
>  
> 
> Key point…DO NOT PUT ANYTHNING on GPIO pins that share the boot function on 
> power up.
> 
>  
> 
> Gerald
> 
>  
> 
>  
> 
> From: beagl...@googlegroups.com [mailto:beagl...@googlegroups.com]
> On Behalf Of Mike Brandon
> 
> Sent: Friday, November 30, 2018 3:07 PM
> 
> To: BeagleBoard 
> 
> Subject: Re: [beagleboard] Beaglebone Black won't boot when gpio connections 
> made
> 
>  
> 
> 
> 
> Gerald,
> 
> 
> 
>  
> 
> 
> 
> 
> Thanks for pointing me to that information but I don't see where I am 
> utilizing one of the 16 boot pins on the expansion header.
> 
> 
> 
> 
>  
> 
> 
> 
> 
> Also, my external device that is connected to the GPIO listed above is not 
> powered up at boot.
> 
> 
> 
> 
>  
> 
> 
> 
> 
> Am I missing another key point in the reference you pointed me to?
> 
> 
> 
> 
>  
> 
> 
> 
> 
> Mike
> 
> 
> 
> On Friday, November 30, 2018 at 3:54:42 PM UTC-5, gcoley1 wrote:
> 
> 
> 
> 
> 
> 
> Yep, you are changing the boot mode of the processor. A big no no.
> 
>  
> 
> https://www.elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Pin_Usage
> 
>  
> 
> Gerald
> 
>  
> 
>  
> 
> From:
> beagl...@googlegroups.com [mailto:beagl...@googlegroups.com]
> On Behalf Of Mike Brandon
> 
> Sent: Friday, November 30, 2018 2:52 PM
> 
> To: BeagleBoard 
> 
> Subject: [beagleboard] Beaglebone Black won't boot when gpio connections made
> 
>  
> 
> 
> 
> I have a device plugged in via GPIO to the following gpio pins:
> 
> 
> 
>  
> 
> 
> 
> 
> 48
> 
> 
> 
> 
> 49
> 
> 
> 
> 
> 115
> 
> 
> 
> 
> 117
> 
> 
> 
> 
>  
> 
> 
> 
> 
> If my device is connected at boot, the BB will not boot.
> 
> 
> 
> 
>  
> 
> 
> 
> 
> I am booting from eMMC. Any idea why this is occurring? I am using the 
> attached custom overlay which is essentially the univ-emmc overlay with some 
> modifications on GPIOs not listed
>  above.
> 
> 
> 
> 
>  
> 
> 
> 
> 
> Mike
> 
> 
> 
> 
>  
> 
> 
> 
> 
>  
> 
> 
> 
> --
> 
> 
> 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...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/bbf65703-a19c-446f-a962-6baa15deff82%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...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/338ac43f-50e8-4130-83d6-a4e85050a802%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/39c8264a-074b-4372-9af2-a173431d2787%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Robert Nelson]

On Fri, Nov 30, 2018 at 4:38 PM Mike Brandon  wrote:
>
> But which gpio am I using that is a boot pin? In the reference manual, the 16 
> boot pins are on the P8 header... I'm using gpios on the P9 header.
>

Does anything show up over serial when it's plugged in? And what shows up?

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

Re: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Mike Brandon]

U-Boot SPL 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26)
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
spl_register_fat_device: fat register err - -1
spl_load_image_fat: error reading image u-boot.img, err - -1
 ** ext4fs_devread read error - block
Failed to mount ext2 filesystem...
spl_load_image_ext: ext4fs mount err - 0



On Friday, November 30, 2018 at 5:55:16 PM UTC-5, RobertCNelson wrote:
>
> On Fri, Nov 30, 2018 at 4:38 PM Mike Brandon  > wrote: 
> > 
> > But which gpio am I using that is a boot pin? In the reference manual, 
> the 16 boot pins are on the P8 header... I'm using gpios on the P9 header. 
> > 
>
> Does anything show up over serial when it's plugged in? And what shows up? 
>
> 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/462d9e5e-449c-4787-95a6-71ce04390003%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Gerald Coley]

Then there must me somethig else at play here. Without  a schematic, kind of 
hard to tell.

-Original Message-
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Mike Brandon
Sent: Friday, November 30, 2018 4:38 PM
To: BeagleBoard 
Subject: Re: [beagleboard] Beaglebone Black won't boot when gpio connections 
made

But which gpio am I using that is a boot pin? In the reference manual, the 16 
boot pins are on the P8 header... I'm using gpios on the P9 header.


On Friday, November 30, 2018 at 5:03:42 PM UTC-5, gcoley1 wrote:
> It just take on boot pin to mess up the boot process. If it is not powered on 
> it still presents a load. It still affects the boot pins.
> 
>  
> 
> Key point…DO NOT PUT ANYTHNING on GPIO pins that share the boot function on 
> power up.
> 
>  
> 
> Gerald
> 
>  
> 
>  
> 
> From: beagl...@googlegroups.com [mailto:beagl...@googlegroups.com]
> On Behalf Of Mike Brandon
> 
> Sent: Friday, November 30, 2018 3:07 PM
> 
> To: BeagleBoard 
> 
> Subject: Re: [beagleboard] Beaglebone Black won't boot when gpio 
> connections made
> 
>  
> 
> 
> 
> Gerald,
> 
> 
> 
>  
> 
> 
> 
> 
> Thanks for pointing me to that information but I don't see where I am 
> utilizing one of the 16 boot pins on the expansion header.
> 
> 
> 
> 
>  
> 
> 
> 
> 
> Also, my external device that is connected to the GPIO listed above is not 
> powered up at boot.
> 
> 
> 
> 
>  
> 
> 
> 
> 
> Am I missing another key point in the reference you pointed me to?
> 
> 
> 
> 
>  
> 
> 
> 
> 
> Mike
> 
> 
> 
> On Friday, November 30, 2018 at 3:54:42 PM UTC-5, gcoley1 wrote:
> 
> 
> 
> 
> 
> 
> Yep, you are changing the boot mode of the processor. A big no no.
> 
>  
> 
> https://www.elinux.org/Beagleboard:BeagleBoneBlack#Expansion_Header_Pi
> n_Usage
> 
>  
> 
> Gerald
> 
>  
> 
>  
> 
> From:
> beagl...@googlegroups.com [mailto:beagl...@googlegroups.com]
> On Behalf Of Mike Brandon
> 
> Sent: Friday, November 30, 2018 2:52 PM
> 
> To: BeagleBoard 
> 
> Subject: [beagleboard] Beaglebone Black won't boot when gpio 
> connections made
> 
>  
> 
> 
> 
> I have a device plugged in via GPIO to the following gpio pins:
> 
> 
> 
>  
> 
> 
> 
> 
> 48
> 
> 
> 
> 
> 49
> 
> 
> 
> 
> 115
> 
> 
> 
> 
> 117
> 
> 
> 
> 
>  
> 
> 
> 
> 
> If my device is connected at boot, the BB will not boot.
> 
> 
> 
> 
>  
> 
> 
> 
> 
> I am booting from eMMC. Any idea why this is occurring? I am using the 
> attached custom overlay which is essentially the univ-emmc overlay with some 
> modifications on GPIOs not listed  above.
> 
> 
> 
> 
>  
> 
> 
> 
> 
> Mike
> 
> 
> 
> 
>  
> 
> 
> 
> 
>  
> 
> 
> 
> --
> 
> 
> 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...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/bbf65703-a19c-446f-a962-6baa15deff82%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...@googlegroups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/338ac43f-50e8-4130-83d6-a4e85050a802%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/39c8264a-074b-4372-9af2-a173431d2787%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/25dd303a0c9d421782a6b36044753b5b%40winhexbeus11.winus.mail.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Gerald Coley]

Looks like you may be conflicted with the eMMC pins, which also go to the 
expansion headers.

[cid:image001.png@01D488DB.E1A48D20]

I do not know if the MMC ports are numbered 0 and 1 or 1 and 2 these days in 
SW. But normally the board boots from the eMMC. On the Hardware we numbered 
them 0 and 1, 0 being the SD card and 1 being the eMMC. You can insert a 
bootable SD card and see if it boots from there.

Gerald

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Mike Brandon
Sent: Friday, November 30, 2018 5:09 PM
To: BeagleBoard 
Subject: Re: [beagleboard] Beaglebone Black won't boot when gpio connections 
made

U-Boot SPL 2017.03-2-gd12b1519b4 (Mar 14 2017 - 10:28:26)
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
spl_register_fat_device: fat register err - -1
spl_load_image_fat: error reading image u-boot.img, err - -1
 ** ext4fs_devread read error - block
Failed to mount ext2 filesystem...
spl_load_image_ext: ext4fs mount err - 0



On Friday, November 30, 2018 at 5:55:16 PM UTC-5, RobertCNelson wrote:
On Fri, Nov 30, 2018 at 4:38 PM Mike Brandon > 
wrote:
>
> But which gpio am I using that is a boot pin? In the reference manual, the 16 
> boot pins are on the P8 header... I'm using gpios on the P9 header.
>

Does anything show up over serial when it's plugged in? And what shows up?

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/462d9e5e-449c-4787-95a6-71ce04390003%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/94c38d0e1d504739a0bc991f5762a2ad%40winhexbeus11.winus.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Mike Brandon]

HAH, wow it has been a long day. It must be time for me to put this aside 
for a bit... WOW. Sometimes I amaze myself.

Thanks and sorry that my goof has taken up a small bit of ya'lls valuable 
time.

Until my next stupid question...

On Friday, November 30, 2018 at 8:24:45 PM UTC-5, RobertCNelson wrote:
>
>
>
> On Fri, Nov 30, 2018 at 7:12 PM Mike Brandon  > wrote:
>
>> [image: IMG_20181130_194825.jpg]
>>
>> [image: IMG_20181130_194818.jpg]
>>
>>
> On Fri, Nov 30, 2018 at 4:38 PM Mike Brandon  wrote: 
>>> > 
>>> > But which gpio am I using that is a boot pin? In the reference manual, 
>>> the 16 boot pins are on the P8 header... I'm using gpios on the P9 header. 
>>> > 
>>>
>>>
> From your picture, that's the P8 header...
>
> 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/7d975b54-d42e-4831-a289-78e500738995%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Mike Brandon]

Actually, one more question before I go cry myself to sleep...

Considering I will want to make similar connections on P8 in the future... 
can I use a device like this to isolate the boot pins at boot?

http://www.ti.com/lit/ds/symlink/sn74cbtd16211.pdf

On Friday, November 30, 2018 at 8:29:32 PM UTC-5, Mike Brandon wrote:
>
> HAH, wow it has been a long day. It must be time for me to put this aside 
> for a bit... WOW. Sometimes I amaze myself.
>
> Thanks and sorry that my goof has taken up a small bit of ya'lls valuable 
> time.
>
> Until my next stupid question...
>
> On Friday, November 30, 2018 at 8:24:45 PM UTC-5, RobertCNelson wrote:
>>
>>
>>
>> On Fri, Nov 30, 2018 at 7:12 PM Mike Brandon  wrote:
>>
>>> [image: IMG_20181130_194825.jpg]
>>>
>>> [image: IMG_20181130_194818.jpg]
>>>
>>>
>> On Fri, Nov 30, 2018 at 4:38 PM Mike Brandon  wrote: 
 > 
 > But which gpio am I using that is a boot pin? In the reference 
 manual, the 16 boot pins are on the P8 header... I'm using gpios on the P9 
 header. 
 > 


>> From your picture, that's the P8 header...
>>
>> 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/788ff78f-39c8-4f85-92a2-7369143f751e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Beaglebone Black won't boot when gpio connections made

[Gerhard Hoffmann]

In principle yes, but given that you won't need that many bits and that 
the BBB pins


are relatively weak drivers and the ground connections on the BBB are a 
joke, I prefer


74LVC244 / 74LVC245 or similar. They present less load to the BBB and 
are also much


more common, mainstream devices, and cheap.

Cheers, Gerhard


p.s.

Has anybody tested out what it takes to isolate that 16 bit multiplexed bus?


Am 01.12.18 um 02:31 schrieb Mike Brandon:

Actually, one more question before I go cry myself to sleep...

Considering I will want to make similar connections on P8 in the 
future... can I use a device like this to isolate the boot pins at boot?


http://www.ti.com/lit/ds/symlink/sn74cbtd16211.pdf



--
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/e2afe3de-8d3f-71bc-e1f2-c0e504a18e67%40hoffmann-hochfrequenz.de.
For more options, visit https://groups.google.com/d/optout.