MicroPython Forum (Archive)

on BBB running make test I get the following... 472 tests performed (15282 individual testcases) 446 tests passed 3 tests skipped: cmd_showbc cmd_verbose extra_coverage 26 tests failed: array_q attrtuple1 builtin_range bytes exception1 gen_yield_from gen_yield_from_close gen_yield_from_ducktype gen_...

OK so I booted up my BBB and attached an Ethernet string. logged in as root. ~# git clone git://github.com/micropython/micropython.git ..... ~#apt-get install libffi-dev .... ~#cd unix ~/micropython/unix make .... ~/micropython/unix ./micropython WOW it works so my question is... how can I do i2c ac...

oh right, I wasn't aware CPython was so clunky, has anyone put uPython on beaglebone black, maybe I should try that instead of the 2.7? default version

thanks

am I missing something, but what is the reason for the linux and windows build of upython, if your not involved in the actual upython development, (asbestos suit on)

fwiw, I'm a windows guy and I can say this all works as expected.
ie put the pyboard into dfu mode (hard or soft).
Run the sfu demo program.

just about to go and watch tfi and I caught one

the command I sent was... ' this is very repeatable

I am using this to remote control the i2c bus, say up to 64 bytes of data, I use raw repl to print(i2c.mem_write(....) et al, and codec.escape_decode to convert back. The largest command I send / recv is under 100 bytes or so, and the failure cases can be quite short I get this quite regularly on th...

fwiw: There is a bug in the raw repl, if you soak test sending commands it will eventually report a syntax error with a dropped character, the only way to recover is to reboot and resend the command, this happens maybe once every thousand commands. @Dave: I notice you use the pyboard module, have yo...

yeh they are tricky... if you read the data sheet the register sub address is in bits 6:3 (NXP SC16IS740/750/760 pg 42, Table 3.3)
nice try tho...