Dev

dev@lists.96boards.org

197 discussions

Improved supply situation for HiKey type boards and more ahead

by Thomas B. Rücker

Hi, Seems like LeMaker have designed their own version of a HiKey board: http://www.lemaker.org/article-57-1.html I'd hope this brings a better supply situation, as so far there seems to have been rather a lack of such. One reason why I went with the immediately available Dragonboard at that time. Also I've spotted a borad named "LeMaker Bass" on their site, that claims to have an Action Semi S900 SoC and is labeled 4/96: http://www.lemaker.org/article-47-1.html The description mentions "96boards compatible". I guess that means compliance, for some definition of such. Interesting times are ahead of us. -- Thomas

10 years, 11 months

Hikey USB OTG serial adapter issue

by Amit Khare

Hi, I am trying to flash my early access hikey board without success. I am trying to boot the board in "install bootloader" mode with pin 1-2 and 3-4 installed. The USB device is getting registered but gets disconnected. I can see others have faced similar issue but i can't find a fix for this problem dmesg log - [ 6888.363849] usb 1-1.1: Product: \xffffffe3\xffffff84\xffffffb0\xffffff84\xffffffb0\xffffffe3\xffffff8c\xffffffb2\xffffff8c\xffffffb2\xffffffe3\xffffff94\xffffffb4\xffffff94\xffffffb4\xffffffe3\xffffff9c\xffffffb6\xffffff9c\xffffffb6\xffffffe3\xffffffa4\xffffffb8\xffffffa4\xffffffb8 [ 6888.363853] usb 1-1.1: Manufacturer: \xffffffe4\xffffff95\xffffff87\xffffff95\xffffff87\xffffffe4\xffffff95\xffffff8e\xffffff95\xffffff8e\xffffffe4\xffffffa5\xffffff8e\xffffffa5\xffffff8e [ 6888.364651] option 1-1.1:1.0: GSM modem (1-port) converter detected [ 6888.364923] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB0 [ 6888.837543] usb 1-1.1: USB disconnect, device number 11 [ 6888.837936] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [ 6888.837996] option 1-1.1:1.0: device disconnected -- Regards, Amit Khare

10 years, 11 months

When is the dragonboard 410c going to be 96boards compliant?

by Thomas B. Rücker

Hi, Just what it says in the Subject: When is the dragonboard 410c going to be 96boards CE compliant? Just /one/ example: Schematics are still not available, although mandated by compliance spec. Has anyone seen the compliance report of the board and could shed some light on all those issues? I'd like to see it, if possible. Thanks! Thomas

10 years, 11 months

ATF: mcuimage - bl30

by Stefan Johansson

Hi, When I include mcuimage.bin from Apr 9 as bl30 in fip, my system gets caught in an endless reboot sequence. I use latest HiKey ATF and it works fine without bl30. With ATF from June it works fine to include bl30. Is this expected behaviour ? Thanks, Stefan

10 years, 11 months

HiKey boot issue with recent 96boards/edk2

by Jerome Forissier

