Harald Welte 37220cce25 Disable interrupts during EEFC_ReadUniqueID() ...

Reading the Unique ID from flash is a rather tricky procedure: After the
STUI command has been issued, we cannot read normal flash anymore.
Rather, the unique ID is mapped at 0x00000000. This is unfortuantely
also where the exception vector table is stored.

EEFC_ReadUniqueID() is already linked to RAM, which is good.  Hoewver,
if an Interrupt happens between STUI and SPUI, then we try to access
the vector table and code from flash, which is illegal.  We run into
a hardfault and stay there until the watchdog resets the processor.

Change-Id: I3c4fad55b47e9013f6615a331983b3989ca805a7
Closes: OS#4428

2020-03-01 15:47:42 +01:00

..

libboard_sam3s-ek/resources

Removed sym links, replaced them with actual folders

2015-04-07 20:04:19 +02:00

libchip_sam3s

Disable interrupts during EEFC_ReadUniqueID()

2020-03-01 15:47:42 +01:00

usb

DFU: add DFU application

2020-01-16 20:35:04 +00:00