OpenCores
no use no use 1/1 no use no use
Timing problem in latest toolchain version.
by meitoku on Jun 1, 2014
meitoku
Posts: 26
Joined: Nov 21, 2013
Last seen: Oct 18, 2015
I noticed a timing problem in latest toolchain version. Some programs that use timer works well with toochain versions before April 2014 now behave erratically.

Example: timer.c in https://github.com/juliusbaxter/orconf2013/blob/master/sw/timer/timer.c. It is a led counter, but now with the latest or1k-gcc commit, the timer didn't work, first one led turned on, then all the led flashed immediately. When I switched to commit d2093f8f4d182be22b24b459badd9f555859cc6f of or1k-gcc and commit 7d53ef07ae838a707e2ca8a467e51cd1174cf388 of or1k-src, I got no such problem. BTW, I wish I could open an issue on that github page. I think it's because of or1k-gcc, but it may be or1k-src too.

RE: Timing problem in latest toolchain version.
by wallento on Jul 31, 2014
wallento
Posts: 28
Joined: Jan 24, 2009
Last seen: Nov 8, 2018
Hi,

I am quite sure it is or1k-src, you can copy the issue there. I changed stuff in the or1k-support in https://github.com/openrisc/or1k-src/commit/b50a0677685f4019ac4c7bb1cde778b0382fceb7 and suspect this one. I thought the changes did not break existing applications but will check this again.
At the moment I am on a business trip, but will try to find the time asap.

Bye,
Stefan
no use no use 1/1 no use no use
© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.