@paul-thornton ... and in the boot.py file I have this code: # boot.py -- run on boot-up import os from machine import UART uart = UART(0, 115200) os.dupterm(uart) #disable the wifi radio from network import WLAN wlan=WLAN() wlan.deinit() #disable the bluetotth radio from network import Bluetooth blt=Bluetooth() blt.deinit()

@protonx I made myself a base board too for the Pycom modules. A Kicad sketch is here: https://github.com/robert-hh/Pycom-baseboard It uses pre-built modules for USB/Serial and SD card. I did not want to deal with SMD parts, and space did not matter. It also has the espressif logic for activating the bootloader, and jumpers for the connection to Reset, Tx, Rx and P2. Not that this costs less than an Pycom expansion board, but it makes fewer troubles when using (no PIC, standard drivers, ..)

@einarj said in Expansion board 3.0 power consumption: @crumble Your initial answer was using the Pycoproc together with the expansion board 3? Yes. You came back with i2c problems. The Pycoproc is used by pysense and pytrack as well. All 3 boards use the PIC for handling firmware update, deepsleep and so on. But there is a chance to run into this i2c problem - depending on firmware version and your hard-/software setup.

@robert-hh Works like a charm, thank you so much!

@stevo52 Yes, from the distance, it sounds like a hardware problem with the board. Maybe a broken wire or a bad solder point at the P2 pin.

@paloma https://forum.pycom.io/topic/3834/lopy4-will-not-boot-via-battery-power-on-expansion-board/3 https://forum.pycom.io/topic/3436/expansion-board-3-0-battery-power-not-enough-juice/13 https://github.com/pycom/pycom-micropython-sigfox/issues/167 It seems connecting P8 to 3V3 solves the issue (or an issue which is similar to yours, at least). Don't ask me why.

@robert-hh OK, I set up some code to try this out, several timers at different periods and several threads including one to start LTE, send an SMS and then deinit. From what I can see, the timers do NOT get interupted by the LTE device. It seems the timer counts are retained and dumped to REPL as soon as possible (buffered apparently). There is some corruption/mixup of REPL lines but all the timer flags are there I will investigate a bit further and see if I can use this to my advantage. One thread/timer I will need will be at 11uS preferably, so as it is too fast to capture by eye, I'll have to write to a file to a file to evaluate any impact by the LTE device. Biggest constraint might be the actual time to write to disk. A FIFO data buffer is probably a good solution - some work to do there. The test code was pretty rough and ready so its needs a lot of refinement to be truly useful as a valid test.

@luca-gamma Perfect. Glad you got it sorted :)

Hi there, I got little more clarification to the issue. When I used I2C bus 1 (instead of default 0) and pins P10 + P11, I got the I2C bus to work. I've have the impression that I2C bus 0 and pins P9 + P10 might be reserved or something like this. Can anyone confirm if they're used by UART or button on Expansion board or something like this? Does anyone know, if 10x orange led blink on Expansion board is some error message? I did not find anything related to this while searching.

@ldbm we don't publish schematics of our products, sorry.

Nevermind. It works now. The correct function is: lora.nvram_save() and lora.nvram_restore()

@mci For coding the content of the pins.csv file is effective, because that file is used for mapping the Pxx and Gxx numbers to the GPIO port numbers,

I've had Zadig be a bit fiddly in terms of getting the timing right. Ive not seen it take that long just to build a catalog. certainly not on decent hardware. On my laptop: i7 6700k, generic sdd. it was basically instant. are you seeing high cpu/io usage during those few seconds? (Admittedly it'll be hard to diagnose given the few seconds of time constraint..)

@averri Besides that, I tried adafruit-ampy, which seems to be used by pycharm, and it works fine. Please be aware, that the files on the device mist be stored under /flash directory (or /sd, it mounted there). So a boot.py must have the target name /flash/boot.py

@averri In Putty settings you should set flow control to None

@vflorio94 this error can happen frequently, it happens when the url is available, but the board doesn't accept connections. Or when the board is starting, it might take a few seconds to be able to connect to it. You don't have another connection to the board, right? (And I assume you have tried hard resetting, disconnecting power then trying again)

Hi @dpalharini Does the board work when powered with USB? Try pulling P8 high, if you also want to use the SD card, use a 10k pull-up.

@eric73 This seems to have solved my problem! Thanks!