Add support for wolfHAL crypto backend - #11033

configure.ac:3683

• The board include path is appended without quoting, so --with-wolfhal-board paths containing spaces will be split into multiple compiler arguments and fail to find board.h.

    AM_CFLAGS="$AM_CFLAGS -I$ENABLED_WOLFHAL_BOARD"

wolfssl/wolfcrypt/port/wolfHAL/wolfhal.h:84

• Prototype for wc_wolfHAL_GenerateBlock() uses plain C types, but the implementation uses wolfCrypt types (byte*, word32). On some platforms word32 is unsigned long (not unsigned int), so this mismatch can cause warnings or ABI issues. Match the public prototype to the definition and wolfCrypt conventions (also aligns with wc_RNG_GenerateBlock()).

/* Generate a block of random data using the wolfHAL RNG device.
 * Suitable for use as CUSTOM_RAND_GENERATE_BLOCK. */
WOLFSSL_API int wc_wolfHAL_GenerateBlock(unsigned char* output,
                                          unsigned int sz);

wolfssl/wolfcrypt/port/wolfHAL/wolfhal_settings.h:30

• This comment says WOLFSSL_WOLFHAL "must be defined in user_settings.h", but this PR also enables it via configure.ac (AM_CFLAGS += -DWOLFSSL_WOLFHAL). Update the wording so it doesn’t incorrectly imply user_settings.h is required (it can be set by build flags too).

/* Compile time configuration for the wolfHAL port. This header holds only
 * preprocessor macros and pulls in no wolfHAL or BSP headers, so wolfSSL
 * settings.h can include it to map WC_USE_DEVID before the unmodified
 * wolfcrypt test and benchmark read it.
 *
 * WOLFSSL_WOLFHAL enables the port and must be defined in user_settings.h.
 * Which AES modes are offloaded follows the usual wolfCrypt feature gates
 * (HAVE_AES_CBC, HAVE_AESGCM, HAVE_AESCCM, HAVE_AES_ECB); the callback
 * returns CRYPTOCB_UNAVAILABLE for anything else and wolfCrypt falls back to

configure.ac:3629

• The configure.ac example uses --with-wolfhal-board=stm32wb_nucleo, but the option is documented/validated as a directory PATH containing board.h. Using a concrete path example (like the README does) would prevent confusion and reduce misconfiguration reports.

# wolfHAL hardware abstraction layer crypto-callback port.
# Include-path only: wolfHAL builds no archive (its drivers compile per-board),
# so the application compiles and links wolfHAL itself.
# Example:
#   "./configure --with-wolfhal=../wolfHAL --with-wolfhal-board=stm32wb_nucleo"
ENABLED_WOLFHAL="no"