XVF3615 SPI slave boot

The XVF3615 boot process is the same as described in the XVF3610 documentation.

The XVF3615 can be booted from an attached QSPI flash device or configured as an SPI slave device allowing the image to be transferred directly from the host processor. This second option allows the host system to store multiple firmware images with different language models to allow dynamic changes of language models while the host is operational.

The available models are stored in the directory data-partiion/ww_models in the release package.

If you are booting from flash, the model is updated in the data partition. The path to the WW model is in the file json config file in ‘data-partition’. After updating the path, the data partition binary must be regenerated and it can be flashed to the device.

If you are booting via SPI boot, the model must be embedded in the boot binary.

The model is updated by using the script update_spi_boot_ww_model.py stored in the host directory. The command to update the model in the SPI bootable binary is:

python update_spi_boot_ww_model.py original_bin_file ww_model_bin_file modified_bin_file

where original_bin_file is the binary with the model to update (or without a model), ww_model_bin_file is the model to use in the new binary and modified_bin_file is the name of the new binary with the updated model.

To restart the device to load a new model or to recover from error conditions the host controller should be connected to and assert the RST_N input signal to the XVF3615.