I started out with my Core Fire using UIFLOW 2, but soon discovered that there were many software functions in Version 1 that were not supported in Version 2 (for example, programming the LED bars), so I switched to Version 1. I understand that Version 2 supports many more devices than Version 1, but if one is going to create a new version of critical software like UIFLOW, shouldn't one make sure that the new version supports all the functionality of the previous version, and then extends the functionality of the new version into new areas. Am I missing something here?

]]>https://community.m5stack.com/topic/7067/uiflow-version-1-compared-to-version-2RSS for NodeThu, 30 Apr 2026 18:57:45 GMTSun, 08 Dec 2024 18:20:17 GMT60@hillsh_vi The problem is that UIFlow2 was designed for the newer processors consisting primary of the S3 and C3 groups because of a fundamental change to the way Micropython operates on them including the boot loader.
You may have noticed that the older gen devices could be programmed without actually touching the cores where as the new gen have to be put into boot loader mode for firmware writing.

]]>https://community.m5stack.com/post/27380https://community.m5stack.com/post/27380Sun, 08 Dec 2024 19:58:47 GMT