Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Add posix support (Linux/NuttX) #171

Open
wants to merge 15 commits into
base: main
Choose a base branch
from

Conversation

microhobby
Copy link

Description

Let's try to upstream the posix POC

Targets affected

  • MBN_QUAIL
  • GHI_FEZ_CERB40_NF
  • I2M_ELECTRON_NF
  • I2M_OXYGEN_NF
  • WEACT_F411CE
  • ST_NUCLEO64_F401RE_NF
  • ST_NUCLEO64_F411RE_NF
  • ST_STM32F411_DISCOVERY
  • ST_NUCLEO144_F412ZG_NF
  • ST_NUCLEO144_F746ZG
  • ST_STM32F4_DISCOVERY
  • ST_NUCLEO144_F439ZI
  • TI_CC1352P1_LAUNCHXL_868
  • TI_CC1352P1_LAUNCHXL_915
  • ESP32_OLIMEX
  • PybStick2x
  • BUILD ALL

Motivation and Context

  • Fixes/Closes/Resolves nanoFramework/Home#NNNN

How Has This Been Tested?

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Config and build (change in the configuration and build system, has no impact on code or features)
  • Dependencies (update dependencies and changes associated, has no impact on code or features)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Signed-off-by: Matheus Castello <[email protected]>
Signed-off-by: Matheus Castello <[email protected]>
nanoFramework expects a tick as 100 nanoseconds

Signed-off-by: Matheus Castello <[email protected]>
In Nuttx if no argument is passed we infer that the default sdcard path
will be used.

Signed-off-by: Matheus Castello <[email protected]>
I do not know if this is a good idea, but this will make the releases
more easy, so I can publish a single binary for x86-64 arch. The side
effect will be a seg fault if the managed code is using
System.Device.Gpio.

Signed-off-by: Matheus Castello <[email protected]>
Tested on Beagle-V beta with success

Signed-off-by: Matheus Castello <[email protected]>
With the __gpio not defined the weak reference will be used

Signed-off-by: Matheus Castello <[email protected]>
This fix a undefined behavior when using NuttX with esp32-c3

Signed-off-by: Matheus Castello <[email protected]>
It's not needed to be static

Signed-off-by: Matheus Castello <[email protected]>
Yeah, unfortunately Beagle-V project was canceled so let's reuse the
work here for the StarFive JH7100 platform.

Signed-off-by: Matheus Castello <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants