[STM32L4] Set NVIC_RAM_VECTOR_ADDRESS to 0x10000000

[bcostm]

Fix issue #1413
Fix issue #1509

[0xc0170]

Please consider writing a test for this feature. Did you use any existing test to verify this? There's interruptIn and InterruptIn2 test units.

@sg- @bridadan We shall provide some docs in test/ folder to encourage writing tests. I dont see much docs in the test units there.

[bcostm]

I just checked the Nucleo_interrupt example but I didn't run the mbed tests. I'll do it too. But I assure you that the 0x20000000 is really a mistake...

[0xc0170]

But I assure you that the 0x20000000 is really a mistake..

Yes, therefore the test should be there and run.

[bcostm]

I ran the InterruptIn test. The InterruptIn2 test is not automated for these boards nor the Interrupt_chaining test. Nevertheless the InterruptIn test shows well the correction.

ORIGINAL with #define NVIC_RAM_VECTOR_ADDRESS (0x20000000) for uARM

+---------+---------------------+-----------+---------+------------------+--------------------+---------------+-------+
| Result  | Target              | Toolchain | Test ID | Test Description | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+---------------------+-----------+---------+------------------+--------------------+---------------+-------+
| TIMEOUT | NUCLEO_L476RG[F32D] | uARM      | MBED_A7 | InterruptIn      |       30.43        |       15      |  0/1  |
| TIMEOUT | NUCLEO_L476RG[F32D] | ARM       | MBED_A7 | InterruptIn      |       30.38        |       15      |  0/1  |
+---------+---------------------+-----------+---------+------------------+--------------------+---------------+-------+

CORRECTION
#define NVIC_RAM_VECTOR_ADDRESS (0x10000000) for uARM

+--------+---------------------+-----------+---------+------------------+--------------------+---------------+-------+
| Result | Target              | Toolchain | Test ID | Test Description | Elapsed Time (sec) | Timeout (sec) | Loops |
+--------+---------------------+-----------+---------+------------------+--------------------+---------------+-------+
| OK     | NUCLEO_L476RG[F32D] | uARM      | MBED_A7 | InterruptIn      |        8.8         |       15      |  1/1  |
| OK     | NUCLEO_L476RG[F32D] | ARM       | MBED_A7 | InterruptIn      |        8.74        |       15      |  1/1  |
+--------+---------------------+-----------+---------+------------------+--------------------+---------------+-------+

[0xc0170]

Thanks!

@bridadan Please have a look at the above

[bridadan]

@0xc0170 InterruptIn results look good.

Regarding InterruptIn2, that test looks fairly unnecessary, perharps we can move/remove it?

Regarding Interrupt_chaining, it looks like it should either be expanded to include all platforms or modified to be general? It looks the #if defined(TARGET) calls are used to resolve IRQ names and LED pins. We can probably figure out the LED stuff, but is there a general IRQ name we can use so we don't have to use #if defined(TARGET)?