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

Porting guide for advanced board (multi CPU SoC) #13170

Closed
r8d8 opened this issue Feb 8, 2019 · 3 comments
Closed

Porting guide for advanced board (multi CPU SoC) #13170

r8d8 opened this issue Feb 8, 2019 · 3 comments
Labels
Enhancement Changes/Updates/Additions to existing features

Comments

@r8d8
Copy link

r8d8 commented Feb 8, 2019

Is your enhancement proposal related to a problem? Please describe.
Started to work with new triplemode SoC(BLE 5.0, WiFi, 802.15.4) board from Qualcomm using QCA4020 board
It utilizes 3 CPUs: Cortex-M4(application), Cortex-M0(BLE, 802.15.4), Xtensa7 (WiFi).
Have read "Porting" doc multiple time, but still strugling to port zephyr fro this board. The ain issue for me is deeply nested file structure (Device Tree files) and Kconfig.

Describe the solution you'd like
Would be nice to have some tutorial for advanced board (like mine with couple of CPU), that guides user step-by-step through all process of porting

@r8d8 r8d8 added the Enhancement Changes/Updates/Additions to existing features label Feb 8, 2019
@henrikbrixandersen
Copy link
Member

CC: @mbolivar-nordic

@mbolivar-nordic
Copy link
Contributor

Yeah, this fits into #51833 I think. We would need to solve this problem for documenting the combination of #51830 and #51831. @r8d8 in short your use case is known and especially since you have different arches, you'll need multiple board directories with different DTS files inside. We don't have a great solution right now.

I'm going to close this issue since the other issues I've linked should address your use case, as documentation for the new enhancements is assumed. Please feel free to comment in those issues if there are requirements you're missing. And please reopen if there's something I missed.

@mbolivar-nordic
Copy link
Contributor

Sorry, I am not sure why github assumed 'completed' was the status. I meant to close as 'duplicate'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Development

No branches or pull requests

3 participants