Hi, I need some help with EDK2 on HiKey (1). After updating my hikey_optee project (2) with the latest 96boards/edk2 (3), I can't boot anymore. Is Grub now required to boot Linux? It seems that boot menu entries are hardcoded in (4), or am I missing something?. I could not really tell by reviewing the commit logs. Well in any case I'm getting the following menu: ~~~~~~~~ Fail to start BootNext. The default boot selection will start in 1 seconds [1] fastboot [2] grub on eMMC [3] grub on SD [4] Shell [5] Boot Manager Start: ~~~~~~~~ Entries 1-3 seem to do nothing, and just return to the same menu. Prior to this, EDK2 would boot Linux immediately as en EFI application, thanks to some entries in HiKey.dsc (5), which now seems to be ignored (are they really? similar entries are still present in 96boards/hikey which tends to indicate they're not obsolete). What should I do to boot my kernel? I'd rather avoid adding Grub to the boot sequence, which is already complex enough IMHO, but I can of course do that if it is the recommended architecture. Now, if I could simply adjust my HiKey.dsc, that would be great... (1) https://github.com/96boards/edk2 (2) https://github.com/linaro-swg/hikey_optee (3) https://github.com/96boards/edk2/commits/4984b34 (4) https://github.com/96boards/edk2/blob/de234273/HisiPkg/HiKeyPkg/Drivers/HiK… (5) https://github.com/linaro-swg/edk2/blob/1690ce6/HisiPkg/HiKeyPkg/HiKey.dsc#… Thanks, -- Jerome

11 years

HiKey and OpenOCD

by Peter Griffin

Hi folks, For anyone who is interested there is a open source OpenOCD / GDB WIP debug solution available for HiKey. I've created a wiki page here https://github.com/96boards/documentation/wiki/JTAG-on-HiKey Which documents the hardware setup, where you can get the code, and a overview of what is currently working. Thanks to Philip Attfield who has already provided some patches to overcome several issues I was facing with read_memory and GDB config. Please feel free to update the wiki page with any additional info you find out (thanks to Dan Thompson for already doing this), and patches making OpenOCD support for HiKey even better are most welcome :) regards, Peter.

11 years

What is the definition of "compliance" as governed by 96Boards/LINARO?

by "Thomas B. Rücker"

The 96boards project promises to bring standards, order and decorum to an otherwise fragmented and mutually incompatible world of development boards, be it for "consumer edition" or "enterprise edition" electronics. This is a laudable goal. It also promises "Makers" standardized interfaces, electrically and mechanically to build things around those boards. For anyone who tried to use an extension board from one board with another before, this will be close to promised land. To maintain order, one needs to maintain authority. In the world of 96 Borads this comes in the form of "compliance". Much thought was apparently spent by great minds on building up a system of compliance definitions, specifications and requirements. Both for Hardware and Software they covered a lot of bases. [1][2][3] They also recognized the needs of protecting the intellectual design property of board manufacturers and decided against mandating full documentation that would allow one to directly modify and produce an own board, based on a certified 96 board. The great goal is, that by the end of 2015 we shall see 96 boards available and compliant with 96 Boards. Oh what a hootenanny that will be! So far we've seen two CE boards reach availability on the market. Some CE boards and an EE boards are in various stages of publicity. It is logical to assume that not only will those companies with announced boards, but also those who are going to announce and bring the remaining 90 boards to market, will turn not only to the aforementioned compliance documentation, but they will also closely examine the two boards that have already received the prestigious 96 Borads certification. For those two Boards must be shining examples, pioneering these waters with the expert help of Navigators who drew the compliance maps of the 96 Boards world and provided exact steps. … That is where I become sad, because I fail to resolve the dissonance between reality and the maps of the world, vulgo the compliance spec. Bear with me while I explain. I recently found myself trying to understand how the GPS in the Dragonboard 410c that I recently bought, to gain some AArch64 experience, is wired to the APQ8016 SoC. Someone had asked me if it would be possible to get NMEA from it, and I thought, well that's going to be easy to find out, after all it's a 96 Board compliant product, as it prominently features on their page. I turned to the 96boards.org page for the 410c [4], as there I would find the necessary documentation. You won't be able to imagine my surprise, when I reached the page and where the hyperlink to the schematics should be stands this text: "The DragonBoard 410c Schematics/BOM (Coming soon)" I then looked at the Hardware Manual [5], trying to keep my hopes up, grasping for the last straw. Well it told me something about "SSBI + IQ", that was something, although I'm still not sure what this actually means. The "Qualcomm ® Snapdragon TM 410 Processor (APQ8016) - Device Specification", linked from [4] mentions it as a "Single-wire SBI", where SBI is apparently some kind of "Serial bus interface". But in which way it is _actually_ wired up, we possibly might never find out. This led me to another train of thought. I hopped on and crossed the land of 96 Boards to arrive back at the compliance page [1]. For it states: "An SoC technical reference manual *shall* be available This *shall* include sufficient information for developers to be able to create board drivers and software interfaces for the supported SoC features." (emphasis from [1]) This confuses me even more, as I can't find from the linked documentation in [4] anything that would cover information necessary to "create board drivers" for the WGR640 GNSS (GPS) chip on the 410c board. Also there *shall* be a open source boot loader. Maybe I've embarked on too many optical experiments, but I can't see the Aboot source for the Ubuntu builds[6] I didn't bother looking at the HiKey board and how it fares in comparison. It's made out of the usual unobtainium as previous animal boards and will probably only ship in homeopathic doses for the next few months. That makes it rather uninteresting and unlikely to acquire a significant community, certainly not going to usurp the RPi throne. Personally this leaves me seeing "Mene, Mene, Tekel, Upharsin." written on the wall, for 96 Boards thou art weighed and thou art found wanting. Of course I might be wrong, maybe the RFC 2119 style language found in [1][2][3] uses different definitions of terms like SHALL, maybe it doesn't mean MUST, but "should, maybe, at some point"? Then I guess everything could be just A-OK and all the remaining boards will all start shipping by the end of the year. What this would mean in relation to the initially stated goals, I'm not sure. I guess it's compliant, depending on your definition of compliant. Thomas 1: https://www.96boards.org/about/compliance/ 2: http://www.96boards.org/ce-specification 3: http://www.96boards.org/ee-specification 4: https://www.96boards.org/products/ce/dragonboard410c/ 5: https://github.com/96boards/documentation/raw/master/dragonboard410c/Hardwa… 6: http://builds.96boards.org/releases/dragonboard410c/linaro/ubuntu/latest/

11 years

[ANN] Linaro Linux/Ubuntu 15.07 release for DragonBoard 410c is available

by Nicolas Dechesne

hello there, A new release Linux release for the DragonBoard 410c is now available. The Linaro Linux release 15.07 is an Ubuntu-based Linaro Build that provides developers with a desktop like environment using Ubuntu and the LXDE desktop, as well as a console-only image. What’s new in 15.07 release? * Upgrade to Mesa 10.6.2 * Bluetooth support is now available by default at boot * Initial support for h/w accelerated video playback using Gstreamer (v4l2dec plugin) * Migrate kernel distro configuration to distro.config file * Various improvements in display/monitor support, especially with low resolutions. * Various fixes for bugs reported since 15.06 release For more details and the list of bug fixes, or to download the release, please go to: http://builds.96boards.org/releases/dragonboard410c/linaro/ubuntu/15.07 For general question or support request, please go to 96boards Community forum: https://www.96boards.org/dragonboard410c/forum For any bug related to this release, please submit issues to the 96Boards Bug tracking system: https://bugs.96boards.org/enter_bug.cgi?product=Dragonboard%20410c Finally, to get in touch with us, you can also use IRC: #96boards on irc.freenode.net On behalf of the Linaro Qualcomm Landing team, Cheers, Nicolas

11 years

Dragonboard Linaro images - IPv6

by "Thomas B. Rücker"

Hi, After some unrelated delay, I have started using my Dragonboard. I downloaded a Linaro customized Ubuntu image: dragonboard410c_sdcard_install_ubuntu-40-47.zip from: http://builds.96boards.org/releases/dragonboard410c/linaro/ubuntu/latest/ I was very surprised to find out that the IP network stack is broken on this image (cf. RFC 6540). The Kernel has been built with IPv6 disabled. This means I can't reach a substantial part of my test network and my production systems. Who at LINARO do I need to poke to get this fixed? Thomas PS: The ZIP file contains a license file that seems to imply that ALL contents are copyright QTI and subject to a proprietary license. I'm rather sure Linus and a few other people would disagree with that. Someone might want to fix that.

11 years

sorry, just test

by Libo (I)

11 years

← Newer
1
...
9
10
11
12
13
14
15
...
20
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev