Search found 778 matches

by Roberthh
Mon Nov 06, 2017 6:38 am
Forum: Development of MicroPython
Topic: MICROPY_PERSISTENT_CODE discussion
Replies: 7
Views: 256

Re: MICROPY_PERSISTENT_CODE discussion

Functions decorated as @micropython.native, @micropython.viper or @micropython.asm_thumb are compiled into native machine code. Frozen bytecode must only contain ... bytecode, not machine code.
by Roberthh
Sun Nov 05, 2017 3:01 pm
Forum: ESP32 boards
Topic: Tool uPyLoader for MP on esp32
Replies: 19
Views: 675

Re: Tool uPyLoader for MP on esp32

That's what the source code tells: // Attempts to use UART0 from Python has resulted in all sorts of fun errors. // FIXME: UART0 is disabled for now. if (uart_num == UART_NUM_0) { nlr_raise(mp_obj_new_exception_msg_varg(&mp_type_ValueError, "UART(%d) is disabled (dedicated to REPL)", uart_num)); } S...
by Roberthh
Sat Nov 04, 2017 5:40 pm
Forum: ESP32 boards
Topic: Tool uPyLoader for MP on esp32
Replies: 19
Views: 675

Re: Tool uPyLoader for MP on esp32

Looking into the mcu scripts in the link you gave, it seems that you could replace UART.read() by sys.stdin.buffer.read(), and UART.write() by sys.stdout.buffer.write(). You have to disable keyboard interrupt with micropython.kbd_intr(-1). You can re-enable it, when the script closes, with micropyth...
by Roberthh
Thu Nov 02, 2017 8:18 pm
Forum: ESP8266 boards
Topic: FTP Server
Replies: 25
Views: 5674

Re: FTP Server

After using it for a year now, I added some functions from the ESP8266 ft server to the simple variant, which runs in foreground and works both on ESP8266 and the ESP32 port. I added active mode and a few command variants used by Windows machines. Now it supports Windows command line ftp, and allows...
by Roberthh
Wed Nov 01, 2017 9:25 pm
Forum: The WiPy and CC3200 boards
Topic: WiPy wireless connection
Replies: 1
Views: 130

Re: WiPy wireless connection

Try www.pycom.io as password. That is used by WiPy 2. If you happen to have that board, you find dedicated support at forum.pycom.io
by Roberthh
Mon Oct 30, 2017 7:24 am
Forum: The MicroPython pyboard
Topic: REPL Pyboard over serial not USB
Replies: 8
Views: 358

Re: REPL Pyboard over serial not USB

This is just to confirm the issue, that Ctrl-C on dupterm does not interrupt code. A first glance into the code shows, that, in contrast to USB, Ctrl-C for UART is indeed not handled by the interrupt routine, but only when getting characters form the buffer. This is an open issue since two years: ht...
by Roberthh
Sun Oct 29, 2017 7:39 am
Forum: ESP8266 boards
Topic: Multiplexing SD card pins
Replies: 6
Views: 235

Re: Multiplexing SD card pins

There was a discussion about this, and I made a few test: For toggling speed, read this thread to the end: https://forum.micropython.org/viewtopic.php?f=16&t=2766&hilit=toggle For reading bit durations, there is nothing like the pulses_get method of pycom.io, so you might us similar like toggle for ...
by Roberthh
Fri Oct 27, 2017 11:35 am
Forum: ESP8266 boards
Topic: Multiplexing SD card pins
Replies: 6
Views: 235

Re: Multiplexing SD card pins

If you are using sdcard.py from the drivers section: as far as I can see, this code does not make use of interrupts. You are limited to use the SPI pins for SPI only, and all devices have to use a common setting for the parameters. And yes, the ESP8266 is very limited with PINs, and some of them lik...
by Roberthh
Thu Oct 26, 2017 3:20 pm
Forum: ESP8266 boards
Topic: Serial REPL not responding
Replies: 9
Views: 340

Re: Serial REPL not responding

Supply voltage tolerances are typically at least +/- 10%. The ESP8266 is specified fo a VDD range of 2.5 - 3.6V, and 3.25V is well within the specs of the LD1117 regulator, which should have a dropout of about 1V at 200 mA. So that looks well for me. If there is a voltage problem, then small dropout...
by Roberthh
Tue Oct 24, 2017 9:04 pm
Forum: ESP8266 boards
Topic: Serial REPL not responding
Replies: 9
Views: 340

Re: Serial REPL not responding

I had a similar experience with an ESP32 board, wich stopped responding a few minutes after turning it on. It was caused by bad soldering, only visible with a good magnifying lens. After resoldering now it woks fine. Even if it does not look like that in your case, it could be a intermittent hardwar...