dce070ebe0
When BOARD=fomu, use the riscv cross-compiler. Otherwise, use the
default arm compiler. This can be overridden by passing
CROSS_COMIPLE on the command line.
Note that there are now three common risc-v prefixes:
- riscv32-unknown-elf- : Common for users who compile their own
- riscv64-unknown-elf- : Upstream multiarch toolchain from SiFive
- riscv-none-embed- : xPack embedded version of SiFive toolchain
Here we assume users are using the `riscv-none-embed-` toolchain from
xPack, because it appears to be growing more common. Additionally,
there is much confusion surrounding `riscv64-unknown-elf-`, which
actually includes both 32- and 64-bit runtimes and can generate software
for both.
Signed-off-by: Sean Cross <sean@xobs.io>
Examples
Clone this repo
$ git clone https://github.com/hathach/tinyusb tinyusb
$ cd tinyusb
Fetch submodule MCUs drivers
TinyUSB examples includes external repos aka submodules to provide low-level MCU peripheral's driver to compile with. Therefore we will firstly fetch those mcu driver repo by running this command in the top folder repo
$ git submodule update --init --rescursive
It will takes a bit of time due to the number of supported MCUs, luckily we only need to do this once.
Build
Here is the list of supported Boards that should work out of the box with provided examples.
To build example, go to its folder project then type make BOARD=[our_board] all e.g
$ cd examples/device/cdc_msc_hid
$ make BOARD=feather_nrf52840_express all
Flash
flash target will use the on-board debugger (jlink/cmsisdap/stlink/dfu) to flash the binary. We should install those debugger/programmer software in advance. Futhermore, since external jlink can be used with most of the board, there is also flash-jlink target for out convenience.
$ make BOARD=feather_nrf52840_express flash
$ make BOARD=feather_nrf52840_express flash-jlink
Some board use uf2 bootloader for drag & drop in to mass storage device, uf2 can be generated with uf2 target
$ make BOARD=feather_nrf52840_express all uf2