No Description

liqiangguo 090d577fa2 CSKY: fix (libacpi、efivar、efibootmgr、dmidecode、acpica、systemd) compile error 2 years ago
.github 36fa20770f first commit 3 years ago
conf 090d577fa2 CSKY: fix (libacpi、efivar、efibootmgr、dmidecode、acpica、systemd) compile error 2 years ago
docs 36fa20770f first commit 3 years ago
recipes-bsp 69e5971ef7 CSKY: supports compiling u-boot and kernel 2 years ago
recipes-core 8bcfa91f0c delete files useless for csky 3 years ago
recipes-devtools 47fb319ed3 update sources.list for csky 2 years ago
recipes-graphics b52353f76a fix mesa complie error 3 years ago
recipes-kernel 69e5971ef7 CSKY: supports compiling u-boot and kernel 2 years ago
recipes-support ede9330ae7 append patch file for icu、libffi、libgpg-error 2 years ago
tools 36fa20770f first commit 3 years ago
wic 36fa20770f first commit 3 years ago
.travis.yml 36fa20770f first commit 3 years ago
CONTRIBUTORS 36fa20770f first commit 3 years ago
LICENSE 36fa20770f first commit 3 years ago
README.md 36fa20770f first commit 3 years ago
setup.sh 4a145eecda fix csky compilation error 3 years ago

README.md

meta-csky

CSKY Architecture Layer for OpenEmbedded/Yocto

license Build Status

Description

This is the general hardware-specific BSP overlay for the CSKY based devices.

More information can be found at: https://csky.org/ (Official Site)

The core BSP part of meta-csky should work with different OpenEmbedded/Yocto distributions and layer stacks, such as:

  • Distro-less (only with OE-Core).
  • Yoe Distro.
  • Yocto/Poky.

Dependencies

This layer depends on:

  • URI: git://github.com/openembedded/openembedded-core
    • branch: master
    • revision: HEAD
  • URI: git://github.com/openembedded/bitbake
    • branch: master
    • revision: HEAD

Quick Start

Note: You only need this if you do not have an existing Yocto Project build environment.

Make sure to install the repo command by Google first.

Create workspace

mkdir csky-yocto && cd csky-yocto
repo init -u git://github.com/csky/meta-csky  -b master -m tools/manifests/csky-yocto.xml
repo sync
repo start work --all

Update existing workspace

In order to bring all the layers up to date with upstream

cd csky-yocto
repo sync
repo rebase

Setup Build Environment

. ./meta-csky/setup.sh

Available Machines

The three different machines you can build for are:

  • qemucsky: The 32-bit CSKY machine
  • freedom-u540: The SiFive HiFive Unleashed board

Build Images

A console-only image for the 64-bit QEMU machine

MACHINE=qemucsky bitbake core-image-full-cmdline

To build an image to run on the HiFive Unleashed using Wayland run the following

MACHINE=freedom-u540 bitbake core-image-weston

To build a full GUI equipped image running Plasma Mobile see the in-tree documentation here.

Running in QEMU

Run the 32-bit machine in QEMU using the following command:

MACHINE=qemucsky runqemu nographic

Running on hardware

Setting up a TFTP server

If you would like to boot the images from a TFTP server (optional) you should set your TFTP server address in your local.conf with the following line. Change 127.0.0.1 to the IP address of your TFTP server and copy the uImage to the server.

TFTP_SERVER_IP = "127.0.0.1"

Running with the Microsemi Expansion board

To use the Microsemi expansion board with your HiFive Unleased add the following line to your local.conf. This tells the Unleashed to use a device tree with the PCIe device described:

Sparse Image Creation

The output of the build can also be written to an SD card using bmaptool, the steps to do this are below:

$ MACHINE=freedom-u540 wic create freedom-u540-opensbi -e core-image-minimal
$ bmaptool create ./freedom-u540-opensbi-201812181337-mmcblk.direct > image.bmap
$ sudo bmaptool copy --bmap image.bmap ./freedom-u540-opensbi-201812181337-mmcblk.direct /dev/sdX

dding wic.gz

The output of a freedom-u540 build will be a <image>.wic.gz file. You can write this file to an sd card using:

$ zcat <image>-<machine>.wic.gz | sudo dd of=/dev/sdX bs=4M iflag=fullblock oflag=direct conv=fsync status=progress

Maintainer(s)

  • Khem Raj <raj dot khem at gmail.com>