-
I am building an application that has been in development for various versions of Zephyr for over a year. This latest versions is identified by the following banner, while is compiles for the Native-POSIX target, crashes and burns badly during I generally follow the described install procedure which utilizes the python based 'west' to install Zephyr proper. Assuming I wanted to effectively do a rollback to a version which did not crash and burn in Native-POSIX, what is the recommended procedure? Is it as simple as making a legacy branch checked out in GIT, and performing a manual copy over the existing /zephyrproject/zephyr folder, or would that mix legacy rollback and later release components resulting in indeterminate behaviors? What is the recommended procedure to do a complete rollback to say a Dec 2022 release? -- Zephyr version: 3.2.99 (/zephyrproject/zephyr), build: zephyr-v3.2.0-3473-g9d2fe69b4efc |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Make sure to run If v3.2 works, try bisecting it to find which commit is causing the crash you are seeing. |
Beta Was this translation helpful? Give feedback.
Make sure to run
west update
after each checkout. This command updates/rollbacks Zephyr Modules at the time of the commit.If v3.2 works, try bisecting it to find which commit is causing the crash you are seeing.