96boards / documentation

This repository hosts the documentation for 96Boards products and specifications.
https://www.96boards.org/documentation/
Other
465 stars 286 forks source link

hisilicon poplar kernel source #39

Closed mattgorski closed 7 years ago

mattgorski commented 8 years ago

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.

sbambrough commented 7 years ago

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 Technical Director, Linaro Services Group

mattgorski commented 7 years ago

This is FANTASTIC news! So where will the GitHub source be located?

On May 8, 2017 3:40 PM, "Scott Bambrough" notifications@github.com 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 https://github.com/96boards/documentation/issues/39#issuecomment-299969202, or mute the thread https://github.com/notifications/unsubscribe-auth/AA9NQX2unA6rs5cuWdaZ5_FYikgcmMgtks5r32-VgaJpZM4KYGh_ .

afaerber commented 7 years ago

Matt, he said "will be", not "has been". (which I see you've edited in the meantime)

mattgorski commented 7 years ago

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

sbambrough commented 7 years ago

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 notifications@github.com 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/ u-boot@lists.denx.de/msg247981.html

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/96boards/documentation/issues/39#issuecomment-300258705, 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

gvalante commented 7 years ago

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 Program Manager, Linaro Services Group

afaerber commented 7 years ago

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...

ldts commented 7 years ago

can you make it to the u-boot shell?

afaerber commented 7 years ago

Yes, I can make it to the first mmc write command in the install.scr script by using 0x01000000 in place of ${scriptaddr} and manually copying commands. It seems to expect the device number (0) instead of the address.

ldts commented 7 years ago

@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

afaerber commented 7 years ago

Confirming that by inserting the missing 0 flashing worked, and it boots, too.

For anyone lazy, I've packaged my bootloader binaries here: https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:Poplar U-Boot is openSUSE's v2017.05 plus the v4 Poplar patchset.

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.

afaerber commented 7 years ago

@ldts I was following https://github.com/Linaro/poplar-tools/blob/latest/build_instructions.md which is linked to from https://github.com/96boards/documentation/blob/master/EnterpriseEdition/Poplar/BuildSource/README.md!

ldts commented 7 years ago

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.

afaerber commented 7 years ago

The newly built and flashed U-Boot has a poplar# prompt, scriptaddr=0x32000000, a source command and an mmc write command with only three parameters: mmc write addr blk# cnt

The original Poplar U-Boot, from which I and others here need to install the new U-Boot, has fastboot#, no scriptaddr variable, no source command, and an mmc write command with four parameters: mmc write <device num> addr blk# cnt

I.e., the documented installation steps and the generated install.scr might work on the new U-Boot, but they are unsuited for users updating from the originally shipping U-Boot.

ldts commented 7 years ago

@afaerber

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: https://github.com/ldts/poplar-u-boot/blob/upstream/board/hisilicon/poplar/poplar.c#L57

It carves the memory needed by ATF (PSCI).

I'll submit it in v5.

afaerber commented 7 years ago

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.

gvalante commented 7 years ago

Hello; I was trying the same thing and knew about the button, but didn't see it in the directions. Fixing it now.

Thanks,

ldts commented 7 years ago

@gvalante I pinged Robert in IRC about it as well.

afaerber commented 7 years ago

@sdrobertw Given Glen's announcement and the fixed poplar-tools build instructions, I think you can close this issue now.

fixxxxxxer commented 7 years ago

Thanks, @afaerber

I will close the issue now.