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.
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
 grub on eMMC
 grub on SD
 Boot Manager
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...
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
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 :)
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.  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 , 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 , 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  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 . 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 )
This confuses me even more, as I can't find from the linked
documentation in  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
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
 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.