While I was getting my bearings to make the modifications for #212, I ran into a number of snags during setup that I hope I can help smooth out for future folk. Half of these are for CANnectivity, and half are for Zephyr itself.
- The link to the "Zephyr Getting Started Guide" is broken. (And for some reason shows the referring URL as the incorrect URL?)
- It's not made super clear that the Zephyr SDK is also required, as the titles read "Get Zephyr" and then "Install the Zephyr SDK." Minor wording choice but it did confuse me when after I did
west init and west update, and the section ended, that I was unable to build still. Mostly a nitpick, ngl.
- I don't fully understand the
my-workspace name suggestion, but it's mostly a product of me also not fully grasping if one is intended to have only One True Zephyr install per system, since it shoves it right into my home directory (which I try to keep to clean of per-project dependencies like that). It also caught me off guard since there's a preceeding cd into ~/zephyrproject/zephyr in the Getting Started guide, but it seems to be A. not needed since it finds the zephyr/ directory anyway, and B. impotent since again, it just installed it into my home dir.
- It might be worth mentioning to use
west sdk install --install-base zephyr/ -t arm-zephyr-eabi, to avoid the above concern of shoving Zephyr into your home directory, as well as installing every single other toolchain, including all of the Xtensa ones! (Especially since I don't think there's ESP or similar support for CANnectivity.)
Regardless, cheers for the cool project and work on maintaining the gs_usb protocol! I don't know if I'll end up contributing something more substantial, but I may in the future!
While I was getting my bearings to make the modifications for #212, I ran into a number of snags during setup that I hope I can help smooth out for future folk. Half of these are for CANnectivity, and half are for Zephyr itself.
west initandwest update, and the section ended, that I was unable to build still. Mostly a nitpick, ngl.my-workspacename suggestion, but it's mostly a product of me also not fully grasping if one is intended to have only One True Zephyr install per system, since it shoves it right into my home directory (which I try to keep to clean of per-project dependencies like that). It also caught me off guard since there's a preceedingcdinto~/zephyrproject/zephyrin the Getting Started guide, but it seems to be A. not needed since it finds thezephyr/directory anyway, and B. impotent since again, it just installed it into my home dir.west sdk install --install-base zephyr/ -t arm-zephyr-eabi, to avoid the above concern of shoving Zephyr into your home directory, as well as installing every single other toolchain, including all of the Xtensa ones! (Especially since I don't think there's ESP or similar support for CANnectivity.)Regardless, cheers for the cool project and work on maintaining the gs_usb protocol! I don't know if I'll end up contributing something more substantial, but I may in the future!