MicroPython Forum (Archive)

Ok so this suggests that MicroPython itself isn't working. So before you try and get the repl working on the F4R9 usb interface (which you're calling the OTG port), you should just get MicroPython itself to work (i.e. get a REPL via the stlink). It sounds like you're going to need to use the debugge...

the only 2 files i saw were mbed.html and detals.txt. I am not sure if REPL works in this case. Could you be more specific about the "give you ttyACM0". This USB drive is the ST-Link. The device should show up as three things: - A MSC drive (which you're describing) - A st-link interface (the thing...

I'm sure Peter will reply in more detail, but I'd guess that https://github.com/peterhinch/micropython-mqtt is a good place to start.

Here's a recent thread discussing it -- viewtopic.php?f=18&t=7259

Hi, I think you might be confusing SPIRAM for SPIFLASH. Which are both external chips, but the external chip you see in that diagram in the bottom right hand corner is the USB interface. The SPIRAM/SPIFLASH chips are typically inside the metal can (i.e. inside the WROOM module itself). The WROOM mod...

Hi, Yes, you've pretty much described it correctly. The ones with the extra digits are the nightly builds. So all options (IDF 3/4, generic/spiram/tinypico) have nightly builds. However, the IDF4 build (and the TinyPico build), were added after the most recent release (i.e. 1.11), so there are _only...

Does the REPL work when you connect via the ST-Link? i.e. the USB port that gives you the mbed.html/details.txt, it should also give you a ttyACM0 which will have the MicroPython REPL. That way you can at least confirm that MicroPython is working. As we did some research on the datasheet of STM32L4R...

Simple version: The module is called "ublueooth", but "import bluetooth" and "import ubluetooth" are the same thing. You should use "import bluetooth" (same as "import machine, time, json, os") Longer version: In MicroPython most of the core libraries are named ufoo (including umachine, ubluetooth, ...

Yeah, it's likely the "-u" that's causing a problem. Assuming there's no way to tell PyDev to use different flags, I wonder if you could try wrapping the micropython binary in a shell script that ignored arguments? Otherwise it should be pretty easy to modify ports/unix/main.c to ignore -u (or bette...

Another option is to use the hardware SPI (or UART) to transmit a precise waveform on the MOSI (or TX) pin.

This will give you very precise control of the pulse width, and spacing (and even allow you to vary it over time, allowing for an acceleration profile).

If the module has SPIRAM (also known as PSRAM), use the GENERIC_SPIRAM. Otherwise, use GENERIC.

The linked page points to https://docs.espressif.com/projects/esp ... er-modules which shows which modules have SPIRAM.