github
/
tinygo
mirror of https://github.com/tinygo-org/tinygo.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2241 Commits
99 Branches
41 Tags
26 MiB
Tree: 6234bf9a88
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6234bf9a88'
${ noResults }
tinygo/targets/itsybitsy-m4.json

11 lines
290 B
Raw Normal View History

machine/atsamd51: add support for ATSAMD51 processor using Adafruit ItsyBitsy-M4 board Signed-off-by: Ron Evans <ron@hybridgroup.com>
6 years ago
{
"inherits": ["atsamd51g19a"],
sam: remove redundant build tags Some build tags were duplicated. This commit removes them.
4 years ago
"build-tags": ["itsybitsy_m4"],
all: add a flag to the command line to select the serial implementation This can be very useful for some purposes: * It makes it possible to disable the UART in cases where it is not needed or needs to be disabled to conserve power. * It makes it possible to disable the serial output to reduce code size, which may be important for some chips. Sometimes, a few kB can be saved this way. * It makes it possible to override the default, for example you might want to use an actual UART to debug the USB-CDC implementation. It also lowers the dependency on having machine.Serial defined, which is often not defined when targeting a chip. Eventually, we might want to make it possible to write `-target=nrf52` or `-target=atmega328p` for example to target the chip itself with no board specific assumptions. The defaults don't change. I checked this by running `make smoketest` before and after and comparing the results.
3 years ago
"serial": "usb",
flash: support flashing boards using Mass Storage Device (MSD) operation for uf2 and daplink bootloaders Signed-off-by: Ron Evans <ron@hybridgroup.com>
5 years ago
"flash-1200-bps-reset": "true",
"flash-method": "msd",
main: detect specific serial port IDs based on USB vid/pid This makes it possible to flash a board even when there are multiple different kinds of boards attached, e.g. an Arduino Uno and a Circuit Playground Express. You can find the VID/PID pair in several ways: 1. By running `lsusb` before and after attaching the board and looking at the new USB device. 2. By grepping for `usb_PID` and `usb_VID` in the TinyGo source code. 3. By checking the Arduino IDE boards.txt from the vendor. Note that one board may have multiple VID/PID pairs: * The bootloader and main program may have a different PID, so far I've seen that the main program generally has the bootloader PID with 0x8000 added. * The software running on the board may have an erroneous PID, for example from a different board. I've seen this happen a few times. * A single board may have had some revisions which changed the PID. This is particularly true for the Arduino Uno. As a fallback, if the given VID/PID pair isn't found, the whole set of serial ports will be used. There are many boards which I haven't included yet simply because I couldn't test them.
3 years ago
"serial-port": ["acm:239a:802b", "acm:239a:002b"],
targets: refactor flash/gdb target configuration Instead of specifying explicit commands, most of these commands have been replaced by more specific properties. This is work that will be necessary for an eventual -programmer flag to the compiler, with which it is possible to select which programmer to use to flash or debug a chip. That's not very useful for boards that already include a programmer or bootloader for that purpose, but is very useful for novel boards or single-purpose boards that are not already included in TinyGo.
5 years ago
"msd-volume-name": "ITSYM4BOOT",
"msd-firmware-name": "firmware.uf2"
machine/atsamd51: add support for ATSAMD51 processor using Adafruit ItsyBitsy-M4 board Signed-off-by: Ron Evans <ron@hybridgroup.com>
6 years ago
}