No console output in PyMakr whatsoever

[robert-hh]

@techykermit WiPy2, SiPy and Lopy all have limited RAM. A source code file of 49k may fail on importing/uploading. You could try to pre-compile the files on your computer with mpy-cross and upload the compiled versions.
Problem: the mpy-cross executable is not published by Pycom. And with today's release they changed the format. So mpy-cross versions that are out ther will not work. Which operating system are you using on you computer?

[techykermit]

@robert-hh I am running Windows 10. Also, I am trying with a WiPy 3. Is MPy-cross compatible with version 1.18.0 (legacy)? In that case, I can just downgrade for now, if you are expecting support for it to be carried on to the newer firmware in the future.

[robert-hh]

@techykermit Wipy3 should has sufficient RAM. The mpy-cross version I have here https://github.com/robert-hh/Shared-Stuff should work with v1.18.0. Filename mpy-cross_pycom.exe
Edit: as crosscheck when having trouble with pymakr youj should always confirm with a simple console like putty, that not pymakr is the source of trouble.

[techykermit]

@robert-hh said in No console output in PyMakr whatsoever:

Edit: as crosscheck when having trouble with pymakr youj should always confirm with a simple console like putty, that not pymakr is the source of trouble.

I am talking to my device via the COM port. Does Putty work with interacting with the device that way? (Probably dumb question, but I have never sent any commands to a Pycom outside PyMakr. Thonny IDE didn´t detect my Pycom either.)

[robert-hh]

@techykermit Yes, Putty is made for that. Take care to set the flow control option in Putty to None.
Meanwhile I was able to build a version of mpy-cross.exe for today's release. name: mpy-cross_pycom_v4.exe

[techykermit]

@robert-hh Converting all the files to .mpy does not make any difference at all. The original issue still persists.

PuTTY gives the same output as PyMakr.

[robert-hh]

@techykermit What happens if you push Ctrl-F? That should force a safe boot.

[robert-hh]

@techykermit Maybe you should shoe more of your code. Because what is above should not cause any harm.

[techykermit]

@robert-hh Yes. As I am developing a production application, I want to disclose as little as possible.

My code seems to run fine on the board, I have everything mapped to LED colors. I am just not getting any print output.

Ctrl+F in PyMakr doesn´t work (maps to the Find function in VS Code). Trying with PuTTY, it does nothing.
I have an Expansion Board 3.0, can I press the "Safe Boot" button on it? I assume that will safe boot it, but when I have tried, nothing really happens.

[robert-hh]

@techykermit Do you re-map or reconfigure UART0? Or do you use uos.dupterm() to reconfigure the standard output?

[techykermit]

@robert-hh No, unless one of the libraries I am using does that.
Obviously I don´t expect you to look through them, I can do that tomorrow, but here is a list of everything I currently have in the lib folder:

• os (from the MicroPython repository on GitHub)
• The umqtt/simple library (from the MicroPython repository on GitHub)
• The dth.py library from https://forum.pycom.io/topic/1172/pure-python-library-for-reading-dht-sensor-on-pycom-boards
• My own internal libraries which do not reconfigure any output or UART0.
• PyCom´s OneWire library
• pkg_resources (from the MicroPython repository on GitHub)
• ulogging (from the MicroPython repository on GitHub)
• urequests (from the MicroPython repository on GitHub)

[robert-hh]

@techykermit Unless you use them, they do not harm. But for what purpose do you have the os module? That is intended for the Unix port. On a micro, you should use uos, which has os as it's alias.

[techykermit]

@robert-hh I removed the os module and now everything seems to work fine. Thank you so much for actually taking time and helping out :))