You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After editing partition_nvs.csv it will also connect to the wifi. I can also use the M5Burner to edit the wifi information. In both cases the Core will connect to wifi, but not to the cloud.
Via M5Burner I managed to "register" the device to my account, however when I keep the custom firmware it appears in https://uiflow2.m5stack.com/ as an unknown device (and thus cannot use it).
All the other attemps have failed to connect to the cloud (always appears are Private, never Public).
If I reflash the original firmware (without utf8) everything works as expected.
Hi,
Sorry for the confusion, the firmware that can connect to uiflow2 via the network is currently only distributed through M5Burner, which means that the firmware you compile through this code repository only supports USB mode.
We are not hiding anything intentionally, but there are some security issues that have not been resolved, and we are working hard to resolve them. Before that sorry for this moment.
Hello,
I created a custom UIFlow2 firmare version (to add UTF8 font, see #25 ).
I can flash it via 'make flash_all', and load programs from https://uiflow2.m5stack.com/ via USB.
After editing partition_nvs.csv it will also connect to the wifi. I can also use the M5Burner to edit the wifi information. In both cases the Core will connect to wifi, but not to the cloud.
Via M5Burner I managed to "register" the device to my account, however when I keep the custom firmware it appears in https://uiflow2.m5stack.com/ as an unknown device (and thus cannot use it).
All the other attemps have failed to connect to the cloud (always appears are Private, never Public).
If I reflash the original firmware (without utf8) everything works as expected.
How can I have my custom firmware interact with https://uiflow2.m5stack.com/ via wifi too?
(see also https://community.m5stack.com/topic/6734/custom-uiflow2-firmware-how-to-connect-to-https-uiflow2-m5stack-com-private-vs-public )
The text was updated successfully, but these errors were encountered: