@magillus Did you ever solve this? I scanned the Factory Reset and now cannot
get the scanner to work with my code. A factory-fresh ATOM does still work.

But I too think there should be a way to disable QR codes. In particular, since the ATOM is
receiving the scanned QR - it should be up to the application to do what it wants with the scanned
value.

My sample arduino code is at: M5 Atom Testing

UPDATE It seems there is a prohibit scanning of configuration modes, as follows (and defined in their document Commands

uint8_t prohibit_scanning_config_mode_cmd[] = {0x07, 0xC6, 0x04, 0x08, 0x00, 0xEC, 0x00, 0xFE, 0x3B};

thanks,

Alternatively - using M5Unified you can also call:

M5.Display.sleep();

To wake it up again use:

M5.Display.wakeup();

@ajb2k3 said in ATOM S3, How to switch to online programming mode?:

By pressing the screen on boot
My case, This is to enter programing mode. not come back to App mode.
My version is UIFlow2.0 Alpha28. what version did you success this way?

M5Burner to get into app mode
This doesn't work.
I did following step. Please advice if the step is wrong.

Open M5 burner and select ATOM S3. Connect USB to ATOM S3, hold reset button dew second until internal LED turn on. Click "Configure" of UIFlow2.0 Change Boot option to "Run main.py directly" Click next to burning the setting once window shows "success", remove USB from Atom S3 and re-connect

After this step, the program does not start.
The window is just black screen.
What version of UIFlow are you using?

Hello @Filipe-Dias

have you tried this example with the commented out GPIOs?

Thanks
Felix

All esp’s are like modern controllers are only 3.3V tolerant, the 5v on the grove is for the grove Standered and for sensors that still require 5v.

What programming environment are you using?

@dawncold I also would like to know of any hid docs for the esp32s3

@felmue great! thank you so much for the data!

I have tried using code above and similar from M5Stack repo. I changed the pin assignments to 19 and 22, which works fine on an alt. setup with Atom Lite, Env I hat, and Atom Mate.

Using the setup below:
Atom Matrix
Env II hat
Atom Mate

I get this error and continuous reset loop.

[ 913][W][Wire.cpp:301] begin(): Bus already started in Master Mode.
Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.

If I pull out the hat, I get a warning via the code that it is disconnected. I know the origin of this post was from long ago, but I can't think what could be causing it. Is there any difference between Env II unit and Env II hat? Any other thoughts welcome.

Hello @tomtom22

to you first question: it doesn't matter whether you press and hold the reset button to get the M5AtomS3 into download mode to burn firmware or let the automatic do it.

The press and hold the reset button method is available in case the automatic download mode fails. This can happen if for instance the currently running firmware has an issue causing the device to constantly reset.

I personally let the automatic download mode do its thing and only if that fails use the reset button method.

Thanks
Felix

Boiled it down to minimalistic piece of code to avoind any sideeffects...

Here is a link to 2 different Atom Lite pieces running exactly the same software as shown below.
https://photos.app.goo.gl/KBm54aqW5LbtxsWq7
This video shows them side-by-side.....
They dow not in any direction behave at least a little bit similar.....

Any ideas anyone?

This is running on the Atom Lite now:

#include <Arduino.h>
#include <LiteLED.h>

// Choose the LED type from the list below.
// #define LED_TYPE LED_STRIP_WS2812
#define LED_TYPE LED_STRIP_SK6812
// #define LED_TYPE LED_STRIP_APA106
// #define LED_TYPE LED_STRIP_SM16703

#define LED_TYPE_IS_RGBW 1
#define LED_GPIO 27
#define LED_BRIGHT 100

static const crgb_t L_RED = 0xff0000;
static const crgb_t L_GREEN = 0x00ff00;
static const crgb_t L_BLUE = 0x0000ff;
static const crgb_t L_WHITE = 0xe0e0e0;

LiteLED myLED( LED_TYPE, LED_TYPE_IS_RGBW );

void setup() {
myLED.begin( LED_GPIO, 1 );
myLED.brightness( LED_BRIGHT );
}

void loop() {
myLED.setPixel( 0, L_RED, 1 );
delay( 500 );
myLED.setPixel( 0, L_GREEN, 1 );
delay( 500 );
myLED.setPixel( 0, L_BLUE, 1 );
delay( 500 );
myLED.setPixel( 0, L_WHITE, 1 );
delay( 500 );
}

Update: I confirmed that I can reproduce this issue with the latest version (i.e., v1.12.3). I also tried specifying the SSID and PASSWORD using a Network block but got no luck. Can anybody else reproduce this issue?

@mono-mono go into uiflow2 and change the name by clicking on the device on the bottom of the screen