* Added some function wrappers to EmbeddedExecutable that expose commonly used functionalities of LibExeObjStep
* atsame51j20a chip added. GPIO support. UART support over SERCOM5.
* added support for true random numbers to atsame51j20a chip
* Add comment about microzig.config
When writing a HAL, having the chip name is very important to switch features and select pinout. Mention the config in the README in a concise manner.
Co-authored-by: Felix Queißner <felix@ib-queissner.de>
* i2c: pass a config to init
For now, allow setting the i2c target speed
* i2c: allow selecting the scl/sda pins
Similar to the previous commit for uart, this allows specifying the pins for
microcontrollers that support multiple pins for a single i2c peripheral
* stm32f407: add support for i2c
Supports using all I2C peripherals with all their pins in standard mode (fast
mode support will be added in the future).
board: and chip: can be prefixed to the pin to force using a pin defined in the
board or in the chip. Currently though, neither chips or boards are handling
this prefix.
Since this is just used to give priority when parsing the pin, this commit
removes the namespace from the spec passed to parsePin. This isolates the
namespace handling to the Pin type creation, without having to handle it in
chips and boards.
While this does not automate clock configuration yet, at least it allows using
microzig with applications that configure the clock themselves and then declare
the speeds of the various domains.
Without this, all peripheral depending on different clock domanins (e.g. Uart or
I2C on STM32 devices) could only work with the reset frequency.
* stm32f407: add Uart support
* lpc1768: add cpu_frequency in board and chip
Allow using them with microzig Uart, which ensures the clock is present
* lpc1768: fix UART2 and UART3 peripheral clock register
They are in the PCLKSEL1 register, not PCLKSEL0
* uart-sync: use native microzig Uart, target different boards/chips
The previous example was lpc1768 specific, this new example should work with all
board and chips which implement the microzig Uart functionality. Instead of 4
LEDs, the new example uses a single LED to provide minimal debugging
capabilities if something does not work correctly.
This allows building this example for the stm32 f3 and f4 discovery boards.
* Add stm32f429 registers
Generated using regz with:
./regz STM32F429.svd > registers.zig
Using this SVD:
871761af63/data/STMicro/STM32F429.svd
* Add initial support for the stm32f429idiscovery eval board
Blinky example working on the board
* Makes AVR UART work.
* Some comment. This is definitly not padding.
* Exports panic, log and log_level from application.
* Implements generic quadrature decoder driver.
* Fixes `@export` bug in AVR interrupt logic. Now we get distinct interrupt vectors.
Co-authored-by: Felix "xq" Queißner <git@masterq32.de>
* Add stm32f407 registers
Generated using regz with:
./regz STM32F407.svd > registers.zig
Using this SVD:
871761af63/data/STMicro/STM32F407.svd
* Add initial support for the stm32f4discovery eval board
The blinky example is working on the board
* build.zig: Trivial rename around UART test
* mmio: Add writeRaw() to set a full register
* UART: Add TODO for auto baud rate detection
* STM32F30x Initial USART1 output/transmit support
All code assumes default chip clock configuration.
Code assumes STM32F303xB / STM32F3030xC.
Code supports only 8 data bits, 1 stop bit.
* stm32f3discovery @panic() to UART1
This is done by implementing `debugWrite()` for the board,
which only initializes UART1 if that was not yet done,
and flushes afterwards to make sure the host receives all.
* stm32f303: Support UART1 reader
This is done by implementing `rx()` and `canRead()`.
* stm32f303 UART1 correctly support 7 and 8 bits
This includes correctly masking the parity bit
on reads.
* stm32f3 UART1 support 0.5/1.5/2 stop bits
* stm32f303 UART1 simplify parity code
* stm32f303 I2C rough initial code
Allows only writing and reading single bytes.
* stm32f3 i2c: enable debug 'logging'
* Add a few comments
* I2C API changes, STM32F303 I2C multi-byte transfers
Now using controller/device terminology, instead of master/slave.
Now using 'transfer objects' to make STOPs and re-STARTs explicit,
and allow using Writer and Reader APIs.
Added 'register' abstraction.
STM32F303 I2C now supports this new API, and multi-byte transfers.
Now waiting for I2C_ISR.BUSY == 0, after setting I2C_CR2.STOP == 1.
Without this, the sequence write-stop-write caused an additional STOP
to be sent immediately the START and address of the second write.
* Make work with regz-generated registers.zig change
* Updated to match regz-generated update
* After #23 repair Reset on stm32, lpc1768
* Clean-up I2C `readRegisters()`.
* Refactor to separate read/write states
* On STM32F303, make second read call fail
Also doc comments to clarify the new API.
* STM32 I2C: Properly support multiple write calls
* I2C STM32: Fix release mode compile error
...on top of an earlier commit on this branch.
* I2C Add 'write register' shorthand functions
Felix Queißner
Philipp Wendel
hollmmax
Matt Knight
David Sugar
Nicolas Goy
Vesim
Matheus C. França
Marnix Klooster
Ethan Frei
Riccardo Binetti