Toolchain versions
Anthony Toft
I have finally taken the plunge to get my chronos updated with openchronos-ng. I got latest, and configured/built it and seem to have it built something that’s not good. Checking my toolchain versions, it appears that I might not be on the right versions, but I cannot find any updates to the debian packages I am using.
Does anyone have the whereabouts of the correct .deb’s or rpms? I would really like to avoid having to track down and build the chain from scratch!
Paolo Di Prodi
If you read the mailing list you will find out you have to build it from scratch.
Look for my name signature and you should find out the links to a wikipage to build the LTS toolchain.
Believe me start to arrange your teacups will take a lot of time AND patience.
Cheers.
I have finally taken the plunge to get my chronos updated with openchronos-ng. I got latest, and configured/built it and seem to have it built something that’s not good. Checking my toolchain versions, it appears that I might not be on the right versions, but I cannot find any updates to the debian packages I am using.
Does anyone have the whereabouts of the correct .deb’s or rpms? I would really like to avoid having to track down and build the chain from scratch!
--
You received this message because you are subscribed to the Google Groups "OpenChronos" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openchronos...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Dr. Paolo Di Prodi
Anthony Toft
Hmmm, I got all of the approved versions of the tools, it wasn’t _that_ difficult.
However, I am still seeing the same issue. In the Alarm module, if you cycle through the modes (alarm, chirp, off) more than a couple of times, then the watch hangs hard. It stops responding to the buttons (all of them) and there are no display updates. The watchdog doesn’t rescue it and the only way out is to remove the battery for a few minutes. Removing the alarm module prevents this from happening.
Unfortunately I don’t have the time at the moment to fully debug what is happening here, but I suspect the button interrupts are being ignored in this case.