sam_xdmac.c edited online with Bitbucket

sam_xdmac.c edited online with Bitbucket

Since I can't (yet) get rid of the sanity checks in config.h, I suppose I should at least update the checks.

Backout d5be40be.  This change is logically correct but unmasks a lot of issues.  Reverted for now.

tools/mkconfig.c:  Go further... remove all autogenerated sanity checks from the config.h header file

Remove CONFIG_FS_READABLE/WRITABLE logic from tools/mkconfig.c.  This logic has been replaced with proper logic in the Kconfig files, it is out of date and an ongoing maintenance problem, and it shoulw not be necessary.

Allows the use of tmpfs when no block driver is available. This is correctly done to define NONBDFS but below the structure is not where it should be.

Fix a bug of GPIO falling-edge interrupt for tiva

userleds: Don't select ARCH_LEDS with BOARD_CUSTOM_LEDS, otherwise we can't use the board_userled* functions

Stm32l4_update_rtc_impl

use INITS flag to avoid magic reg value to detect power up reset state of rtc
correct a problem clearing interrupt flags (they weren't) which prevented an alarm from ever being used more than once per reset cycle

Fix a copy and paste error concerning the CAN driver. In the file sam_matrix.h the define SAM_MATRIX_CAN0_OFFSET is set to the wrong value.

Error is only triggered if the global variable g_mcan0_msgram is located in RAM at an address beyond 0x20400000 + 0x0000ffff. In this case all send CAN messages have the length zero and the CAN-ID is zero as well.

Fix typo in variable name in serial BREAK logic.  Review other serial implementations for similar naming problems.

when setting an alarm, ensure that the respective alarm triggered flag is reset, because the alarms are edge-triggered interrupts

fix nasty bug in ISR handler, where interrupt was not properly acknowleged (write to CR instead of ISR, as intended).  Also, minor, set the LSI prescaler values more appropriately (though not critical since LSI is so low precision anyway).

userleds: Don't select ARCH_LEDS with BOARD_CUSTOM_LEDS, otherwise we can't use the board_userled* functions

correct the RTC_ALRMR_ENABLE value, it needs to ignore the date/dow component since that is not set.  Also, the prescaler value for HSE (which presumes 1 MHz, anyway) had transposed digits.