MicroPython Forum (Archive)

I updated the repository. Should be:

Must be n >>= 1.

Thanks for staying on focus. In the last days I made a few additions to the Development branch at my repository, especially: adc.read_timed_into(buffer, freq) dac.write_timed(buffer, freq [, count]) Both methods use a hardware timer and DMA for data transfer, so the timing is precise and does not in...

Could be like that below. The driver requires for oversampling the log2 + 1 of the number. x1: 1 x2: 2 x4: 3 x8: 4 x16: 5 That is calculated with the log2i() function. def log2i(n): result = 1 while n > 1: result += 1 n >>= 1 return result #bme280 sensor addresses bme0_i2c_address = 0x77 bme1_i2c_ad...

I updates as well my variant of the BME280 driver at https://github.com/robert-hh/BME280. The bme280_int.py version is based on the same driver as the one you use, with a small bug fix in processing the calibration data. But that has only rarely a minor effect on the results.

So I have a modified code here. It can be loaded. But I cannot tell if it works, since I have given away my BME280 sensor. The mode parameter is now either a single int or a tuple of three ints with (mode_hum, mode_temp, mode_pressure). # Authors: Paul Cunnane 2016, Peter Dahlebrg 2016 # # This modu...

The driver can easily be modified. If you change the API to supply a tuple of 3 values for oversampling instead of a singe value, these values can be sent to the chip. There seems to be only a single place where that happens.

Basically the board runs a single task, and boot.py and main.py run sequentially. To get more that a single task handled, you have at least two options: 1. Threading. That allows to start additional tasks which run in parallel to the first task. Therading uses exhausting multiprocessing. 2. Aysncio,...

The feather board has the espressif boot loader logic. So esptool.py will switch the device into bootloader mode automaitically, Strange enough, GPIO0 seems not to be connected to the board's pin headers.

You should be able to write:

mpremote connect /dev/cu.usbmodem14401 mount .

or whatever the port name is.