John McGuigan | 29 Jun 22:46 2016
Picon
Picon

Killer board

Hi folks,

The discussion regarding the FriendlyARM SBCs and the focus on the
CuBox-i4Pro got me thinking about my ideal arm board. Personally, I think a
small ARM SBC would be perfect as a home router if it has 2 (or more)
Ethernet ports -- preferably gigabit, fanless, serial console (FTDI), etc.
I really like the Cavium port but I'm hoping there is something similar in
the ARM world.

Is anyone familiar with some ARM hardware that would fit that bill? I'd
really like to get my hands on some and help out the project. I think
support for a killer board could really drive up use of this port.

For the record, I'm not trying to steer the current devs away from the
CuBox or BBB but I'd like to engage this port in the best way possible.

Take care,

John

Karl Hammerschmidt | 29 Jun 06:21 2016
Picon

FriendlyARM SBCs

Is anyone else interested in their boards?

They were very willing to provide extra documentation when asked,
including a schematic for one of their LCD drivers and an unpublished
datasheet for the AXP228 PMIC used on some of their boards. They also
offered free boards to the FreeBSD guys several months ago, but there
were no replies.

It would be a different SoC, though (Allwinner H3, Samsung 4412, 4418,
6818). On a positive note, I haven't found any mention yet of closed
binaries like the ODRIOD C1. (Doesn't mean there aren't any, and I'm
still looking...)

Mattieu Baptiste | 26 Jun 13:05 2016
Picon

reproducible uvm_fault on bbb/-current

Hi,

When compiling arm-none-eabi, I'm encountering repeated uvm_fault:

Here is a full dmesg, panic, trace and ps.

U-Boot SPL 2016.05 (Jun 15 2016 - 15:57:27)
Trying to boot from MMC2
Card doesn't support part_switch
MMC partition switch failed
*** Warning - MMC partition switch failed, using default environment

reading u-boot.img
reading u-boot.img

U-Boot 2016.05 (Jun 15 2016 - 15:57:27 +1000)

Watchdog enabled
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - bad CRC, using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
Could not get PHY for cpsw: addr 0
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
(Continue reading)

Artturi Alm | 21 Jun 05:28 2016
Picon

misc not-so-tech <at> worthy question

Hi,

i'm unsure about the accepted way of working around irregular registers,
like would be needed with supporting Mentor OTG USB on both omap&sunxi
on armv7. irregular as in _no_ correlation what so ever, so off*4 kind
of solution does not apply.
My question in particular is; is (ab)using bus_space for this accepted
workaround?

NetBSD, where the driver got ported from, does have #ifdef MOTG_ALLWINNER
which is obviously not possible, given GENERIC and its nature as true
'uni-mono-kernel'. i was actually a bit shocked when i figured how many
arm kernel configs etc. they get to have maintenance-fun with if/when
necessary :)

reason why i think this is better than any other method to solve it in
run-time rather than compile-time is, because it wouldn't affect other
than the offender(=sunxi/Allwinner), no matter how ugly.

shortened(actually +30cases in switch below) to show something like
what i would propose:

struct armv7_bus_space_tag sxiotg_bustag;

