[Buildroot] [PATCH 2/2] board/sifive: add support for the HiFive Unleashed board

Arnout Vandecappelle arnout at mind.be
Mon Apr 15 14:27:44 UTC 2019



On 15/04/2019 15:04, Mark Corbin wrote:
>>> +Connect the USB cable and open minicom (/dev/ttyUSB1, 115200, 8N1).
>>  How do you know it is ttyUSB1? It is usually USB0...
> There are two USB serial devices on the board - the console always seems
> to be on USB1 on my board. I can be more cautious and say '/dev/ttyUSBx'
> instead.

 Ah, now I see... So the single USB cable provides two serial ports, and USB1 is
the one you need? Then it's indeed better to specify USB1 in the README. But
maybe also explain that there are two ports.

>>> +
>>> +See the 'SiFive HiFive Unleashed Getting Started Guide' for
>>> +more details (https://www.sifive.com/documentation).
>>> +
>>> +--
>>> +
>>> +Mark Corbin <mark.corbin at embecosm.com> April 2019
>>> diff --git a/configs/sifive_u540_unleashed_defconfig b/configs/sifive_u540_unleashed_defconfig
>>> new file mode 100644
>>> index 0000000000..b56ae1b164
>>> --- /dev/null
>>> +++ b/configs/sifive_u540_unleashed_defconfig
>>> @@ -0,0 +1,29 @@
>>> +# Architecture
>>> +BR2_riscv=y
>>> +BR2_RISCV_64=y
>>> +
>>> +# Patches
>>> +BR2_GLOBAL_PATCH_DIR="board/sifive/patches"
>>> +
>>> +# Linux headers same as kernel, a 4.20 series
>>> +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_20=y
>>> +
>>> +# System
>>> +BR2_ROOTFS_POST_IMAGE_SCRIPT="board/sifive/u540-unleashed/post-image.sh"
>>> +
>>> +# Kernel
>>> +BR2_LINUX_KERNEL=y
>>> +BR2_LINUX_KERNEL_CUSTOM_VERSION=y
>>> +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.20.17"
>>  Oh, now I see, you're porting the changes done by sifive from 4.19 to 4.20...
>> Is that also what the freedom-u-sdk does? I don't think so...
> I'm not sure that the freedom-u-sdk has moved to 4.19 yet (the v1_0
> release uses 4.15), but there is a patched 4.19 kernel tree available in
> the master branch. I've generated a patch for 4.20.17 based on this
> patched 4.19 tree. I wanted to move to the most recent version of the
> 4.20 kernel that Buildroot supported, but I guess that I could also just
> look at using the patched 4.19 branch that already exists.

 If a board is far away from being supported by upstream, we usually stick to an
"offical" fork from the board vendor.


 Regards,
 Arnout


More information about the buildroot mailing list