Rshell works pretty well, although the newer M5 releases are a lot harder to get into the correct mode, particularly on the atom.

Uiflow is micropython: I have often written something in uiflow and then switched to the micropython side to see what the python is for a given uiflow thing. And then I can cut and paste into repl.

For long-term debugging (fails once a day or week), I leave the device connected to putty.

I have considered adding code that would catch Exception () in the main loop, do a stack trace, and save it into a file so that I don't need it to always be connected, but have never implemented it.

@medy mostly:

print(dir(wifiCfg))
print(wifiCfg.__dict__())

I'm sure that someone has written a function that formats all this, recurses, etc, but I usually just do it manually, because there are usually only a few things that make sense to try.

Also googling for micropython wifiCfg (or whatever), because micropython is not just for M5, and a lot of the code is on the internet. It's not always exactly the same, but it often is, or is close enough to provide hints for more things to look at.

I'm assuming that you know how to use rshell or some other tool to get to repl so that you can just type in statements as they occur to you, rather than writing a script for every new thing you want to try.

@keesjan With micropython, port 22 works fine, and as expected:

CDS_PIN = 33
TX = 19
RX = 22

As an aside, the idea that the labeling of the pins is "oriental logic" shows an unawareness of the history of rs232 and is a bit insulting. The question of what to label the pins depends on whether the manufacturer thinks of the device as DTE or DCE: StackExchange has a good explanation of the history.

In particular:

'some manufacturers try to "help" by effectively labelling their DTE equipment as if it was a piece of DCE. They mark their data input pin as Tx so that user just connects "Tx" from the external device (which, if it's DTE, will be the data output from there) to the pin marked "Tx" on their equipment (which they know is an input). Thereby allowing them to say "just connect Tx on your device to Tx on our equipment". They think they are trying to help, but such labelling often just adds to the confusion.'

Hmm, OK, get_wifi() works on 1.5.4, so maybe I just guessed wrong back then.

Some time ago, I asked where the wifi config was held.
At that time, the answer was:

 import wifiCfg
      self.ssid, self.password = wifiCfg.deviceCfg.wifi_read_from_flash()

Fast forward to 1.7.0:
I have set the WiFi credentials with M5burner 2.2.2 via "Configuration". But the above returns an empty list, rather than actual credentials.

Apparently the new hotness is:

wifiCfg.deviceCfg.get_wifi()

It's a bit frustrating when this keeps changing, and there's no user-visible notice, just broken code. Can we get some kind of announcement of functionality-breaking changes?

Re: Running code with rshell?

I had rshell working for a while, but now it is failing. I filed https://github.com/dhylands/rshell/issues/138, but I wonder if it is because of the fancy UISHELL ascii logo?

This is on the Atom Mini, so it's a bit tough to figure out!

I'm running v1.6.2-lite on it, and REPL says:

MicroPython 400ff3bbf-dirty on 2020-08-06; M5Stack with ESP32

Thanks, once I got the other computer to see the device (can't flash a device that doesn't show up in device manager), I was able to reflash it.

Then I took it back to my laptop, and it still wasn't seeing it. So I switched USB cables, and it did. Then I switched back to the original USB cable, and it worked with that cable again. (Note that I had hooked up a M5StickC via the original USB cable, and it is working fine with that cable now, so the cable isn't bad).

Gotta love Microsoft Windows sometimes.

This was the super-frustrating "windows doesn't recognize a device. But a different windows computer does". :(

I hooked up a 10K resistor and a CDS cell (resistance 50k-1M) in series from 3v3 to GPIO36. I set the pin to ADC mode, and was reading between 3000 & 4095.

But now the gray isn't working. It doesn't show up as a serial port on the PC. If I try playing the built-in rock/paper/scissors, it goes black as soon as I push a button (https://claar.org/gray.mp4).

So, did I kill my gray? If so, what did I do wrong? I don't want to repeat with another piece of hardware!

Google suggests that 10K should be plenty as a pullup, and an ohm meter shows that the resistance goes between ~60K to 1+M, so I didn't use the wrong resistor (and the CDS is 50K in any case).

I guess I misunderstood what support said: "If you are connecting through 3.96 terminal, 12V DC is required" seemed to say that I needed 12V to use the serial pins.