<time.h> clock() HARD FAULT

RE: clock() HARD FAULT

Susheel Nuguru — Tue, 21 Jul 2015 12:22:58 GMT

thanks for updating :)

RE: clock() HARD FAULT

Victor Nascimento — Tue, 21 Jul 2015 12:19:11 GMT

Turned out that my time_consuming_task() function was giving a Stack Overflow, thus hard-faulting the processor. I presume it has nothing to do with clock().

RE: clock() HARD FAULT

Susheel Nuguru — Tue, 21 Jul 2015 11:59:48 GMT

Victor, could you please update this thread with latest info, I want to avoid closing threads with goodinfo as unresolved

RE: clock() HARD FAULT

Susheel Nuguru — Mon, 22 Jun 2015 13:59:42 GMT

@RK, i think the clock() just return the current tick which is updated in systems with operating systems. Here as there is no OS, it will never get updated and hence will return the same value always. It would compile as the variable do exist in the library, just that the mechanism to update it does not. Using clock() is of no use here.

RE: clock() HARD FAULT

RK — Mon, 22 Jun 2015 13:27:49 GMT

where's the implementation of clock()? Sure it's in the standard c library but I can't see how it could possibly be implemented on something with no operating system, no real time clock, no gettimeofday(), no nothing. I'm fairly surprised it links, I'm not at all surprised it fails.

RE: clock() HARD FAULT

Victor Nascimento — Mon, 22 Jun 2015 12:58:59 GMT

I comment the line, code works fine. I don't know what happened.

RE: clock() HARD FAULT

Susheel Nuguru — Mon, 22 Jun 2015 12:47:53 GMT

It should not have hardfaulted. Are you sure that clock() function is causing it?

RE: clock() HARD FAULT

Wojtek — Mon, 22 Jun 2015 11:59:20 GMT

If You are using RTC in Your project, You can just check it's registers value to see time passing. Check app_timer.h library. Or You can set/clear GPIO and measure time on oscilloscope...