void
sxiotg_attach(struct device *parent, struct device *self, void *args)
{
	/* ... */
	sxiotg_bus_init();
	sc->sc_motg.sc_bus.dmatag = &armv7_bus_dma_tag;
(Continue reading)

SASANO Takayoshi | 9 Jun 22:17 2016
Picon

armv7 with Banana Pi (BPI-M1)

Hello,

Is there any reports which succeeded to run OpenBSD/armv7
on Banana Pi BPI-M1?
I am trying now but it reboots with undefined instruction exception.

What should I do to solve this problem?

----
U-Boot SPL 2016.05 (Jun 02 2016 - 22:39:53)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2016.05 (Jun 02 2016 - 22:39:53 +0900) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: LeMaker Banana Pi
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

Setting up a 720x576i composite-pal console (overscan 32x20)
In:    serial
Out:   vga
Err:   vga
SCSI:  SATA link 0 timeout.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
(Continue reading)

Jonathan Gray | 29 May 16:02 2016
Picon

armv7 now has a bootloader

There is now a bootloader for armv7 thanks to kettenis <at> 
Recent armv7 snapshots will configure disks to use efiboot and install
device tree dtb files on a fat partition at the start of the disk.

u-boot kernel images are no longer part of the release but can still
be built for the time being.  We are going to start assuming the
kernel has been loaded with a dtb file to describe the hardware sometime
soon.  Those doing new installs can ignore the details but here they
are.

Support for EFI payloads was introduced in u-boot 2016.05, a port
was recently imported for u-boot along with a patch to prevent
it from allocating memory from non-populated regions (required for
non imx platforms).  A dtb port with prebuilt dtb files was also added.

If BOOTARM.EFI is placed on fat or ext2 as /efi/boot/bootarm.efi and
dtb files placed in /, /dtb/ or /dtb/current u-boot will automatically
load and run it without any boot.scr or uenv.txt needed.  efiboot will
then load kernel images off ffs filesystems it finds.  The u-boot
binaries themselves on the same partition or raw offset remain largely
board specific.

Farid Joubbi | 28 May 23:49 2016
Picon

Can't install current on bbb internal storage

Hi,

Since it's not possible to install 5.9 release on the internal storage, I
figured that I will try the latest snapshot from May 27th.

With the snapshot I am able to choose to install on both sd0 and sd1 which
was not possible with 5.9.
The installation goes for a while until I get "newfs: wtfs: write error on
block 160: Input/output error".
I think that the hardware is fine since I am able to install and run debian
on it without problems.

Any ideas?

Here is the output:

Available disks are: sd0 sd1.
Which disk is the root disk? ('?' for details) [sd0] sd1
Disk: sd1       geometry: 465/255/63 [7471104 Sectors]
Offset: 0       Signature: 0xAA55
            Starting         Ending         LBA Info:
 #: id      C   H   S -      C   H   S [       start:        size ]
-------------------------------------------------------------------------------
*0: 0C      0   1   2 -      2  11   9 [          64:       32768 ] Win95
FAT32L
 1: 00      0   0   0 -      0   0   0 [           0:           0 ]
unused
 2: 00      0   0   0 -      0   0   0 [           0:           0 ]
unused
 3: A6      2  11  10 -    465  13  60 [       32832:     7438272 ]
(Continue reading)

Mattieu Baptiste | 26 May 00:34 2016
Picon

latest snapshot on bbb doesn't boot after install

Hi,

I freshly installed the latest snapshot (may 25) on a BeagleBone Black.
The install process works flawlessly but it refuses to load the kernel
at first boot:

# halt -p
syncing disks... done

Attempting to power down...
The operating system has halted.
Please press any key to reboot.

rebooting...

U-Boot SPL 2016.05 (May 17 2016 - 17:11:59)
Trying to boot from MMC1
Card doesn't support part_switch
MMC partition switch failed
*** Warning - MMC partition switch failed, using default environment

reading u-boot.img
reading u-boot.img

U-Boot 2016.05 (May 17 2016 - 17:11:59 +1000)

Watchdog enabled
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
(Continue reading)

Daniel Bolgheroni | 25 May 15:49 2016
Picon

Kernel compile times on 2 supported boards

Hi,

I've been following armv7 recent changes and these days I was able to
compare kernel compile times on 2 of the supported boards.

The first is an omap BeagleBone Black with a NFS-mounted /usr/src. It's
pretty stable and I had no issues so far with what is supported.

The second is a sunxi CubieBoard 2 with the Allwinner A20 SoC. This one
has a 1.8" hdd instead.

BeagleBone Black:
(...)
ld -T ldscript --warn-common -nopie -S -o bsd ${SYSTEM_HEAD} vers.o ${OBJS}
text    data    bss     dec     hex
3684900 104816  470508  4260224 410180
   59m00.17s real    51m31.67s user     3m43.93s system

CubieBoard 2:
(...)
ld -T ldscript --warn-common -nopie -S -o bsd ${SYSTEM_HEAD} vers.o ${OBJS}
text    data    bss     dec     hex
3684128 104816  470080  4259024 40fcd0
  269m38.01s real   252m33.07s user    12m29.56s system

The sizes are slightly different because one source tree is maybe a
dozen commits ahead of the other, so no significant changes.

The cb2 host kernel has a small workaround published by Patrick Wildt on
bugs <at> , to only flush a TLB for a specified VA, not the entire TLB. It
(Continue reading)

Philipp Westphal | 24 May 21:32 2016

Sharp Zaurus C3000 -- suspend problems?


Hi, 

I know it might be a bit out of date Hardware, but I recently got my fingers on an C3000 (spitz). I replaced the
4GB Microdrive with a 32GB CF.

1. Installed pdaXii13 (build 5.4.9 "Alice")
2. installed OpenBSD 5.9 on the unusued part of the CF.

So faar everything works fine, the system runs stable enough to compile kernel and Userland (within 3 days
:D). But I can't get it to suspend/wake up.

Problem: 

a) lidsuspend (without X) --> white screen with backlight sucking battery 
   pressing power again: system resuming everything is fine.
b) lidsuspend (with X) --> white screen as before before, but pressing power button brings the zaurus back
to the console but it will not accept any key pressing --> so I have to reset the whole thing.

the same results are for zzz / zzz -s / zzz-Z or apm.

Thank you!
Philipp

PS. I hope this is the popper List for this.
Attachment (daemon): application/octet-stream, 7537 bytes
Attachment (dmesg.out): application/octet-stream, 3238 bytes
Attachment (messages): application/octet-stream, 5977 bytes
Attachment (sysctl.out): application/octet-stream, 32 KiB
Aaron Bieber | 23 May 21:58 2016
Gravatar

Can't boot Pandaboard ES with current snapshots (1463985060)

Simply flashing the miniroot image onto an SD card and booting will
result in:

reading uEnv.txt
162 bytes read in 3 ms (52.7 KiB/s)
Importing environment from mmc0 ...
Running uenvcmd ...
reading bsdrd.umg
10883512 bytes read in 507 ms (20.5 MiB/s)
## Booting kernel from Legacy Image at 82800000 ...
   Image Name:   boot
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    10883448 Bytes = 10.4 MiB
   Load Address: 80300000
   Entry Point:  80300000
   Verifying Checksum ... OK
   Loading Kernel Image ... Image too large: increase
   CONFIG_SYS_BOOTM_LEN
Must RESET board to recover
resetting ...

U-Boot SPL 2015.10 (Feb 01 2016 - 13:59:48)
OMAP4460 ES1.1

I was able to get the image to boot by bumping CONFIG_SYS_BOOTM_LEN, but
then I run into this:

Available disks are: sd0.
Which disk is the root disk? ('?' for details) [sd0] 
Disk: sd0       geometry: 1936/255/63 [31116288 Sectors]
(Continue reading)


Gmane