While they share the same register maps, the FRAM devices from Cypress
and Fujitsu return a different data structure when the RDID register is
read.

This driver will panic if HAL_RAMTRON_NO_FALLBACK is defined in the
hwdef.dat file and the RAMTRON initialisation fails. This prevents us
from silently falling back to a potentially different parameter set and
causing unexpected behaviour.

…is used

Note: This usually won't get seen as the USB is not up when this is
printed. However, adding a delay (of ~2s) into the main_loop() function
in the HAL_ChibiOS_Class.cpp, just after the scheduler is initialised,
will allow this message to be seen.

…efined

This #error pragma causes the Bootloader to fail, even though this file
class isn't used by the Bootloader. However, it is included in the base
AP_HAL definition that the Bootloader pulls in.

…e bit

Inline initialisation of VLAs will cause a compilation error under
Clang, as it is not allowed according to the C specification. However,
GCC will allow it.

::printf() is available earlier than hal.console->printf() during boot.

Change from HAL_RAMTRON_NO_FALLBACK to HAL_RAMTRON_ALLOW_FALLBACK.

This adds equivalent functionality that was originally added in:
ArduPilot#13581

This adds equivalent functionality that was originally added in:
ArduPilot#13581