This fixes that.Īlso, if you are using nRF51 there are some bugs in the us ticker implementation that cause this to crash. Return the number of microseconds since boot.Įdit: I updated it to use 4 timer inserts instead of 2 - some implementations (the good ones) execute events that are 'in the past' immediately, so there is a chance that insert(0x80000000) when we are at 0 will happen immediately. Return the number of milliseconds since boot. Return the number of seconds since boot. The number of times the us_ticker has rolled over. then mTriggers now equals 1 and we want to insert at 0x80000000. ![]() If this is the first time we've been called (at 0x4.) Return mTriggers * 0x40000000ull + (ticker_read(_ticker_data) & 0x3FFFFFFF) be considered to be in the past and executed immediately. It measures time by the number of seconds that have elapsed since 00:00:00 UTC on 1. Also because if we only use 0 and 0x80000000 then there is a chance it would Unix time is a date and time representation widely used in computing. code that calls interrupts that are "very soon" immediately and we don't I would suggest adding some non-internal functions like this: This seems like a sorry situation for mBed's otherwise great API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |