--enable_burn_mode ENV Issue

[ivybowman]

I have identified that setting the auto burn mode env setting with this tool https://github.com/frederic/superbird-bulkcmd then trying to adb boot does work but(after restoring the env) trying to use --enable_burn_mode then adb boot does not work and I am wondering if it's changing a setting it does not need to.

[bishopdynamics]

I am getting the same results as you. Looks like my implementation of bl2_boot is not quite identical to the way the amlogic tool does it. I will investigate further, and hopefully have a fix soon.

[ivybowman]

Cool thanks! On Mon, Oct 31, 2022 at 3:04 PM Bishop @.***> wrote:

I am getting the same results as you. Looks like my implementation of bl2_boot is not quite identical to the way the amlogic tool does it. I will investigate further, and hopefully have a fix soon.

— Reply to this email directly, view it on GitHub https://github.com/bishopdynamics/superbird-tool/issues/2#issuecomment-1297539627, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEN4BBOWSQZTGU7IYPFBZATWGAJ3LANCNFSM6AAAAAARSYW5JE . You are receiving this because you authored the thread.Message ID: @.***>

-- Ivy Bowman she/they

[bishopdynamics]

Still sorting this out, but I just pushed an update that adds a bunch of options for reading/writing env, including an option to restore stock env. This will make it easier to troubleshoot.

[ivybowman]

Cool, I will check it out soon, I know my friend was able to use the flag without an issue so it could be just hit or miss honestly.

[bishopdynamics]

issue discovered in #4 and fixed