MicroPython Forum (Archive)

ok thanks chaps, looks like its time to expt but at least I have some pointers of where to start

thanks dave, but I was hoping for even more hand holding (sorry), ive installed the arm toolchain, but windows doesn't have make so I downloaded a make for win32 and I get a tr problem, I'm thinking I might need a whole bunch of stuff to get this to build, maybe it would be easier to stick mint? on ...

Hi, could anyone point me to any information on building upy on a windows machine, all the info seems to be Linux.

Hang on there is another stretch goal for 15K, sounds like my management

OK I have found a way to recreate without any hardware, and this doesn't happen on 1.5.1 from pyb import I2C pyb.Accel() i2c=I2C(1,I2C.MASTER) i2c.mem_read(1,76,112) # works i2c.mem_read(1,77,112) # fails OSError 5 i2c.mem_read(1,76,112) # fails OSError 116 i2c.init() i2c.mem_read(1,76,112) # STILL ...

You don't mean this do you
http://micropython.org/resources/microp ... ngeLog.txt

OK this version (1.5.2) has introduced a breaking change for I2C. It is impossible to recover from an I2C bus error 1.5.1 from pyb import I2C i2c=I2C(2,I2C.MASTER) i2c.mem_write(8,76,112) # force a reset causes i2c error (but not until we next do a read) i2c.init(I2C.MASTER) # reset the i2c bus to r...

Well I agree it would be more consistent but note that
A is 65 decimal
B is 66 Decimal
@ is 64 decimal

What you describe is what I get using python3 on a PC.
Isnt this just the way python stringifies byte arrays ie prints the char or if not printable then the \x value

OK Something has broken (changed?) using the I2C bus between version between 1.5.1 (23 Nov) and 1.5.2 (31 Dec). :( My code has suddenly stopped working. The problem is related to a failure condition which reports an OS Error but only on the next i2c transaction. I used to be able to recover by recre...