hisilicon poplar kernel source #39
Comments
|
You can run an image that is already in flash. We will be pushing out a Poplar Github landing page by the end of the week, until then I would suggest utilizing the resources available by Tocoding: http://en.tocoding.com/index.php/96boards-poplar/ I will leave this issue open in the mean time. Thanks! |
|
Okay great! Thank you for the reply Robert. I guess we will have to use a |
|
Any updates on the landing page? I didnt see anything up yet for poplar. If there is anything I can do to help please let me know... |
|
Right now I am still waiting on some key players to begin their contributions to the landing page. I will do my best to get as much core information up to the 96Boards github this week. In the mean time, you can find the Poplar repository under my personal github: www.github.com/sdrobertw/Poplar Sorry for the inconvenience, I expect things to be coming together soon. |
|
Thank you for the informative response Robert! I apprciate the update and github link. |
|
I've created my own github page for poplar dedicated to Android TV builds. I just got my board in so ill be testing some builds tonight, not even sure if the device tree or vendor blobs/binaries are correct but it's a work inprogress :) |
|
Just a quick question. How do we enter fastboot mode on the poplar the manual isnt too clear? I can understand all jumpers off is default emmc... The 96Boards Poplar board allows system to boot from the SPI flash, NAND flash, fSD, The value of BOOTSEL2, BOOTSEL1, or BOOTSEL0 is as follows: |
|
Can you help with this please? |
|
There does seem to be an S1 recovery button but when held down during power does nothing to enter fastboot. Thanks for any pointers 96 team... |
|
Okay I sucessfully got fastboot in bootloader now buy ctrl+c immmediatly at boot but now how to enter fastboot? From my experience the command fastboot enters fastboot usb protocol. Does tocoding use an imx type usb tool for uart flashing? I've been in contact with support and I am awaiting a response on the proceedure. Here is the correct minicom settings: sudo minicom -b 115200 -o -D /dev/ttyUSB0 ctrl+A the Z then O select serial port settings. Software flow: ON One other side note I wasnt aware that they are only selling 1GB RAM version on Ali. Hopfully they will stock the 2GB version also because 1GB isnt very adequate. Might want to change the specs on 96 boards poplar page. "DRAM DDR3/3L/4 SDRAM interface, maximum 32-bit data width 2 GB on board" |
|
Still have not heard a thing from tocoding on how to flash thru UART. I'd love to try some of my custom builds or even a repacked system image but no idea how to reflash in fastboot. My poor poplar is just collecting dust now... |
|
@mattgorski I am very sorry, I am really trying to find someone to help with this. Unfortunately I do not own a Poplar nor do I have an experience with it. I have been hunting down people who can help since this issue started. Sorry for the inconvenience. -Robert W. |
|
In addition to lack of documentation of the current state, is there any "proper" bootloader in the works by Linaro, such as Tianocore or U-Boot? It's disappointing to see Poplar regress compared to HiKey. |
|
Hi @mattgorski, to enter fastboot you need to hit Ctrl-c on the serial line during the first seconds of the boot. To download the boot image: To download the Linux image: File system image: Kernel Source is still not available for the board, we are trying to speed up the process so it gets released ASAP. |
|
@mattgorski did this help? I would like to close this issue until more Poplar information is available. Please get back to me. Thank you. Robert Wolff - www.96board.org/openhours |
|
@sdrobertw The title says "kernel source" - and without sources we have no FTR playing with the above instructions shows that "Fastboot 3.3.0" is in fact a U-Boot fork (whose sources will be needed, too), unrelated to Android's fastboot protocol/tool. To speed up the process of getting all those sources, have you considered taking down the "Buy Poplar Board" link from 96boards.org until the products sold comply with the GPL? You don't show any on the Latest Boards and Enterprise Edition overview pages, but on the Poplar product page there is one. Isn't release of schematics and sources a compliance criteria for your specification? |
|
Great to see all the detailed responses. I really have had no time to do any custom flashes yet, will be much easier when we have the kernel source and vendor binaries. One thing that is disappointing to see on the poplar is the deinterlacing with Mali. Almost unusable as an Android TV device due to this. I really hope this is fixable with some codec configs and upgraded mali gl binaries. |
|
@afaerber : The current status on Poplar source is out of our hands, though we do have control over the website and your recommendations make a lot of sense, it is a very legitimate observation, one that I will surely pass up the line asap. Thank you very much for your contribution to this thread, once again I am very sorry for the inconvenience. @mattgorski : I am going to keep this issue active, we appreciate your contributions and hope to help get these issues resolved asap. We will continue to push for answers and provide them to you as we become informed. Thanks, R.W. |
|
Thanks again for everything @sdrobertw and all who contributed to this issue (a big thanks to @kuscsik for the tftp flash instructions), I am sure we have gotten the wheels rolling faster with more interest. I will make some time to try the device tree with prebuilt kernel I made awhile back (https://github.com/96Boards-AndroidTV). At least we can get some testing done on some modified system images repacked and built with tv permissions in mind not tablet ;) |
|
@kuscsik would it be possible to get the u-boot includes/config for poplar so we can implement the android fastboot sparse image format so we can use the USB OTG interface for flashing images? I've implemented fastboot on a couple non Android devices so I can lend a hand... EDIT: Actually can OTG ADB/Fastboot even be used on poplar? It uses the front otg port with the FTDI USB converter not the standard OTG usb port. Might be able to use a standard USB port with a male-to-male USB cable... |
|
I am attempting to flash a new system image today and I noticed in the tftp instructions that the rootfs you are flashing is yaffs (android 4.x) yet the tocoding flash package has a system.ext4 which i am also building for. So do i convert to yaffs or substitute ext4 for yaffs? Kinda confused again here I just wish we could fastboot flash and be done.. TARGET_USERIMAGES_SPARSE_EXT_DISABLED := true Guess the ol poplar goes back into hiding again until we can flash a system.img :( |
|
Okay different approach. @kuscsik What is the hex offset for recovery flashing? I'll just get a TWRP recovery built and we can bypass the uboot/fastboot until we can build a proper android u-boot. One other thing is the flash package comes with an xml config for flashing so how do we implement this? Nvidia uses a similar protocol with the nvflash APX recovery. There must be a hidden function we are unaware of.... example:
Hi3798CV200-emmc.xml
|
|
Not getting the tftp to work. I have followed the basic tftp guide here setting server ip: http://processors.wiki.ti.com/index.php/Booting_Linux_kernel_using_U-Boot And get this error: fastboot# tftp 1000000 system.ext4 I must not have my network params correct. ipaddr=192.168.1.10 - poplar ip addess set in u-boot/fastboot Tried multiple settings.... i know my tftp server is running. Is there any other way to flash??? This mysterious Hi3798CV200-emmc.xml was definitely made to be the easy way to flash but WHERE ARE THE INSTRUCTIONS??? |
|
Any news on this ? Will we be able to compile AOSP 7.0 for the Poplar aswell ? I'm interested in this board but only if I can compile up to date android versions for it. |
|
Looks like we will have sources at least after next week. For 6.0/7.0/7.1 we will have to wait and see how caught up to mainline google the kernel is for selinux and such. Here is the latest word from tocoding as of this morning: Issue pertaining to no fastboot instructions in flash package:
|
|
Just got the word from tocoding that they have released the sources to Linaro 2 weeks ago. So any update on the sources guys :) |
|
FYI, I just got answer on my 2 months old request regarding creation of Poplar subforum on Linaro's 96Borad. Not as speedy as needed, but anyway ... Also I finally finished firmware for 3716cv100 so I'm moving to Poplar. |
|
It's near the end of the April 2017, Is the AOSP released now? Any one knows? If the sources/resources are released, I want to buy some Polar boards. |
|
I would love to know myself if anyone has even built an android build and if so how did they even flash with no flash tools.... Been over 6 months and this board has zero love. |
|
Any news on the 25th Feb posting? It's now gone past the end of April. |
|
From the Status of Android “AOSP” TV – BUD17-118 presentation at Linaro Connect BUD17: http://connect.linaro.org/resource/bud17/bud17-118/ , it seems that "migrate to 96Boards " is the last item of the Next 6 month plan (See the PPT, Page 8). Also, here, hikey appears, no polar. I guess maybe resources wouldn't be released in near future.? Below is the page 8 from PPT:
|
|
Initial U-Boot patches have arrived on u-boot mailing list on Thursday, along with a README for flashing. |
|
Hello all, For several months now, Linaro has been working together with HiSilicon to provide the community with access to source code for the Poplar board. This week an initial drop of source code for the Poplar board, along with flashing tools and some documentation will be made available on GitHub. The initial code drop will include source for ARM Trusted Firmware, U-Boot, and a 4.11 based upstream kernel along with documentation on how to build the software and tools to flash it to the Poplar board. This release of source code, tools and documentation provides:
This drop of source code is just a start. This code allows us to boot to a console using the source code and tools provided. We have begun to upstream this source and will continue to add features and update the repositories on a more regular basis. The team's goal is to release source as functionality is completed, tested and passes an internal IP review. There is still more more to do with the bootloaders and partitioning of the eMMC which we will work on over the next couple of months. Kernel features due for release in the next month are HDMI support, and keyboard/mouse support. We are also planning to provide a branch in the kernel tree that will be based on the Android 4.9 common kernel. This won’t be upstream based, but will be more feature complete than our mainline branch. This will be used to support AOSP running on the Poplar board. As we push topics and changes to the GitHub repositories, we will post a message to the forums to update people here. I will provide another update on our overall progress and plans in early June. Scott Bambrough |
|
This is FANTASTIC news! So where will the GitHub source be located?
…On May 8, 2017 3:40 PM, "Scott Bambrough" ***@***.***> wrote:
Hello all,
For several months now, Linaro has been working together with HiSilicon to
provide the community with access to source code for the Poplar board. This
week an initial drop of source code for the Poplar board, along with
flashing tools and some documentation will be made available on GitHub.
The initial code drop will include source for ARM Trusted Firmware,
U-Boot, and a 4.11 based upstream kernel along with documentation on how to
build the software and tools to flash it to the Poplar board.
This release of source code, tools and documentation provides:
- The ability to boot in 64-bit mode.
- Console functionality via the micro USB port.
- Network via ethernet.
- All cores enabled.
- USB device support (disk & network adapter)
- The ability to flash the board via USB flash drive.
- Documentation
This drop of source code is just a start. This code allows us to boot to a
console using the source code and tools provided. We have begun to upstream
this source and will continue to add features and update the repositories
on a more regular basis. The team's goal is to release source as
functionality is completed, tested and passes an internal IP review.
There is still more more to do with the bootloaders and partitioning of
the eMMC which we will work on over the next couple of months. Kernel
features due for release in the next month are HDMI support, and
keyboard/mouse support.
We are also planning to provide a branch in the kernel tree that will be
based on the Android 4.9 common kernel. This won’t be upstream based, but
will be more feature complete than our mainline branch. This will be used
to support AOSP running on the Poplar board.
As we push topics and changes to the GitHub repositories, we will post a
message to the forums to update people here. I will provide another update
on our overall progress and plans in early June.
Scott Bambrough
Technical Director, Linaro Services Group
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA9NQX2unA6rs5cuWdaZ5_FYikgcmMgtks5r32-VgaJpZM4KYGh_>
.
|
|
Matt, he said "will be", not "has been". (which I see you've edited in the meantime) |
|
I would guess the source will eventually pop here with a manifest ;) Can't wait for the next update. The u-boot commit can be found here: https://www.mail-archive.com/u-boot@lists.denx.de/msg247981.html |
|
Hi Matt,
The guys will post links to the GitHub repos and a bugzilla instance once
they have be created.
Scott
…On 9 May 2017 at 14:26, Matt Gorski ***@***.***> wrote:
I would guess the source will eventually pop here with a manifest ;) Can't
wait for the next update.
The u-boot commit can be found here: https://www.mail-archive.com/
***@***.***/msg247981.html
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAo8d-rc29xPRU_hapPZ-VAgfnX6DIgAks5r4K_GgaJpZM4KYGh_>
.
--
Scott Bambrough
Technical Director, Member Services
Linaro <http://www.linaro.org>
|
|
Hello all, The initial source code drop for the Poplar board is now available on GitHub.com/Linaro. This drop includes source for ARM Trusted Firmware, U-Boot, and a 4.11 based upstream kernel along with documentation on how to build the software and tools to flash it to the Poplar board. This release of source code, tools and documentation provides:
To start, please review the README for pointers to the instructions for downloading. ( https://github.com/Linaro/poplar-tools/blob/latest/README ). This public drop is the first of many and the team plans on providing updates as we receive feedback and functionality becomes available. For follow-on drop announcements, questions or to provide feedback, see the 96Boards Poplar forum. Bugs can also be submitted at the soon to be available bugs.96boards.org (Product: Poplar). Thanks; Glen Valante |
|
Has anyone tried this yet? On my board there is neither a scriptaddr environment variable defined nor is there a source command available to run the install.scr script... |
|
can you make it to the u-boot shell? |
|
Yes, I can make it to the first |
|
@afaerber does your uboot shell gives you a #poplar prompt or are you booting in the old #fastboot? I suspect you might not be booting into the new uboot. Could you confirm that you are following this README please ? https://github.com/ldts/poplar-u-boot/blob/upstream/board/hisilicon/poplar/README |
|
Confirming that by inserting the missing For anyone lazy, I've packaged my bootloader binaries here: https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:Poplar In order to use an openSUSE .tbz rootfs instead of Debian .tar.gz I had to patch the shell script, and I also noticed a bug in the cleanup patch that I'll send a pull for. |
|
yep that contains more detail; I was just concerned that you might not be using the new uboot since scriptaddr is already set to 0x32000000. |
|
The newly built and flashed U-Boot has a The original Poplar U-Boot, from which I and others here need to install the new U-Boot, has I.e., the documented installation steps and the generated |
|
yes to upgrade from the original poplar u-boot the easiest way is to write the new one in a USB stick and boot from it (I tried to document that in the u-boot README). Also you should get this change below: It carves the memory needed by ATF (PSCI). I'll submit it in v5. |
|
With Jorge's help we've figured out that the documentation misses to mention that one should press the USB_BOOT button (S3) on power up, so that it uses the new instead of the old U-Boot. |
|
Hello; Thanks, |
|
@gvalante I pinged Robert in IRC about it as well. |
|
@sdrobertw Given Glen's announcement and the fixed poplar-tools build instructions, I think you can close this issue now. |
|
Thanks, @afaerber I will close the issue now. |
Could someone here please let me know where to find the kernel source and if possible the vendor binaries and device tree for the new TV platform 96 board linaro hisilicon poplar? Thank you in advance. I'm excited to get my current Android TV builds ported to the poplar.
The text was updated successfully, but these errors were encountered: