Silently a new 96board starts appearing: Cello
It seems to be produced by LeMaker and is based around the AMD A1100
SoC. That's the same as on the illusive Husky, actually both boards look
very similar with only minor differences in the placement of some
connectors.
The LeMaker product page has it up for preorder for 299$; with an
estimated shipping time frame of 2016Q2.
http://www.lenovator.com/product/103.html
This could mean the first "cheap" 64 bit ARM server board becoming
available. Also more power: A57 cores.
Though I'm sure hrw will still disapprove as it has SATA, but is a weird
non-industry-standard form factor.
Oh, and the obligatory question:
Will it be 96boards compliant and are we going to get to see the actual
compliance report?
Cheers
Thomas
I have an HiKey Early Access Board which I assume is made by CircuitCo.
I have connected it to a HDMI display and USB keyboard/mouse.
When I plug in a 12v PS, and click on the power button, after a
few seconds LED 1 lights and stays on, LED 0 flashes a couple
times and goes out.
Nothing else happens. I don't get any signal to the display.
Am I doing something wrong? Any suggestions?
--
Michael Eager eager(a)eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
Hi,
So, LC BKK came and went, and now I'm back, sounding like a broken record:
- Compliance report: HiKey (CCo)
- Compliance report: HiKey (LeMaker)
- Compliance report: Dragonboard410c
- Compliance report: Bubblegum
- Compliance report: Cello
- Compliance report: Husky
- Compliance Check-List
- Other latest work (cf. mail on this list 2016-02-05T11:11)
- Anything of significance at LCBKK?
Please.
If anyone has /any/ doubt about why I'm asking for all those compliance
reports:
"Once a compliance report has been approved the vendor may use the
96Boards branding and logo according to published terms and conditions,
and the vendor product will be added to the 96Boards website(s)."
-- http://www.96boards.org/compliance/#Compliance
All boards mentioned above are on the website and their vendors show the
"96Boards branding and logo".
So with all due respect and excuse my french:
Reports or GTFO!
Cheers
Thomas
PS: Someone broke a Wordpress plugin on http://96borads.org
Ugh. The rev-c 96Boards Sensors mezzanine got shipped without a
bootloader on the ATMEGA. You'll need to flash the bootloader
yourself, or return the board to get it reflashed. (I recommend doing
it yourself. It's very simple to do).
I'm working with Seeed to get the boards shipped from the Seeed Bazaar
reflashed.
Here are the instructions. Do this with the Sensors board DISCONNECTED
from the baseboard.
https://www.arduino.cc/en/Tutorial/ArduinoISP
Let me know when you've fixed your board. I'm keeping a list.
g.
Hi all,
I found one bug for enabling Hikey's usb gadget driver; this bug only
happen when I use linux-linaro-lsk-v4.1-android but
linux-linaro-lsk-v4.1 has no such issue.
The detailed info for this bug is: When system bootup, I use configfs
to enable ethernet on USB, kernel dumps below backtrace.
After narrow down this issue, found below patch introduce this issue:
commit 3fdf0dcfea876a0d730da5544f947b0a19c37fdc
Author: Badhri Jagan Sridharan <Badhri(a)google.com>
Date: Wed Sep 24 18:58:23 2014 -0700
usb: u_ether: Add workqueue as bottom half handler for rx data path
u_ether driver passes rx data to network layer and resubmits the
request back to usb hardware in interrupt context. Network layer
processes rx data by scheduling tasklet. For high throughput
scenarios on rx data path driver is spending lot of time in interrupt
context due to rx data processing by tasklet and continuous completion
and re-submission of the usb requests which results in watchdog bark.
Hence move the rx data processing and usb request submission to a
workqueue bottom half handler.
Change-Id: I316de8e267997137ac189a8b7b2846fa325f4a5a
Signed-off-by: Badhri Jagan Sridharan <Badhri(a)google.com>
I'm not familiar with USB driver, so want to get some suggestion to fix
this issue. BTW, I also searched this patch, but this patch have not
been really merged into mainline kernel.
Thanks,
Leo Yan
--- Kernel dump log ---
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
[ 11.638907] using random self ethernet address
[ 11.643381] using random host ethernet address
[ 11.677646] usb0: HOST MAC 0a:70:5f:8a:c1:aa
[ 11.682136] usb0: MAC 1e:84:31:c3:50:0f
[ 11.689207] dwc2 f72c0000.usb: bound driver configfs-gadget
[ 11.701933] dwc2 f72c0000.usb: bound driver configfs-gadget
SIOCSIFHWADDR: Device or resource busy - you may need to down the interface
root@linaro-developer:~# [ 12.009430] dwc2 f72c0000.usb: new device is high-speed
[ 12.094179] dwc2 f72c0000.usb: new device is high-speed
[ 12.164194] dwc2 f72c0000.usb: new address 53
[ 12.191379] configfs-gadget gadget: high-speed config #1: c
[ 12.256053] ------------[ cut here ]------------
[ 12.260753] WARNING: CPU: 0 PID: 0 at kernel/workqueue.c:1369 __queue_work+0x2dc/0x354()
[ 12.268861] Modules linked in:
[ 12.271932] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.1.15+ #86
[ 12.278033] Hardware name: HiKey Development Board (DT)
[ 12.283265] Call trace:
[ 12.285722] [<ffffffc00008a928>] dump_backtrace+0x0/0x164
[ 12.291131] [<ffffffc00008aaac>] show_stack+0x20/0x28
[ 12.296196] [<ffffffc0006f0b38>] dump_stack+0x84/0xc4
[ 12.301260] [<ffffffc0000bc960>] warn_slowpath_common+0xa8/0xdc
[ 12.307192] [<ffffffc0000bcae0>] warn_slowpath_null+0x38/0x44
[ 12.312959] [<ffffffc0000d51d8>] __queue_work+0x2dc/0x354
[ 12.318377] [<ffffffc0000d52d0>] queue_work_on+0x80/0xa4
[ 12.323712] [<ffffffc00057e748>] rx_complete+0xd4/0x1ac
[ 12.328958] [<ffffffc00057c110>] usb_gadget_giveback_request+0x2c/0x38
[ 12.335510] [<ffffffc0005516d4>] s3c_hsotg_complete_request+0xdc/0x1ec
[ 12.342059] [<ffffffc000553e08>] s3c_hsotg_handle_outdone+0xa4/0x1d0
[ 12.348433] [<ffffffc0005541d0>] s3c_hsotg_epint+0x29c/0x6f4
[ 12.354112] [<ffffffc000554dd8>] s3c_hsotg_irq+0x408/0x734
[ 12.359621] [<ffffffc00010fca4>] handle_irq_event_percpu+0x64/0x210
[ 12.365909] [<ffffffc00010fea4>] handle_irq_event+0x54/0x80
[ 12.371501] [<ffffffc000112f6c>] handle_fasteoi_irq+0xb4/0x178
[ 12.377355] [<ffffffc00010f214>] generic_handle_irq+0x3c/0x54
[ 12.383121] [<ffffffc00010f564>] __handle_domain_irq+0x6c/0xbc
[ 12.388972] [<ffffffc000082494>] gic_handle_irq+0x3c/0x88
[ 12.394388] Exception stack(0xffffffc000a83d30 to 0xffffffc000a83e50)
[ 12.400850] 3d20: d91bd3d5 00000002 00b0bce0 ffffffc0
[ 12.409063] 3d40: 00a83e70 ffffffc0 005ae31c ffffffc0 00000000 00000000 005ae318 ffffffc0
[ 12.417275] 3d60: 00a80000 ffffffc0 005d8518 ffffffc0 00000020 00000000 004ea4a9 00000000
[ 12.425487] 3d80: 5fe6aba0 00023c34 00000019 00000000 b5193519 00000032 00084800 ffffffc0
[ 12.433697] 3da0: 00000000 00000000 00000000 00000000 34d5d91d 00000000 00000000 00000000
[ 12.441908] 3dc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 12.450120] 3de0: 00000000 00000000 d91bd3d5 00000002 00b0bce0 ffffffc0 3a3bfe00 ffffffc0
[ 12.458332] 3e00: 00000002 00000000 00000001 00000000 00000000 00000000 d8fad491 00000002
[ 12.466544] 3e20: 00a64b50 ffffffc0 00a6a1d8 ffffffc0 007099b0 ffffffc0 00a83e70 ffffffc0
[ 12.474753] 3e40: 005ae318 ffffffc0 00a83e70 ffffffc0
[ 12.479822] [<ffffffc0000855ac>] el1_irq+0x6c/0xe0
[ 12.484634] [<ffffffc0005ae568>] cpuidle_enter+0x30/0x3c
[ 12.489967] [<ffffffc0000fff98>] call_cpuidle+0x44/0x78
[ 12.495212] [<ffffffc0001001f8>] cpu_startup_entry+0x22c/0x314
[ 12.501064] [<ffffffc0006ebc44>] rest_init+0x8c/0x94
[ 12.506051] [<ffffffc0009b3980>] start_kernel+0x394/0x3a8
[ 12.511466] ---[ end trace 7240af96fd6fdc18 ]---
Just for anyone interested, I've been releasing experimental disk images
of CoreOS [1] for the HiKey ARM64 developer board. These images
currently have about 90% of the packages in the CoreOS developer build.
See the README at https://github.com/glevand/hikey-coreos.
[1] https://coreos.com/
-Geoff
I am having issues getting the HiKey to enter bootloader mode by linking J15
pins 1-2, 3-4 (the board always boots not matter what).
is there a work around to reprogram the bootloader?
--
jro
We are happy to announce the 16.03 release for the Reference Software
Platform project, right before Linaro Connect BKK16!
This is our third release, incorporating quite a few changes and
improvements for both the consumer and enterprise reference platforms.
We are also happy to share, for the first time, that we were able to
produce a common and unified kernel tree (4.4.0 based) that is shared
across all the supported platforms!
The unified kernel is a critical piece as we can concentrate the
development and validation into one single source tree, and also
allowing us to create one package (deb/rpm) that can be shared with
everyone. As a result of the integration of many different development
trees, we are also able to quickly spot issues that could later affect
upstream and distros (e.g. DT x ACPI).
Some of the highlights for this release (check
https://github.com/96boards/documentation/wiki/RPB-16.03-Highlights
for the complete list):
Unified Kernel:
- Unified tree shared between the CE and EE builds, supporting Hikey,
Dragonboard, D02, APM X-Gene, HP Proliant m400 and AMD Overdrive.
- 4.4.0 based, including under-review topic branches to extend the
hardware support for the platforms available.
- Device-Tree support for CE; ARM ACPI and PCIe support for Enterprise.
- Single kernel config for all platforms in arch/arm64/configs/distro.config
Consumer Reference Platform:
CE Debian RPB:
- Upgrade to Debian 8.3 "Jessie"
- Upgrade to the unified 4.4.0 Linux Kernel
- DB410c: Freedreno X11 video driver included by default (1.4.0)
- HiKey: Grub 2 config supporting kernel package updates
CE AOSP RPB:
- AOSP Android Marshmallow 6.0 (android-6.0.1_r16)
- Early Developer Preview snapshot for DragonBoard™ 410, supporting
Mesa and Freedreno
Enterprise Reference Platform:
Platforms Supported:
- AMD Overdrive A0 (new) and B0
- D02
- APM X-Gene Mustang (new)
- HP ProLiant m400 (new)
Features: UEFI with ACPI, KVM and PCIe support
Firmware: Updated UEFI/EDK2 for D02, including support for PCIe and SAS
Network Installers:
- Upgrade to Debian 8.3 "Jessie"
- CentOS (now supported): Based on CentOS 7.2 15.11
Install instructions, known issues, test reports and instructions to
build from source are all published at
https://github.com/96boards/documentation/wiki/Reference-Platform-Home.
For general questions or support requests, please go to the
96boards.org Community forum (https://www.96boards.org/forums/). For
development questions and topics, please use the 96Boards.org
development mailing-list (dev(a)lists.96boards.org).
For bugs related to the 96Boards platforms, please use the 96Boards
bug tracking system (https://bugs.96boards.org/). For bugs related to
the reference software platform release, but on development boards
that are not officially part of 96Boards, please use
https://bugs.linaro.org instead (e.g. AMD Overdrive and HiSilicon
D02).
For IRC support, please go to the #96boards channel at Freenode.
Since Linaro Connect BKK16 is just around the corner, please also make
sure to check the sessions involving 96Boards and the Reference
Software Project. Sessions we will cover next week:
* BKK16-100: Evolution of the Reference Software Platform Project
* BKK16-501: Kernel and bootloader consolidation and upstreaming
* BKK16-505: Mezzanine Enablement
Also make sure to check https://bkk16.pathable.com/ for the full schedule!
We hope you enjoy the release, and have a great Linaro Connect BKK16!
On behalf of the Linaro 96Boards team,
Ricardo Salveti
Hi all,
For the upcoming 16.03 release of the reference platform, we've been
working on a unified kernel that works on Hikey, Dragonboard 410c and
also enables enterprise HW that we have access to (D02, Overdrive, APM
XGene).
That kernel is now pushed to github[1] to the 96b/releases/2016.03
branch. It is based on the upstream kernel v4.4 and combines the work
from the Hisilicon and Qualcomm landing teams with the enterprise bits
coming from the Linaro Enterprise Group. A big thanks for their
assistance in sorting out various integration issues.
Please note that this kernel tree will now be used only to host a
unified kernel. The Hisilicon landing team has graciously agreed to
modify their workflow and move their kernel tree to the 96boards-hikey
namespace[2] on github.
I'll be talking about the experience of putting together this tree at
Connect BKK16 (including some patch statistics) and soliciting
feedback on the roadmap for this kernel tree - please get in touch if
you have ideas.
Look forward to more information about the release itself from Ricardo later.
Regards,
Amit
[1] https://github.com/96boards/linux.git
[2] https://github.com/96boards-hikey
Hi, Nico and Fathi
https://github.com/96boards/96boards-tools/commit/7d2d6c5d4f3f4a1488fe75024…
Bruce from Lemaker reported this issue when he tries to use
'resize-helper.sh' to resize his SD card on HiKey. Here is his log.
Would you please have a check? Does his procedure correct?
-Guodong
On 27 January 2016 at 10:19, bruce.zou <bruce.zou(a)lemaker.com> wrote:
> Hi，
>
>
>
> 昨天聊的这个问题，帮忙看看哈。重启后没有任何变化。
>
>
>
> root@linaro-alip:~# lsblk
>
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
>
> mmcblk0boot0 179:64 0 4M 1 disk
>
> mmcblk0boot1 179:128 0 4M 1 disk
>
> mmcblk0 179:0 0 7.3G 0 disk
>
> ├─mmcblk0p1 179:1 0 1M 0 part
>
> ├─mmcblk0p2 179:2 0 1M 0 part
>
> ├─mmcblk0p3 179:3 0 1M 0 part
>
> ├─mmcblk0p4 179:4 0 8M 0 part
>
> ├─mmcblk0p5 179:5 0 2M 0 part
>
> ├─mmcblk0p6 179:6 0 64M 0 part /boot/efi
>
> ├─mmcblk0p7 179:7 0 256M 0 part
>
> ├─mmcblk0p8 179:8 0 256M 0 part /media/linaro/cache
>
> └─mmcblk0p9 179:9 0 6.7G 0 part
>
> mmcblk1 179:192 0 7.4G 0 disk
>
> ├─mmcblk1p1 179:193 0 68M 0 part /media/linaro/boot
>
> └─mmcblk1p2 179:194 0 2G 0 part /
>
> root@linaro-alip:~# ./resize-helper.sh
>
> Warning: The kernel is still using the old partition table.
>
> The new table will be used at the next reboot.
>
> The operation has completed successfully.
>
> Error: Partition doesn't exist.
>
> resize2fs 1.42.12 (29-Aug-2014)
>
> The filesystem is already 506880 (4k) blocks long. Nothing to do!
>
> root@linaro-alip:~#
>
>
>
>
>
> *Bruce Zou*
>
>
> *Making Innovation EasyLeMaker Team -- The Professional Makers for
> Hardware and Software Customization.*
>
> Address: B1002, SIAT campus, Shenzhen University Town, Shenzhen, China
> Post Code: 518055
>
> Email:
> support(a)lemaker.org (Technical Support)
> product(a)lemaker.org (Product Distribution)
>
> http://www.lemaker.org/
>
>
>
