Skip to content

Conversation

@pmoussay-emdalo
Copy link

Add initial support for the Microchip PIC64GX Curiosity Kit development Board.
This work adds initial support for 'pic64gx_curiosity_kit' which has a five core micro-
processor subsystem with:
SiFive E51 Monitor core (1 x RV64IMAC)
SiFive U54 Application cores (4 x RV64GC)

Product page: https://www.microchip.com/en-us/development-tool/curiosity-pic64gx1000-kit

Add minimal support for PIC64GX SoC and devicetree

Signed-off-by: Pierre-Henry Moussay <[email protected]>
Add minimal support for PIC64GX curiosity kit

Signed-off-by: Pierre-Henry Moussay <[email protected]>
Add pic64 SoC and pic64gx_curiosity_kit to Microchip RISCV board and SoC

Signed-off-by: Pierre-Henry Moussay <[email protected]>
@github-actions
Copy link

Hello @pmoussay-emdalo, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

@sonarqubecloud
Copy link

- fkokosinski
- kgugala
- tgorochowik
- con-pax
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

way too many maintainers here, are all of those active? @fkokosinski @kgugala @tgorochowik are you still actively maintaining this platform?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, we're still maintaining Microchip RISC-V platforms. @pmoussay-emdalo - feel free to remove relegate @tgorochowik and @kgugala to collaborators

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to give a confirmation, we discussed this offline and we're okay with moving us

Copy link
Member

@fkokosinski fkokosinski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Convert this photo to webp and compress it using e.g. https://tinypng.com/

@@ -0,0 +1,38 @@
# SPDX-License-Identifier: GPL-2.0-or-later
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


if BOARD_PIC64GX_CURIOSITY_KIT

endif
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this file needed?

CONFIG_FPU=n
# GPIO driver options
CONFIG_GPIO=y
CONFIG_I2C=y
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be selected by samples/tests/application that actually use I2C

CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000
# GPIO driver options
CONFIG_GPIO=y
CONFIG_I2C=y
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000
# GPIO driver options
CONFIG_GPIO=y
CONFIG_I2C=y
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000
# GPIO driver options
CONFIG_GPIO=y
CONFIG_I2C=y
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

- fkokosinski
- kgugala
- tgorochowik
- con-pax
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, we're still maintaining Microchip RISC-V platforms. @pmoussay-emdalo - feel free to remove relegate @tgorochowik and @kgugala to collaborators

payload-name: "zephyr"
}
Please refer to the following README.md for more information on playload generation:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s'/playload/payload/'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants