Finally, the driver must be added to the ChorusOS operating system. This can be done by either:
Including the new driver in the ChorusOS operating system image, or
Dynamically adding the driver to the operating system
To include the new driver in the ChorusOS operating system image you will need to add the new driver's definition to the BSP target.xml file, as follows:
<definition name='zl345y'> <type name='File' /> <value field='path'> <vstring>${MYDRV_DIR}/bin/drv/keybrd/zl345y/D_zl345y.r</vstring> </value> <value field='bank'><ref name='sys_bank' /></value> <value field='binary'><ref name='driver_model' /></value> </definition>
Also, a reference to the new driver will need be to be made in the BSP FileList:
<definition name='BSP_files'> <description>system image BSP files</description> <type name='FileList' /> .... <value index='size'><ref name='zl345y' /></value> .... </definition>
Alternatively, to add the driver dynamically, after the system image has been created, the arun command should be used to run the new driver.