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,
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
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,
: [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
: [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 b
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
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,
--
legroups.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,
>
>
>
>
>
@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
#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
ald
>
>
>
>
>
> *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
>
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
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
13 matches
Mail list logo