@ajb2k3 That's great, many thanks have placed order today Looks like the perfect thing and just what was needed :)

Here are some additional details:

When I initially scan for the I2C bus, it says:
Scanning...
I2C device found at address 0x70

After pressing the reset button in AtomS3, it says:
Scanning...
I2C device found at address 0x44
I2C device found at address 0x70
I2C device found at address 0x76

I tried using Wire.end() to end all I2C communication, but the addresses still remains open. How to close them?

void scanI2CBus() { byte error, address; Serial.println("Scanning..."); for (address = 1; address < 127; address++) { // The I2C address 0x00 is reserved and the addresses should be between 0x01 and 0x7F Wire.beginTransmission(address); error = Wire.endTransmission(); if (error == 0) { Serial.print("I2C device found at address 0x"); if (address < 16) { Serial.print("0"); } Serial.print(address, HEX); } } }

@uberdweeb Hello! Sorry for late answer, but I have the fix for it. All you need to do is modify the platformio.ini file, and write this into it:

[env:m5stack-stamps3] platform = espressif32 board = m5stack-stamps3 framework = arduino build_flags = -DARDUINO_USB_CDC_ON_BOOT=1 monitor_speed = 115200

@teastain I wish I knew and it is on my plans to test but I haven't got that far yet. I think if you can program it on an RPI (not pico) then you should be able to control it on the CoreMP135
I was looking into the device tree overlays and how they work but didn't get very far.

@AndresCotes you need to learn how to program in linux and about Device tree overlays.

@teastain I posted an issue in the library repo, perhaps the ambiguous comment will be clarified. M5Core2 was updated last Jan 29, latest update to M5Unified was 3 days ago.

@felmue the computer probably needed to remove the temp files associated with the site

@Prashant today its working with the same username and password dont know what was the problem

The same way you would with other devices, see this video : https://www.youtube.com/watch?v=Z1i93cYSPIQ

@ajb2k3 said in M5Burner Error Burn Bin to Cardputer After Burn UIFlow2.0:

ESP-IDF

Well at least that gives me some sense of avenues forward. Thank you. What are the other options for burning the software? I have some rasberry pi's and picos, and Chrome seems to have some ability to interact with the unit.

Edit: Xcode and possibly another driver CH34x_MAC got it working.
THANK YOU!

There is a bug in the AXP2101 begin() logic which means the Core2 V1.1 doesn't start on DC power.

The current official fix, along with my variant can be found here https://github.com/m5stack/M5Core2/commit/c26f1b63635c90d9bd82d87db6ab4d9048b3a1b5 .

Both check to see if VBUS is powered before deciding whether to enable the DC-DC converter. The original V1.1 behaviour is to always enable, and this causes an error shutdown from the AXP2101.

@felmue

Thanks for the help! I've got it working now :)

@sgllama i could not explain better! Thanks!.
Finally i´m doing with UIFlow, and sending broadcast UDP orders. Every Core unit will have its own orders. About the router option that will give always the same IP address to same mac devices, i have to take a look at that option.
The problem that i´m facing now is that when i want to receive an UDP packet, the loop program gets waiting until a packet arrives.