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,
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
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
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
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 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
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
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,
--
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
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:
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,
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
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,
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
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
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
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
>
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
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=9s
>
> On Saturday, May 12, 2012 at 11:30:11 PM UTC+7, Soranne wrote:
>>
>> Does anyone know if it is possible
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
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
21 matches
Mail list logo