Driver for ADZS-ICE-1000

trying to write to or read from a 533 Blackfin using the ADZS-ICE-1000,   

just using the CrossCore command line utility cldp.exe switches.

It reports  "Error no -driver option" so I guess I need a .dxe for it, where do I get it ?

Top Replies

    •  Analog Employees 
    Jul 24, 2020 +1 verified
    533 B

    Hi,

    To flash a loader image to target using CLDP, flash driver is needed.

    Flash driver will be located in the below BSP location.
    C:\Analog Devices\ADSP-BF533_EZKIT-Rel1.0.1\BF533_EZ…

  • +1
    •  Analog Employees 
    on Jul 24, 2020 2:06 PM
    533 B

    Hi,

    To flash a loader image to target using CLDP, flash driver is needed.

    Flash driver will be located in the below BSP location.
    C:\Analog Devices\ADSP-BF533_EZKIT-Rel1.0.1\BF533_EZ-Kit_Lite\Blackfin\Examples\Device_Programmer\parallel

    You can download and install the ADSP-Bf533 BSP from the below link.
    download.analog.com/.../ADI_ADSP-BF533_EZKIT-Rel1.0.1.exe

    You can refer the below linked FAQ on flashing loader image into target.
    FAQ: How do I program flash on my target board using CrossCore Embedded Studio?
    ez.analog.com/.../faq-how-do-i-program-flash-on-my-target-board-using-crosscore-embedded-studio

    If you are using ADSP-BF533 custom board and using any other flash part other than the one available in ADSP-BF533 EZ-KIT, you have to modify the flash driver according to your flash part.

    We would recommend that you to take one of our current drivers (bf533_psd4256g6v_dpia.dxe) as a base for creating a driver, which will be compatible with your flash part.

    The flash drivers we ship with our tools are specific to our EZ-Kit boards. For example, the bf533_psd4256g6v_dpia.dxe driver is specific to the BF533 EZ-KIT.

    We provide documentation for the Device Programmer API, which describes the commands the Flash Programmer Drivers require to perform the Flash accesses. Following the API, it's relatively simple to port an existing Flash Programmer Driver to match your specific flash part.

    When modifying a driver we would recommend referring to both the custom flash part data sheet and the data sheet for the original device when doing so, so that you can verify elements such as number and size of sectors, reset commands, Manufacturer and Device codes, then see how these differ in the data sheet for your custom flash device. The examples/drivers are well documented/commented so you should be able to determine where changes are required to suit your target.

    Following the API, it's relatively simple to port an existing Flash Programmer Driver to match your specific flash part. This documentation is available at
    Help > CrossCore® Embedded Studio <version> Integrated Development Environment > Working with Bootable and Non-bootable Files > Device Programmer > Custom Device Drivers

    We are aware of many customers who have successfully modified our flash drivers to suit different flash parts.

    Regards,
    Nishanthi.V