General and Questioning the Very Fabric of Development/Zephyr

General Discussion
, ,
1

Building Zephyr of your Own Clone via git

1. hey@you: git clone https://github.com/some_dude/zephyr.git
2. hey@you: mkdir Flagrant && mv zephyr/ Flagrant/
3. Building the files needed...
a. hey@you: python3 -m venv ~/zephyrproject/.venv
b. hey@you: source ~/zephyrproject/.venv/bin/activate
c. hey@you: cd Flagrant/zephyr/ && pip install west
d. hey@you: west update
e. hey@you: west zephyr-export
f. hey@you: west packages pip --install
4. now, it boils down to porting the new board (beagley-ai which is already ported and working)
5. the reason for making it a separate build is to not mess with what works

Just a heads up here. I have successfully built what someone else did to make it work. All fine and dandy on that front.

I am getting errors in zephyr for building on a board called the y-ai. It is a play on wording. It seems adding architecture is very difficult and adding GPIO within zephyr for the am67a onboard the beagley-ai is a little less complicated.

So, I am going to try to build the less complicated version to start. So far, I have renamed some files and added /zephyr/boards/y-ai/* where * are my files mislabeled.

Has anyone ported a board successfully in zephyr on their own git clone?

Seth

2

So, I am behind the times. Zephyr for the BeagleY-AI is already done supposedly but the r5f cores need attention in that they do not have header access from r5f to GPIO (I think.

If I am wrong, please do interrupt me.

So also, porting a board is not easy. So, I forked the repo and am harvesting ideas and reading up. Um, luckily there are some people willing to support the cause on beagleboard.org personnel and/or community members and then on the Zephyr side of things.

I got the forking-cloning-setting up of the zephyr done but it seems most people have beat me to the punch.

Seth

P.S. I will keep ticking until the end. So, until then, I will try to get some ideas and make subject matter of it.