BLENano/RTC Implementation

[dhofstetter]

Maybe in interest with others. I added the changes that have to be done manually if I want to compile for the blenano (see here) device.

Think the impact is not big, but makes creating a new project for this device much easier.

BR

[nvlsianpu]

We still need requirement ^1.0.0. Requested changes were not associated with this requirement . mbed-hal required version 1.0.0 or compatible one. if mbed-hal-blenano requires lower version - then mbed-hal-blenano should be upgrades.

[nvlsianpu]

According to the @dhofstetter explanation, "any version" is the valid requirement.

[dhofstetter]

Yes but have a look at #49 and #50 there I already made a description why the dependency on mbed-hal Version 1.0.0 is not sufficient due to circular dependency problems.

But I'm sorry that my pull request have this commit in there, as it was already targeted with another pull request.

BR

[dhofstetter]

Some of my tests to implement the rtc functionality ended up here :( the corresponding discussion to rtc can be found at #51

I think that the file rtc_int.c won't get compiled, or is not linked for compilation as expected. Do I have to make some special assignments in any file to make sure the file is included as expected?

[dhofstetter]

I finally got everything to compile, think the code is ready for testing and review.

Are their hints how to test? Is the handbook here the correct way?

Edit: By testing with a small sample application, I have the problem that every five seconds the time jumps for five minutes. But I think as the periodic callbacks are triggered in correct intervals the problem might be within my rtc update calculation.

Edit2: I finally managed to correct my time calculation, but i was expecting an interrupt on timer overflow, to trigger my rtc_update latest with timer overflow, but I'm never getting this event anymore.

I thought the EVTEN bits have to be 0 while the INTEN Bits have to be set. Here are my register values during execution

EVTEN<0x00000000>
INTEN<0x00020002>

I don't know why the overflow event never occurs, altough I'm sure that there have been an overflow (If I trigger my rtc calculation with a frequency lower than the overflow time (512 seconds) then the calculation is totally messed up.

[dhofstetter]

I have fixed all issues and commited them into my fork. It's available here for review and testing.

Would be great to hear your opinions about my implementation

• us_ticker.c is now using the rtc_int.c functions to access rtc1
• lp_ticker.c is now using the rtc_int.c functions to access rtc1
• rtc_api.c is using the rtc_int.c functions and is at least updating the rtc value on rtc1 overflow interrupt

Testing locally everything seemed to be fine, but I'm not able to use mbed test environment, to perform this I need more informations.

BR Daniel