t on the Beagle.
However when I plug my screen in I can see that _something_ is
happening: the screen detects output, indicator LED's etc. say so and
input selection tells me there's something coming in on HDMI1.
On the BeagleBone, running `wsconsctl` gives me the correct screen size
and i
Okay, so I have made a little progress...
I modified .dtb file in the way similar to described here:
https://stackoverflow.com/questions/36090929/modifying-the-device-tree-for-the-beaglebone-black
I've put the am335x-boneblack.dtb file on SD card before installation and
then run installati
Hello,
How can I check which /dev/tty or /dev/cua corresponds to which physical
pin at the connector?
Is there a need to set or change something in dtb files (or something like
that) to enable UART on OpenBSD on BBB?
(I ask because to run UART on BBB on Debian I have to add some lines to
/boot/u
it.
OpenBSD 7.2-current (GENERIC) #78: Mon Oct 31 22:21:50 MDT 2022
dera...@armv7.openbsd.org:/usr/src/sys/arch/armv7/compile/GENERIC
real mem = 484179968 (461MB)
avail mem = 464629760 (443MB)
random: good seed from bootblocks
mainbus0 at root: TI AM335x BeagleBone Black
cpu0 at mainbus0 mp
/GENERIC
> real mem = 484179968 (461MB)
> avail mem = 464629760 (443MB)
> random: good seed from bootblocks
> mainbus0 at root: TI AM335x BeagleBone Black
> cpu0 at mainbus0 mpidr 0: ARM Cortex-A8 r3p2
> cpu0: 32KB 64b/line 4-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cach
MB)
random: good seed from bootblocks
mainbus0 at root: TI AM335x BeagleBone Black
cpu0 at mainbus0 mpidr 0: ARM Cortex-A8 r3p2
cpu0: 32KB 64b/line 4-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 256KB 64b/line 8-way L2 cache
omap0 at mainbus0
prcm0 at omap0 rev 0.2
dmtimer0 at omap0 rev 3.1
= 464629760 (443MB)
random: good seed from bootblocks
mainbus0 at root: TI AM335x BeagleBone Black
cpu0 at mainbus0 mpidr 0: ARM Cortex-A8 r3p2
cpu0: 32KB 64b/line 4-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 256KB 64b/line 8-way L2 cache
omap0 at mainbus0
prcm0 at omap0 rev 0.2
I would love too, but the only bbb I have
is used for local DNS.
I can't pull it now.
Besides it took a very long time trying to install openbsd on it,
see it fail then spending long time re-flashing it with freebsd.
If I had another one - I would try. As it stands now, I would need
to be sure fi
:52, Jan Stary wrote:
> On Nov 04 09:55:10, da...@davebarrass.org.uk wrote:
>> I am intending to try the 7.2 install on a Beaglebone Black having not
>> had any success to date with any stock images from 5.9 onwards. the
>> issue that I experience is U-Boot. I can boot my BBB f
On Nov 04 09:55:10, da...@davebarrass.org.uk wrote:
> I am intending to try the 7.2 install on a Beaglebone Black having not
> had any success to date with any stock images from 5.9 onwards. the
> issue that I experience is U-Boot. I can boot my BBB from U-Boot images
> from other
On Nov 05 08:29:19, olp...@yahoo.ca wrote:
> It runs previous versions of openbsd.
> Freebsd also, so I doubt it is internal storage fault.
So try it now and show the script(1) of the install.
> On Nov 04 06:35:01, olp...@yahoo.ca wrote:
> > I actually could not run anything after 6.X,
> > so ha
It runs previous versions of openbsd.
Freebsd also, so I doubt it is internal storage fault.
But anyway, sorry for hijacking the thread.
On Friday, November 4, 2022 at 08:51:14 p.m. GMT+9, Jan Stary
wrote:
On Nov 04 06:35:01, olp...@yahoo.ca wrote:
> I actually could not run anything
> Date: Fri, 4 Nov 2022 13:40:35 +0100
> From: Jan Stary
>
> On Nov 04 13:14:31, mark.kette...@xs4all.nl wrote:
> > The device names used by the bootloader differ from the names used by
> > the kernel. What gets printed as bootdevice/bootfile here is simply
> > the string that the bootloader pas
On Nov 04 13:14:31, mark.kette...@xs4all.nl wrote:
> The device names used by the bootloader differ from the names used by
> the kernel. What gets printed as bootdevice/bootfile here is simply
> the string that the bootloader passed to the kernel. We probably
> should change the names in the boot
> Date: Fri, 4 Nov 2022 12:59:13 +0100
> From: Jan Stary
>
> On Nov 02 21:18:03, h...@stare.cz wrote:
> > This is current/armv7 on a BeagleBone Black, dmesg below.
> > The booting sequence ends with
> >
> > sd0 at scsibus0 targ 1 lun 0: removable
> >
On Nov 02 21:18:03, h...@stare.cz wrote:
> This is current/armv7 on a BeagleBone Black, dmesg below.
> The booting sequence ends with
>
> sd0 at scsibus0 targ 1 lun 0: removable
> sd0: 1832MB, 512 bytes/sector, 3751936 sectors
> scsibus1 at sdmmc0: 2 targets, init
On Nov 04 06:35:01, olp...@yahoo.ca wrote:
> I actually could not run anything after 6.X,
> so had to install freebsd there, unfortunately.
> (can't remember the X now).
> It was always failing to install on the internal disk.
> (can't write on disk, errors).
It is quite possible that the intern
I am intending to try the 7.2 install on a Beaglebone Black having not
had any success to date with any stock images from 5.9 onwards. the
issue that I experience is U-Boot. I can boot my BBB from U-Boot images
from other projects but when I simply write the image as downloaded from
a nearby
I actually could not run anything after 6.X,
so had to install freebsd there, unfortunately.
(can't remember the X now).
It was always failing to install on the internal disk.
(can't write on disk, errors).
On Friday, November 4, 2022 at 03:20:44 p.m. GMT+9, Jan Stary
wrote:
On Nov 03 2
On Nov 03 22:14:32, olp...@yahoo.ca wrote:
> Wow, did you install vanilla 7.2 on bbb?
Is it the 7.2 in particular that surprises you?
OpenBSD has been running on bbb since 5.4 for me.
> Or did you have to tweak kernel?
No, it installs just fine.
Wow, did you install vanilla 7.2 on bbb?
Or did you have to tweak kernel?
On Thursday, November 3, 2022 at 05:18:10 a.m. GMT+9, Jan Stary
wrote:
This is current/armv7 on a BeagleBone Black, dmesg below.
The booting sequence ends with
sd0 at scsibus0 targ 1 lun 0: removable
sd0
This is current/armv7 on a BeagleBone Black, dmesg below.
The booting sequence ends with
sd0 at scsibus0 targ 1 lun 0: removable
sd0: 1832MB, 512 bytes/sector, 3751936 sectors
scsibus1 at sdmmc0: 2 targets, initiator 0
sd1 at scsibus1 targ 1 lun 0: removable
sd1: 30436MB, 512 bytes
/compile/GENERIC
real mem = 484261888 (461MB)
avail mem = 463945728 (442MB)
random: good seed from bootblocks
mainbus0 at root: TI AM335x BeagleBone Black
cpu0 at mainbus0 mpidr 0: ARM Cortex-A8 r3p2
cpu0: 32KB 64b/line 4-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 256KB 64b/line 8-way L2
functional.
> >>>
> >>>
> >>>>> On Mar 20, 2021, at 14:52, Alan Corey wrote:
> >>>>
> >>>> man mount, then type /read-only to search, / to search for the same
> >>>> thing
> >>>> again. Som
On Thu, Mar 25, 2021 at 12:54:02AM +1100, Jonathan Gray wrote:
> On Wed, Mar 24, 2021 at 11:14:43PM +1100, Jonathan Gray wrote:
> > On Mon, Mar 22, 2021 at 07:00:06PM -0500, Jordon wrote:
> > > 6.6 was the last release that works. 6.7 and 6.8 throw an input/output
> > > error when it tries to cre
;>>> thing
> >>>> again. Sometimes a read-only mount happens if thare's something
> wrong.
> >>>>
> >>>> But reformat and try reloading before you throw it away.
> >>>>
> >>>>> On Sat, Mar 20, 2021, 3:3
On Wed, Mar 24, 2021 at 11:14:43PM +1100, Jonathan Gray wrote:
> On Mon, Mar 22, 2021 at 07:00:06PM -0500, Jordon wrote:
> > 6.6 was the last release that works. 6.7 and 6.8 throw an input/output
> > error when it tries to create the partitions (right after you choose
> > ‘(W)hole disk’).
> >
>
On Mon, Mar 22, 2021 at 07:00:06PM -0500, Jordon wrote:
> 6.6 was the last release that works. 6.7 and 6.8 throw an input/output error
> when it tries to create the partitions (right after you choose ‘(W)hole
> disk’).
>
> Am I the only person to try installing it to onboard storage in the last
type /read-only to search, / to search for the same
>>>> thing
>>>> again. Sometimes a read-only mount happens if thare's something wrong.
>>>>
>>>> But reformat and try reloading before you throw it away.
>>>>
>>>>>
>>>
>>> But reformat and try reloading before you throw it away.
>>>
>>>> On Sat, Mar 20, 2021, 3:30 PM Fred wrote:
>>>>
>>>>> On 3/20/21 1:28 PM, Jordon wrote:
>>>>> I recently decided to play with my BBB boards after ig
fter ignoring them for a
>> few years (one of them still had 5.6 installed on it!). I have 3
>> BeagleBone Black boards (2 with 2GB, 1 with 4GB). When i dd’ed
>> miniroot-am335x-68.img to a uSD cards and booted it, it all seemed pretty
>> normal until I got to the part whe
, 3:30 PM Fred wrote:
>>>
>>>> On 3/20/21 1:28 PM, Jordon wrote:
>>>> I recently decided to play with my BBB boards after ignoring them for a
>>> few years (one of them still had 5.6 installed on it!). I have 3
>>> BeagleBone Black boards (2 wi
On 3/20/21 1:28 PM, Jordon wrote:
I recently decided to play with my BBB boards after ignoring them for a few
years (one of them still had 5.6 installed on it!). I have 3 BeagleBone Black
boards (2 with 2GB, 1 with 4GB). When i dd’ed miniroot-am335x-68.img to a uSD
cards and booted it, it
e:
> > I recently decided to play with my BBB boards after ignoring them for a
> few years (one of them still had 5.6 installed on it!). I have 3
> BeagleBone Black boards (2 with 2GB, 1 with 4GB). When i dd’ed
> miniroot-am335x-68.img to a uSD cards and booted it, it all seemed pretty
>
46 AM Jordon wrote:
> I recently decided to play with my BBB boards after ignoring them for a
> few years (one of them still had 5.6 installed on it!). I have 3
> BeagleBone Black boards (2 with 2GB, 1 with 4GB). When i dd’ed
> miniroot-am335x-68.img to a uSD cards and booted it, it
I recently decided to play with my BBB boards after ignoring them for a few
years (one of them still had 5.6 installed on it!). I have 3 BeagleBone Black
boards (2 with 2GB, 1 with 4GB). When i dd’ed miniroot-am335x-68.img to a uSD
cards and booted it, it all seemed pretty normal until I got
. Card did not respond to voltage select!
U-Boot 2019.01 (Apr 09 2019 - 23:15:32 +0200)
CPU : AM335X-GP rev 2.0
Model: TI AM335x BeagleBone Black
DRAM: 512 MiB
musb - not able to bind usb peripheral node
NAND: 0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... MMC: no card
On Tue, Jan 28, 2020 at 04:01:49PM +0100, Jan Stary wrote:
> > On Jan 28 15:03:33, h...@stare.cz wrote:
> > > After a failed sysupgrade that reboots midway
> > > https://marc.info/?l=openbsd-misc&m=157856684125898&w=2
> > > my BBB will not boot into anything:
> > >
> > >
> > > U-Boot SPL 2017.03
On Tue, Jan 28, 2020 at 04:09:21PM +0100, Jan Stary wrote:
> Is anyone using wifi with the BBB?
>
> A USB dongle seems the easiest to do
> - does anyone have a success story to report please?
The USB OTG controller on the BBB is not supported.
Is anyone using wifi with the BBB?
A USB dongle seems the easiest to do
- does anyone have a success story to report please?
I might need the USB for a disk - is there any option
to get wifi on the BBB beside a USB dongle?
I understand there is BeagleBone Black Wireless,
which does have wifi
and now.)
http://stare.cz/dmesg/beaglebone-black.20200113
> On Jan 28 15:03:33, h...@stare.cz wrote:
> > After a failed sysupgrade that reboots midway
> > https://marc.info/?l=openbsd-misc&m=157856684125898&w=2
> > my BBB will not boot into anything:
> >
> >
> > U-Boot SPL 2017.03 (Mar 26 2017 - 16:58:08)
> > Trying to boot from MMC2
> > MMC partition s
the current miniroot-am335x-66.fs
>
> I have no idea what the problem is.
> Can anyone push me in the right direction please?
>
> Jan
>
OpenBSD 6.6-current (GENERIC) #0: Mon Jan 13 14:45:16 CET 2020
h...@bbb.stare.cz:/usr/src/sys/arch/armv7/compile/GENERIC
real mem = 4
After a failed sysupgrade that reboots midway
https://marc.info/?l=openbsd-misc&m=157856684125898&w=2
my BBB will not boot into anything:
U-Boot SPL 2017.03 (Mar 26 2017 - 16:58:08)
Trying to boot from MMC2
MMC partition switch failed
*** Warning - MMC partition switch failed, using default envir
On Jun 07 11:44:01, h...@stare.cz wrote:
> Hi all,
>
> this is current/armv7 on a BeagleBone Black, dmesg below.
> It has an internal flash storage (2GB), and I put a 32GB SD into it,
> which is where the OpenBSD installation lives.
>
> The boot seems to be changing its mi
Hi all,
this is current/armv7 on a BeagleBone Black, dmesg below.
It has an internal flash storage (2GB), and I put a 32GB SD into it,
which is where the OpenBSD installation lives.
The boot seems to be changing its mind about what sd0 and sd1 is.
After a reboot, I see the same dmesg, except
I upgraded OpenBSD 6.3 to 6.4 GENERIC#71 armv7 on my BeagleBone Black and
then all my packages using pkg_add -u which then showed: redis
redis-4.0.2->4.0.11:
ok
I ran redis-server and it gave me a bus error. I ran the core file it
dumped through gdb and below is what it showed. All my ot
rc/sys/arch/armv7/compile/GENERIC
real mem = 536870912 (512MB)
avail mem = 516853760 (492MB)
mainbus0 at root: TI AM335x BeagleBone Black
cpu0 at mainbus0: ARM Cortex-A8 r3p2 (ARMv7)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way
I'm not sure what is going on with my BBB it always seems to go to ddb>
prompt after a day or two of no use. This is happening on one other BBB I
leave on as well. I thought maybe 6.2 or 6.3 will fix this but nothing
seems to stay up. It still is in the ddb prompt in case someone has any
other debu
On Fri, 20 Apr 2018 01:38:05 +1000
Jonathan Gray wrote:
> There is no driver for the mentor usb otg controller in the am335x.
Thanks a lot for fast reply. Looks like for this toy router I would
stay with VLANs and routing thorough one NICs. I've seen there exist
drivers for mentor usb on am335x
On Thu, Apr 19, 2018 at 04:28:45PM +0200, Karel Gardas wrote:
>
> Hello,
>
> trying to make toy router with BeagleBone White Rev A6a, planning to
> use builtin cpsw0 ethernet together with Lenovo ThinkPad USB Ethernet
> adapter which when used on AMD64 shows as cdce0 ethernet d
Hello,
trying to make toy router with BeagleBone White Rev A6a, planning to
use builtin cpsw0 ethernet together with Lenovo ThinkPad USB Ethernet
adapter which when used on AMD64 shows as cdce0 ethernet device and so
far I've not seen any issue on AMD64 with it. The problem with BBW is
th
> From: Vadim Zhukov
> Date: Sun, 17 Dec 2017 12:45:32 +0300
>
> Hi all.
>
> First, I have to sorry for likely stupid questions, I'm a totally
> newbie in the ARM world.
>
> I'm looking toward BeagleBone Enhanced -
> https://elinux.org/SanCloud:
Hi all.
First, I have to sorry for likely stupid questions, I'm a totally
newbie in the ARM world.
I'm looking toward BeagleBone Enhanced -
https://elinux.org/SanCloud:BeagleBoneEnhanced . And there are a few
questions:
1. Does anyone have expirience with it? Or at least things should
> On Aug 28, 2017, at 9:35 PM, Jonathan Gray wrote:
>
> On Mon, Aug 28, 2017 at 09:13:26PM -0600, Dan Jones wrote:
>> I have a BBB Rev B which I am trying to boot OpenBSD current (28-Aug-2017)
>> from the SD card and the boot fails repeating the message below. I am able
>> to boot other OSs f
> Reset Source: Power-on reset has occurred.
> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Board: BeagleBone Black
> not set. Validating first E-fuse MAC
> BeagleBone Black:
> BeagleBone: cape eeprom: i2c_probe: 0x54:
> BeagleBone: cape eeprom: i2
c'
Some drivers were not found
Reset Source: Power-on reset has occurred.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
Board: BeagleBone Black
not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_pro
On Sun, Jun 11, 2017 at 04:50:07PM -0400, Luke Tidd wrote:
> Sorry the entire serial output from the upgrade is not available.
> The log lasted below shows the end of the upgrade, and two attempts to
> boot bsd and bsd.rd.
> I mostly mashed enter during the upgrade like usual. The mirror was
> open
Sorry the entire serial output from the upgrade is not available.
The log lasted below shows the end of the upgrade, and two attempts to
boot bsd and bsd.rd.
I mostly mashed enter during the upgrade like usual. The mirror was
openbsd.cs.toronto.edu.
After mounting my SD card on another machine, I r
hi all .
thanks for the Mailing List's help .
ftp.jaist.ac.jp:/pub/OpenBSD/6.0/armv7/miniroot-am335x-60.fs is also OK .
-
Tuyosi ; http://akita-arm.blogspot.jp/2016/09/bbb.html
Hi all .
i managed to succeed to run openbsd on beaglebone black(BBB).
i tried 6.0 & snapshots , but LED did not light .
so i use 5.4 .
the next is too long for veterans .
but it may be kind to the newbies like me .
-->
cu -l cuaU0 -s 115200
Connected to /dev/cuaU0
hi all .
i fail and fail to install miniroot-am335x-YY.fs into micro sd card .
by the way
i am impressded the way how archlinux is installed into emmc.
whole view
1st) install archlinux into a micro sd card .
2nd) boot BBB by the micro sd card's archlinux , and again install
archlinux into emmc
You should try miniroot-am335x-60.fs or a recent snapshot.
A lot of change happen on openbsd and especially on recent port like
the ARM one.
2016-09-06 5:44 GMT+02:00 Tuyosi T :
> Hi all .
>
> i try miniroot-am335x-59.fs .
> but i can not boot it by sd card nevertherless i can boot arch linux by s
Hi all .
i try miniroot-am335x-59.fs .
but i can not boot it by sd card nevertherless i can boot arch linux by sd
card
bootting sd card of arch linux movie is
https://www.youtube.com/watch?v=FnT2J2AjGLE
is there some magics with openbsd's arm ?
-
regards http://akita-arm.blogspot.jp/2016/0
I tried the latest snapshot again.
It works now!
I was able to install without a problem.
Thank you whoever you are that fixed something!
On Mon, Aug 15, 2016 at 10:07 AM, Farid Joubbi wrote:
> I used dd in linux to copy the snapshot to a microSD.
> Then booted with that card.
>
> I then did the
I used dd in linux to copy the snapshot to a microSD.
Then booted with that card.
I then did the exact same procedure with 5.9 release using the same card.
That one boots normally (but is not able to install on the internal memory
of the BBB).
On Sun, Aug 14, 2016 at 4:07 PM, Jonathan Gray wrote
On Sat, Aug 13, 2016 at 02:57:39PM +0200, Farid Joubbi wrote:
> Hello,
>
> Lately I have not been able to boot the current snapshots at all with my
> bbb.
> This is what I get with the snapshot from 12th of August:
>
> U-Boot SPL 2016.07 (Aug 05 2016 - 23:28:55)
> Trying to boot from MMC1
> ** Fi
Hello,
Lately I have not been able to boot the current snapshots at all with my
bbb.
This is what I get with the snapshot from 12th of August:
U-Boot SPL 2016.07 (Aug 05 2016 - 23:28:55)
Trying to boot from MMC1
** First descriptor is NOT a primary desc on 0:1 **
MMC partition switch failed
*** W
On 2016-05-19 10:07, Jonathan Gray wrote:
> On Sun, Apr 24, 2016 at 08:23:53AM +, Karel W. Dingeldey wrote:
>
> On 2016-04-22 10:32, Jonathan Gray wrote:
>
> On Fri, Apr 22, 2016 at 10:10:10AM +, Karel W. Dingeldey wrote:
>
> Hi everyone,
>
> I'm currently using OpenBSD 5.7 and
On Sun, Apr 24, 2016 at 08:23:53AM +, Karel W. Dingeldey wrote:
>
>
> On 2016-04-22 10:32, Jonathan Gray wrote:
>
> > On Fri, Apr 22, 2016 at 10:10:10AM +, Karel W. Dingeldey wrote:
> >
> >> Hi everyone,
> >>
> >> I'm currently using OpenBSD 5.7 and 5.8 on a couple of BBBs -- works
mem = 536870912 (512MB)
avail mem = 515084288 (491MB)
mainbus0 at root
cpu0 at mainbus0: ARM Cortex A8 R3 rev 2 (ARMv7 core)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way) wr-back D-cache
omap0 at mainbus0: TI AM335x Beag
Hello,
Same problem here.
I didn't paid attention because I prefere to boot from a SD card.
Here is my console output at boot :
U-Boot SPL 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06)
U-Boot 2015.01-1-gb2412df (Jan 29 2015 - 15:01:06), Build:
jenkins-github_Bootloader-Builder-105
On Fri, Apr 22, 2016 at 10:10:10AM +, Karel W. Dingeldey wrote:
>
>
> Hi everyone,
>
> I'm currently using OpenBSD 5.7 and 5.8 on a couple of BBBs -- works
> like a charm.
>
> Since 5.9 came out a couple of days ago, I wanted to use it on another
> BBB (new install).
>
> When it comes to
Hi everyone,
I'm currently using OpenBSD 5.7 and 5.8 on a couple of BBBs -- works
like a charm.
Since 5.9 came out a couple of days ago, I wanted to use it on another
BBB (new install).
When it comes to stating which hard drive it should install to (eMMC in
this instance), I can only select s
This is a BeagleBone Black board Revision B6.
Running OpenBSD 5.6-current as of 15 November 2014.
When using net/tor:
Tor v0.2.5.10 (git-42b42605f8d8eac2) running on OpenBSD with Libevent
1.4.14b-stable, OpenSSL LibreSSL 2.1 and Zlib 1.2.3.
I can use exit nodes to access external sites like
using the variable syntax and not the address explicitly.
To be more clear about the problem I *actually* ran into, the
frequently-Googled post by tedu
(http://www.tedunangst.com/flak/post/OpenBSD-on-BeagleBone-Black) uses
a dhcp line that did not work for me due to a default filename
(pxelinux.0) be
ck D-cache
omap0 at mainbus0: BeagleBone
prcm0 at omap0 rev 0.2
sitaracm0 at omap0: control module, rev 1.0
intc0 at omap0 rev 5.0
edma0 at omap0 rev 0.0
dmtimer0 at omap0 rev 3.1
dmtimer1 at omap0 rev 3.1
omdog0 at omap0 rev 0.1
omgpio0 at omap0: rev 0.1
gpio0 at omgpio0: 32 pins
omgpio1 at omap0: rev
On Sun, Nov 02, 2014 at 09:31:26PM +1100, Jonathan Gray wrote:
> On Mon, Oct 20, 2014 at 02:40:13AM -0400, Andrew Hills wrote:
> > On 10/19/14, 11:15 AM, Gerke M. Preussner wrote:
> > > I haven't had any time yet to look into this. Were you able to make any
> > > progress on your end?
> >
> > I'm
On Mon, Oct 20, 2014 at 02:40:13AM -0400, Andrew Hills wrote:
> On 10/19/14, 11:15 AM, Gerke M. Preussner wrote:
> > I haven't had any time yet to look into this. Were you able to make any
> > progress on your end?
>
> I'm not sure I'd call it progress; I'm not familiar with the MMC
> protocol, so
On Mon, Oct 20, 2014 at 02:40:13AM -0400, Andrew Hills wrote:
> On 10/19/14, 11:15 AM, Gerke M. Preussner wrote:
> > I haven't had any time yet to look into this. Were you able to make any
> > progress on your end?
>
> I'm not sure I'd call it progress; I'm not familiar with the MMC
> protocol, so
On 10/19/14, 11:15 AM, Gerke M. Preussner wrote:
> I haven't had any time yet to look into this. Were you able to make any
> progress on your end?
I'm not sure I'd call it progress; I'm not familiar with the MMC
protocol, so I'm spending most of my time learning rather than debugging.
During the
On 10/13/14 14:37, Andrew Hills wrote:
On 10/13/14, 9:03 AM, Jonathan Gray wrote:
The rev C I have recognises the 4GB eMMC. Does anything change if you
remove the sd card?
When I boot (5.5, snapshot, -current) from an SD card on my rev C, dmesg
always contains the following:
sdmmc1: can't en
led
cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way) wr-back D-cache
omap0 at mainbus0: BeagleBone
prcm0 at omap0 rev 0.2
sitaracm0 at omap0: control module, rev 1.0
intc0 at omap0 rev 5.0
edma0 at omap0 rev 0.0
dmtimer0 at omap0 rev 3.1
dmtimer1 at omap0 rev 3.1
omdog0 at omap0 rev 0.1
omgpio0 at
On Sun, Oct 12, 2014 at 06:14:40PM -0400, Gerke M. Preussner wrote:
>
> On 10/12/2014 07:34 AM, Raphael Graf wrote:
> > [..]
> > This snapshot works fine on my BeagleBone (rev. A5C, 2GB eMMC), dmesg below.
> > No idea what you're missing. Can you send a dmesg?
> &g
On 10/12/2014 07:34 AM, Raphael Graf wrote:
> [..]
> This snapshot works fine on my BeagleBone (rev. A5C, 2GB eMMC), dmesg below.
> No idea what you're missing. Can you send a dmesg?
>
> [..]
Please find below the console outputs of my
1.) rev. B, 2GB eMMC
2.) rev. C, 4GB eM
On Sun, October 12, 2014 1:48 am, Gerke M. Preussner wrote:
> On 09/25/2014 12:45 AM, Jonathan Gray wrote:
>> On Wed, Sep 24, 2014 at 11:48:14PM -0400, Gerke M. Preussner wrote:
>>> I'm having the same problem on a BeagleBone Black Rev C. sdmmc1 cannot
>>>
On 09/25/2014 12:45 AM, Jonathan Gray wrote:
> On Wed, Sep 24, 2014 at 11:48:14PM -0400, Gerke M. Preussner wrote:
>> I'm having the same problem on a BeagleBone Black Rev C. sdmmc1 cannot
>> be enabled, and hence sd1 is not available.
>>
>> [..]
>>
>&g
On Wed, Sep 24, 2014 at 11:48:14PM -0400, Gerke M. Preussner wrote:
>
> I'm having the same problem on a BeagleBone Black Rev C. sdmmc1 cannot
> be enabled, and hence sd1 is not available.
>
> Interestingly, it works fine on my other board, which is a Rev B. Please
> note
> I am trying to install the latest arm7 snap on a BeagleBone Black
> using miniroot-am335x-55.fs but it only offers sd0 (the SD card)
> for installation. I installed to the SD card OK and the build-in
> emmc is visible as /dev/sd1.
[..]
> Here is dmesg as produced after booting
Hi,
I'm trying to install the latest armv7 snapshot (June 18) on the
internal 4GB mmc of a Beaglebone Black Rev C. The mmc is recognized by
the installer, but when the installer tries to create the disklabel, it
spits out a bunch of I/O errors.
Installing on an SDCard (sd0) works perf
I have now managed to install to the built-in emmc drive - for some
reason the problem of the emmc not being available for installation
has cleared. However I now have another problem, if I have a uSD card
plugged in for data storage (web server and torrent client) then boot
fails.
I tried everyth
>> No idea, this works fine on my BeagleBone Black (rev. A5C).
>> Can you send a dmesg?
Here is dmesg as produced after booting the miniroot. I added
(from memory) a message I just caught at the very start of boot:
WARNING: No entropy supplied by boot loader
NAND: No NAND
On 07/22/14 18:36, Neoklis Kyriazis wrote:
Hi
I am trying to install the latest arm7 snap on a BeagleBone Black
using miniroot-am335x-55.fs but it only offers sd0 (the SD card)
for installation. I installed to the SD card OK and the build-in
emmc is visible as /dev/sd1.
From (poor!) memory
Hi
I am trying to install the latest arm7 snap on a BeagleBone Black
using miniroot-am335x-55.fs but it only offers sd0 (the SD card)
for installation. I installed to the SD card OK and the build-in
emmc is visible as /dev/sd1.
>From (poor!) memory, the installation kernel gave a message that
On 6/30/14, Matthieu Herrb wrote:
> On Mon, Jun 30, 2014 at 06:04:11PM -0700, patrick keshishian wrote:
>> This prevents one to write a simple one-wire protocol
>> using the gpio ioctl interface, where a data pin needs to
>> switch directions between in and out. Which is where
>> I'm stuck ATM.
>
On Mon, Jun 30, 2014 at 06:04:11PM -0700, patrick keshishian wrote:
> Hi, yea, more on this
>
> Your argument about not knowing all the pins on all the
> different platforms, etc. I can see the point there, but(!) ...
>
> This prevents one to write a simple one-wire protocol
> using the gpio
Hi, yea, more on this
On 6/29/14, Matthieu Herrb wrote:
> On Sun, Jun 29, 2014 at 12:31:16AM -0700, patrick keshishian wrote:
>> On 6/29/14, Benjamin Baier wrote:
>> > You can set the default securelevel in /etc/rc.securelevel.
>> > The "logic behind that" is described in securelevel(7).
>>
On 6/29/14, Matthieu Herrb wrote:
> On Sun, Jun 29, 2014 at 12:31:16AM -0700, patrick keshishian wrote:
>> On 6/29/14, Benjamin Baier wrote:
>> > You can set the default securelevel in /etc/rc.securelevel.
>> > The "logic behind that" is described in securelevel(7).
>>
>> locking down pins when/i
On Sun, Jun 29, 2014 at 12:31:16AM -0700, patrick keshishian wrote:
> On 6/29/14, Benjamin Baier wrote:
> > You can set the default securelevel in /etc/rc.securelevel.
> > The "logic behind that" is described in securelevel(7).
>
> locking down pins when/if another device driver is attached
> to
On 6/29/14, Benjamin Baier wrote:
> You can set the default securelevel in /etc/rc.securelevel.
> The "logic behind that" is described in securelevel(7).
locking down pins when/if another device driver is attached
to them makes sense, but locking down idle pins ... i'm not
too sure. especially si
1 - 100 of 145 matches
Mail list logo
