help needed to get started.
has someone also problem by starting with their M5 stack dev board???
We have 1 of two issues here.
Issue one (most likely) you haven't put the Atom S3 into Boot mode and so M5Burner cant access the AtomS3's eprom
Issue two Windows built in security is blocking M5 Burner from writing to the EPROM.
I have a video for the CoreS3 going live on Saturday which shows how I flashed the CoreS3 using M5Burner (or at least I hope I didn't cut that bit) but the instructions still work for the Atom S3
I got the way around the problem of security but still the tmp file is empty so it cannot access the patch because there are no files there
I was able to run the m5 burner as admin ( right click on the icone m5).... so this must go through the windows issue although the file is empty.this still be an issue.
the zip file is not inside the folder.....
Why is it looking in the pictures folder?
M5Burner should be in the root user folder or the programs folder!
Because it put the downloaded zipfile in here and extracted here...
As it is not a msi installer but just an exe i had never a problem running an exe not from the program files folder. Also from the temp folder.
It is not playing a role sofar. This would be for me the first time.... if this is mandatory one must write a step by step standard procedure as idiot proof as possible...
Nevertheless i an sure trying to extract into the program file folder will not solve the missing patch file...my honest opinion.
Hi adam, I saw your review of cores3, sad that this part is not as straight foreward as one can expect.if i reckon correctly you struggled to get uiflow burned to the device as well. I did not get gow you did it!
But you erase first the mwmory using m5 burner.
The boot load mode was quite tricky to trigger.seems like
On the atom s3 i need to press the side button for 3 seconds and a green led is shining for 2 secs i however do not know if you started thw mode. It stays in this mode untill you power off.
No it doesn't start in this mode. Thank you for watching the video.
The second time it work fine.
Connect to computer,
Press and hold boot button for a few minuets and "Port ***** detected" will show,
Click erase and wait,
click write and wait,
power down and rest the S3 device and UIFlow starts.
Hi Adam, so: I unzip my file in programm subfolder.
However I connected the s3 to it. and push the left side button until green led flashes....then connect com6 (the detected port com there it is green) It fails to erase or to burn. failed to get mac. also when reducing the baud rate to 11000..
I tried even the easyloader software without success...
I refer to ENOENT as Error no Entity, it means something is missing probably in you background tools.It's possible you need ESPIDF or ESPTool installed but I can't remember
Ok thks adam.
By the way i have a m5stick cplus. I could burn uiflow on it.
Does it mean then i can install any program made with uiflow on it?without needing to install the program via m5burner?from uiflow.
I am looking for the key of each part cannot find those i have the sn feom the label ...
By the way i printed the part yesterday and i neede to scale it a bit to fit the tailbat and a m5atom s3. Thank you for that you saved me time also i had to print it 3 times before getting the right dimensions.
It may be due to my printer tolerances! I will send you the dimension i used. Bye
I have two stickv card what are those for.
@dr_froggy_rd You install UIFlow for the stickCplus to the StickCplus and the API key will be shown on the screen.
DR_Froggy_rD last edited by DR_Froggy_rD
thx Adam....As you said I found it..
I still do not know why it is not workimg with atom s3
For the S3 Generation you need to hold down a button for several second to get it into boot mode, M5Burner will report a new port detected and then you can try accessing the settings.
what the fuck esptool is not good. somehow
DR_Froggy_rD last edited by DR_Froggy_rD
It is not working with two Tom s3 i own to burn a firmware on it...
So as it seems to be working on another iot dev kit, i will rather advice going for the stick c..
Have you held the boot button down until the green boot led lights up?