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

Yocto Support? #2

Open
swanav opened this issue Jun 27, 2020 · 5 comments
Open

Yocto Support? #2

swanav opened this issue Jun 27, 2020 · 5 comments

Comments

@swanav
Copy link

swanav commented Jun 27, 2020

Support for Yocto-Linux based devices would be very useful and would suit my requirement for a WiFi/BT Combo for a custom board.

@MangeshMalusare
Copy link
Contributor

Thanks for your feedback. There is no plan to support Yocto linux in near future. We will keep it in consideration though.

Thanks

@myfreescalewebpage
Copy link

@swanav I think you should just write a simple recipe in your layer to get the sources and build the module. Pretty simple when doing yocto stuff, no more than few lines are required :-)

@Oquirella
Copy link

This would indeed be very nice

@mantriyogesh
Copy link
Collaborator

mantriyogesh commented Jul 13, 2022

Hello @Oquirella,

Many of the customers have ported the solution with Yocto.
Worth to check issues to understand how the porting happened:
#101
#128

Also, PR: #130 for Beaglbone Black (BBB)

In general, Yocto boards have to

  1. Configure device tree so that the expected device is correctly set-up.
  2. If any user space application can be used to test that the device driver provided by Linux is working correctly.
  3. Additional pins to be configured for ESP-Hosted solution as mentioned in porting guide
  4. For only SDIO transport, Additional Pull-ups to be added, If required any, as per https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/sd_pullup_requirements.html
  5. Hardware and software setup as per Hosted documentation and porting guide.

The problem with Yocto is that no specific configuration works for all the SoCs. Why? Because, the peripherals and their Pin Controls differ. Device Trees differ across the SoCs. No single Yocto config will work for any other SoCs as is.

Be it Yocto or Non-Yocto, the procedure for porting remains the same.
The porting should be given some efforts as mentioned in the Porting Guide and you should definitely get the ESP-Hosted working with the least efforts.

If you are stuck at any place while porting, just raise an issue. We will certainly help you out.

@mantriyogesh
Copy link
Collaborator

A Yocto bitbake recipe from end user could be found in #137

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants