AnsweredAssumed Answered

custom board support files

Question asked by hugejeans on Aug 17, 2011
Latest reply on Jun 6, 2012 by CraigG

Hi,

 

We have a custom board support file created to be used with a BF537. It works fine for most setups but on mine I keep getting the following error:

 

Error:

 

[Error xml1018] [emulator] Custom board file failed validation against XSD schema rules.
        Custom file "C:\Sandbox\Halo\CameraBoard\Source\bf537\Config\TitanIILogicBoardSetting3s_3.xml"
        Line number 7, positioned at column 39:     file="TitanIILogicBoardSettings.xml">
        Reason: The system cannot find the path specified.
   
    [Error xml1002] [emulator] Illegal custom board file "C:\Sandbox\Halo\CameraBoard\Source\bf537\Config\TitanIILogicBoardSetting3s_3.xml". Reverting to the known good base XML processor definition "C:\Program Files (x86)\Analog Devices\VisualDSP 5.0\system\ArchDef\ADSP-BF537-proc.xml".

 

Custom board support file:

 

<?xml version="1.0" standalone="yes"?>

 

<custom-visualdsp-proc-xml
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="\Program Files\Analog Devices\VisualDSP5.0\System\ArchDef\ADSP-custom-board.xsd"
    processor-family="BLACKFIN"
    file="TitanIILogicBoardSettings.xml">

 

<!-- ************************************************************************* -->
<!-- ******* TitanIILogicBoardSettings.xml                                                  -->
<!-- ************************************************************************* -->

 

<custom-register-reset-definitions>

 

    <register name="EBIU_SDRRC" reset-value="0x0258" core="Common" />
    <register name="EBIU_SDBCTL" reset-value="0x0013" core="Common" />
    <register name="EBIU_SDGCTL" reset-value="0x8091994B" core="Common" />
    <register name="PORTHIO" reset-value="0x001F" core="Common" />

 

</custom-register-reset-definitions>
</custom-visualdsp-proc-xml>

 

This setup has worked for everyone else. Has anyone seen something like this before or a suggestion on how to fix this error? I'm currently working around it by simply editing the default file under:

 

"C:\Program Files\Analog Devices\VisualDSP 5.0\system\ArchDef\ADSP-BF537-proc.xml"

Outcomes