Dev

dev@lists.96boards.org

241 discussions

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, 1 month

[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, 1 month

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, 1 month

sorry, just test

by Libo (I)

11 years, 1 month

bl1 crash

by Stefan Johansson

So I built hikey ATF and l-loader for the first time and seemed to be able to flash the l-loader.bin However, the serial log shows this, what did I do wrong ? debug EMMC boot: print init OK debug EMMC boot: send RST_N . debug EMMC boot: start eMMC boot...... load fastboot1! Switch to aarch64 mode. CPU0 executes at 0xf9801000! INFO: BL1: 0xf9810000 - 0xf9817000 [size = 28672] NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.1(debug):a0c0399 NOTICE: BL1: Built : 09:31:15, May 28 2015 INFO: BL1: RAM 0xf9810000 - 0xf9817000 Platform exception reporting: ESR_EL3: 0000000002000000 ELR_EL3: 00000000f9803348 ...

11 years, 1 month

Re: [Dev] Is 96boards just another scam or another failing kickstarter project?

by Clint Cooley

Gregoire Total understand. As you may be aware Circuitco has been involved with OSHW for over 8 years. We are very excited about the 9 boards program and are comic red to making it a success and building a strong community. Thank you for your passion and I am also aware of your support of these types of communities We are happy to have you on board! Clint CooleyCircuitco Electronics LLCPresident -------- Original message -------- From: Gregoire Gentil <gregoire(a)gentil.com> Date: 06/12/2015 4:33 PM (GMT-06:00) To: Clint Cooley <clint(a)circuitco.com>, dev(a)lists.96boards.org Cc: customer.care(a)avnet.com, sales(a)circuitco.com Subject: Re: Is 96boards just another scam or another failing kickstarter project? Thanks for the answer and the clarification. It's more the lack of communication and the feeling to be in front of a black box à la Kickstarter that triggers my comment to the mailing list. I guess that I'm not the only one in this situation. I have waited for 4 months, at this point, I can probably wait for another week or so! Hopefully, customers (including me) are about to get those boards soon, Grégoire On 06/12/2015 02:27 PM, Clint Cooley wrote: > Hello Gregoire, > > Thank you for the escalation and my apologies for the lack of proper > communication. > > As you may know Circuitco did the hardware development and the initial > production for the Hikey board. Similar to any new product release > there have been some delays. The good news is production boards are > coming off our lines now and are shipping and hopefully stocked within > the next 5 days or less. > > I was unaware that Avnet actually allowed any purchase other than pre > order but will be happy to check in to this for you as we do work very > closely with them. > > The Hikey project is very real and I assure you not a scam. We have > actually delivered hundreds of pre production boards for Beta > development that was very well received. > > I am happy to directly address and facilitate a solution for you. Due > to customer confidentiality I will need to do this outside the public > forum. > > Please contact me directly at clint(a)circuitco.com. > > Thank you > > > Clint Cooley > President > Circuitco > > > > > > Clint Cooley > Circuitco Electronics LLC > President > > > -------- Original message -------- > From: Gregoire Gentil <gregoire(a)gentil.com> > Date: 06/12/2015 4:08 PM (GMT-06:00) > To: dev(a)lists.96boards.org > Cc: customer.care(a)avnet.com, sales(a)circuitco.com > Subject: Is 96boards just another scam or another failing kickstarter > project? > > To the project leader of 96 boards, > > > I have ordered through Avnet a HiKey board shortly after it was > announced. My order is dated February 19, four months ago (PO Number: > WEB5348914). And I still have received NOTHING. > > The shipping date has been pushed at least three times on the Avnet > website and the promise date is now /6/3/2015. BTW, today is 6/12/2015. > > I have contacted 96boards back a months ago and after a short email > exchange with CircuitCo (I still don't get it why my message was > forwarded to CircuitCo), I didn't receive neither a precise shipping > date, nor an explanation of what's going on. > > So can the project leader of 96boards.org explain the situation and > clarify if this project is just another scam or one of those failing > kickstarter project to deliver? How can I get a refund? Avnet is > refusing to reimburse. > > I don't know if I'm the only one in this situation, but this is a > complete poor experience. When I ordered, I didn't see a message like > "you are not going to receive your board soon". > > Grégoire > > PS: There is even not an email address on the 96boards.org website. Who > is in charge of this project?

11 years, 2 months

About enable software cursor of xf86-video-armsoc driver

by Xinliang Liu

Hello, since our SoC doesn't support hardware cursor, i want to enable SW cursor with xf86-video-armsoc driver. So i set the cursor API type to HWCURSOR_API_NONE in my driver. list as bellow. +struct drmmode_interface hisi_interface = { + 1 /* use_page_flip_events */, + 1 /* use_early_display */, + CURSORW /* cursor width */, + CURSORH /* cursor_height */, + CURSORPAD /* cursor padding */, + HWCURSOR_API_NONE /* cursor_api */, + NULL /* init_plane_for_cursor */, + 0 /* vblank_query_supported */, + create_custom_gem /* create_custom_gem */, +}; But when i run startx the X crash with log pasted bellow: And if i set the cursor API type to HWCURSOR_API_STANDARD, X can start up , but without cursor display. ---------------------xorg log start------------------- [ 92.153] (II) ARMSOC(0): drmmode_set_mode_major:428: Exiting [ 92.985] (EE) [ 92.985] (EE) Backtrace: [ 92.985] (EE) 0: /usr/bin/X (xorg_backtrace+0x5c) [0x7fb527075c] [ 92.985] (EE) [ 92.986] (EE) Segmentation fault at address 0x7fb50b7ffc [ 92.986] (EE) Fatal server error: [ 92.986] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 92.986] (EE) [ 92.986] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 92.986] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 92.986] (EE) [ 92.987] (EE) Server terminated with error (1). Closing log file. ---------------------xorg log end------------------- Does anybody know what's wrong it is? And how to enable SW cursor with xf86-video-armsoc driver? Best regards, xinliang

11 years, 2 months

Re: [Dev] Is 96boards just another scam or another failing kickstarter project?

by Clint Cooley

Hello Gregoire, Thank you for the escalation and my apologies for the lack of proper communication. As you may know Circuitco did the hardware development and the initial production for the Hikey board. Similar to any new product release there have been some delays. The good news is production boards are coming off our lines now and are shipping and hopefully stocked within the next 5 days or less. I was unaware that Avnet actually allowed any purchase other than pre order but will be happy to check in to this for you as we do work very closely with them. The Hikey project is very real and I assure you not a scam. We have actually delivered hundreds of pre production boards for Beta development that was very well received. I am happy to directly address and facilitate a solution for you. Due to customer confidentiality I will need to do this outside the public forum. Please contact me directly at clint(a)circuitco.com. Thank you Clint CooleyPresidentCircuitco Clint CooleyCircuitco Electronics LLCPresident -------- Original message -------- From: Gregoire Gentil <gregoire(a)gentil.com> Date: 06/12/2015 4:08 PM (GMT-06:00) To: dev(a)lists.96boards.org Cc: customer.care(a)avnet.com, sales(a)circuitco.com Subject: Is 96boards just another scam or another failing kickstarter project? To the project leader of 96 boards, I have ordered through Avnet a HiKey board shortly after it was announced. My order is dated February 19, four months ago (PO Number: WEB5348914). And I still have received NOTHING. The shipping date has been pushed at least three times on the Avnet website and the promise date is now /6/3/2015. BTW, today is 6/12/2015. I have contacted 96boards back a months ago and after a short email exchange with CircuitCo (I still don't get it why my message was forwarded to CircuitCo), I didn't receive neither a precise shipping date, nor an explanation of what's going on. So can the project leader of 96boards.org explain the situation and clarify if this project is just another scam or one of those failing kickstarter project to deliver? How can I get a refund? Avnet is refusing to reimburse. I don't know if I'm the only one in this situation, but this is a complete poor experience. When I ordered, I didn't see a message like "you are not going to receive your board soon". Grégoire PS: There is even not an email address on the 96boards.org website. Who is in charge of this project?

11 years, 2 months

Is 96boards just another scam or another failing kickstarter project?

by Gregoire Gentil

To the project leader of 96 boards, I have ordered through Avnet a HiKey board shortly after it was announced. My order is dated February 19, four months ago (PO Number: WEB5348914). And I still have received NOTHING. The shipping date has been pushed at least three times on the Avnet website and the promise date is now /6/3/2015. BTW, today is 6/12/2015. I have contacted 96boards back a months ago and after a short email exchange with CircuitCo (I still don't get it why my message was forwarded to CircuitCo), I didn't receive neither a precise shipping date, nor an explanation of what's going on. So can the project leader of 96boards.org explain the situation and clarify if this project is just another scam or one of those failing kickstarter project to deliver? How can I get a refund? Avnet is refusing to reimburse. I don't know if I'm the only one in this situation, but this is a complete poor experience. When I ordered, I didn't see a message like "you are not going to receive your board soon". Grégoire PS: There is even not an email address on the 96boards.org website. Who is in charge of this project?

11 years, 2 months

Hikey kernel crash on OE build

by Will Chen

Hi hikey_developers, I built OE hikey successfully, but the generated kernel will crash during booting. The attached files are conf setting and kernel crash log. Could you please check this issue? *Below are the build configurations:* willchen@willchen-NB:~/lhg/96board/hikey/oe/oe-core/hikey$ bitbake linux-hikey Parsing recipes: 100% |#########################################| Time: 00:00:39 Parsing of 1482 .bb files complete (0 cached, 1482 parsed). 1960 targets, 105 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.26.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS = "aarch64-oe-linux" MACHINE = "hikey" DISTRO = "nodistro" DISTRO_VERSION = "nodistro.0" TUNE_FEATURES = "aarch64" TARGET_FPU = "" meta = "fido:b266977372f2d5704d00dd07b29ea49898ebf70e" meta-oe = "master:a8b76a264155f4b9f6ba1bebe3ac87640a6f35ed" meta-96boards = "master:4f43c70d636d2b3ab5d20e2cdded0df353323c88" NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: Failed to fetch URL git:// sourceware.org/git/glibc.git;branch=release/2.21/master, attempting MIRRORS if available WARNING: QA Issue: linux-hikey: Files/directories were installed but not shipped /lib/firmware/sb16 /lib/firmware/sb16/alaw_main.csp /lib/firmware/sb16/ima_adpcm_playback.csp /lib/firmware/sb16/ima_adpcm_init.csp /lib/firmware/sb16/mulaw_main.csp /lib/firmware/sb16/ima_adpcm_capture.csp [installed-vs-shipped] NOTE: Tasks Summary: Attempted 407 tasks of which 0 didn't need to be rerun and all succeeded. BR, Will

11 years, 2 months

← Newer
1
...
14
15
16
17
18
19
20
...
25
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev