Pytrack and Pysense firmware release 0.0.3 ??

[livius]

@daniel is this ok?

if (memaddr > 0xFF) {
        if (!mp_hal_i2c_write_byte(self, memaddr >> 8)) {
            goto er;
        }
    }
    if (!mp_hal_i2c_write_byte(self, memaddr)) {
        goto er;
    }

i ask about if (memaddr > 0xFF) {
if it is lower, then only one byte is written?

how device can distinguishe it then from data bytes?
I suppose that this if is unnescessary - but maybe i am wrong (i am not an expert).

[bartp]

@jmarcelino Yes, I downgraded only the LoPy to 1.7.3b1. Pytrack (both modules I have) are running 0.0.3. That works ok.

[jmarcelino]

@bartp
Thanks, so it's unrelated to 0.0.3 and more likely an issue with I2C on 1.7.5, maybe to do with what @livius found.

Makes sense..

I'd hope Pycom would test their releases with their own official add-on boards. I think people quite rightly expect at least these to always work.

[bartp]

@jmarcelino @daniel Personally I think better documentation of what code needs to be updated is essential. I noticed there were updated libraries, updated pytrack firmware, so I assumed I had to update all of them to be 'in sync' with Daniel.

Perhaps it's best to reference to the corresponding change log in each firmware announcement, and mention any pytrack/pysense updated you need to do first.

Anyway, I've no doubts the engineers at Pycom are working full force to bring all promised features into the firmware.

[bucknall]

Hi all,

I ran into this bug yesterday upon testing and I'm pleased to share that it's been resolved now :)

Daniel will be releasing an patch for the bug later today, it was an issue related to readfrom_mem in the I2C class (1.7.5b1). I'll update here when it's patched and uploaded.

We're working on a methodology for better tracking releases and fixes. I have some ideas and thoughts on how we can best handle this publicly but am open to suggestions.

Thanks!

[bartp]

@bucknall @daniel Ok, thanks! Looking forward to the new release.

[daniel]

Hello,

The issue with the readfrom_mem method has been solved. The new release is out: https://forum.pycom.io/topic/1423/new-firmware-release-1-7-5-b2

Cheers,
Daniel

[bartp]

@daniel Confirmed! All is working nicely again! Thanks for the update!

Regarding the original topic; is there a changelog of Pytrack firmware 0.0.3 available?

[bucknall]

@bartp On my current todo list is compiling a release notes page on our docs for LoPy/WiPy/SiPy Firmware, Pymakr Plugin, Pytrack/Pysense Libs and Pytrack/Pysense Firmware. Please bear with us as I'm involved in a number of different projects and am aiming to have this up by the end of next week, followed by updates to it every time we update any of those products

[bartp]

@bucknall Sounds good! Ok, we gaan met jullie beren...