[PATCH v3] score: Fix simple timecounter support
marcos.diaz at tallertechnologies.com
Fri Jan 22 18:20:51 UTC 2016
Ok, I'm testing this, but I'm having one problem:
When I compile my example for testing the timer, I ran out of ROM memory...
for 42456 bytes
This commit is from the trunk? because the last time we tested in 4.11 it
worked OK, and that seems a lot of space incremented.
On Fri, Jan 22, 2016 at 3:33 AM, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:
> On 21/01/16 14:50, Daniel Gutson wrote:
>> El 21/1/2016 10:08, "Sebastian Huber" <sebastian.huber at embedded-brains.de
>> <mailto:sebastian.huber at embedded-brains.de>> escribió:
>> > On 21/01/16 14:04, Marcos Díaz wrote:
>> >> Just a question, isn't this hardware counter used for debugging? This
>> won't cause us any problem for debugging?
>> > Why should it cause problems?
>> Beside any problem, how this affects debugging since this is using indeed
>> a dubigging resource?
> I don't share your concerns. You can start and stop the cycle counter. Why
> should a debugger stop it? You can read the cycle counter. What is the
> problem with this? You can reset the cycle counter. Why should a debugger
> do this? You can do nothing else with the cycle counter.
> Sebastian Huber, embedded brains GmbH
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone : +49 89 189 47 41-16
> Fax : +49 89 189 47 41-09
> E-Mail : sebastian.huber at embedded-brains.de
> PGP : Public key available on request.
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
San Lorenzo 47, 3rd Floor, Office 5
Phone: +54 351 4217888 / +54 351 4218211/ +54 351 7617452
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel