Willmish / bibop-zephyr-eos-s3

Zephyr port of BiBoP on a eos s3 SoC, for EOSS
Apache License 2.0
2 stars 1 forks source link

PRs needed for full EOS S3/Quickfeather support on Zephyr and others we can pick up #12

Open Willmish opened 1 year ago

Willmish commented 1 year ago

For Interrupts to work on Zephyr with EOS S3 (and so that SPI can work?): https://github.com/zephyrproject-rtos/zephyr/pull/28291

For OpenOCD flashing support to work on Zephyr: https://review.openocd.org/c/openocd/+/6956 https://github.com/Willmish/openocd/tree/eoss3_flash_patch

Incomplete support for quickfeather_Hal module for zephyr: https://github.com/zephyrproject-rtos/hal_quicklogic Antmicro's repo with seemingly some additional not moved over support (i2c, spi, etc): https://github.com/antmicro/eos-s3-hal

For YoSys (synthesis of FPGA images support for QuickLogic devices): https://github.com/YosysHQ/yosys/pull/1816

JDuchniewicz commented 1 year ago

How is I2C handled? is it a hardware setup? code in FPGA? (probably hardware regisers etc). How can we access Wishbone and I2C

Willmish commented 1 year ago

NEXT THING: In the quickfeather dts, Button0, blue green and red gpios are defined, but their pinmuxes are not set up in board.c (https://github.com/zephyrproject-rtos/zephyr/blob/533c1985dc18177d8986fea86f00d39c132cda5e/boards/arm/quick_feather/board.c#L15) only uart is.

See:

Willmish commented 1 year ago

Turns out the pinmux was already set in bootloader, since removing gpio_pin_configure and the pinmux still meant the button was read fine, at least we learned:

JDuchniewicz commented 1 year ago

NEXT THING: In the quickfeather dts, Button0, blue green and red gpios are defined, but their pinmuxes are not set up in board.c

As discussed earlier today, we plan to put full support for all peripherals for this board so that M4 app (Zephyr) can be run directly without the bootloader, hence:

JDuchniewicz commented 1 year ago

Might be useful here https://www.zephyrproject.org/how-to-set-up-esp32-gpio-pins-in-zephyr-rtos/