Post Go back to editing

BF702 BF706 differences

Category: Hardware
Product Number: BF702

I'm using a BF702 with code developed on a BF706. I've been careful to ensure I don't run into L2 memory problems, but it still gives some incorrect results to calculations that use L2. I am also unable to program the boot code into the flash. If I write this:

cldp -proc ADSP-BF706 -emu 1000 -driver bf706_w25q32bv_dpia.dxe -cmd prog -file myprogram.ldr

It programs but does nothing on reset. If instead I write this:

cldp -proc ADSP-BF702 -emu 1000 -driver bf706_w25q32bv_dpia.dxe -cmd prog -file myprogram.ldr

It just hangs.

Appreciate some help here.

  • Hi,

    Can you please confirm that flash used for BF702 is same as ADSP-BF706. "bf706_w25q32bv_dpia.dxe" is driver file which is used to program the loader file in Winbond W25Q32BC 32 Mb flash.
    If flash is same, please follow the below steps:
    1. Please open the "Device_programmer" example from the below path C:\Analog Devices\ADSP-BF706_EZ-KIT_Mini-Rel1.1.0\BF706_EZ-Kit_MINI\Blackfin\Examples\Device_programmer
    2. Change the processor to BF702
    3. Build the project
    4. Now, use the updated driver file available in debug folder to program using CLDP

    Anand Selvaraj.

  • Hi Anand,

    Yes, it's the same flash. I opened the "Device_programmer" example and from Project > Properties > C/C++ Build > Settings I selected the Processor settings tab and selected ADSP-BF702.

    Then did a build and used the new bf706_w25q32bv_dpia.dxe file.

    Still no luck. I have tried both:

    cldp -proc ADSP-BF706 -emu 1000 -driver bf706_w25q32bv_dpia.dxe -cmd prog -file myprogram.ldr


    cldp -proc ADSP-BF702 -emu 1000 -driver bf706_w25q32bv_dpia.dxe -cmd prog -file myprogram.ldr

    Is there anything else I am doing wrong?


  • Hi,

    We are aware of many customers who have successfully modified our flash drivers to suit different processors.
    Please try the below format:
    cldp -proc ADSP-BF706 -emu 1000 -driver bf706_w25q32bv_dpia.dxe -cmd prog -erase all -format hex -file myprogram.ldr -cmd compare -format hex -file myprogram.ldr

    -erase all : Erases all sectors in device memory -format hex: loader file created in hex format.

    Can you please share command window after using above cldp commands. Also, we recommend to flash simple LED application.

    Anand Selvaraj.

  • Thanks Anand. Yep I tried all of these commands. I have also probed the pins on the flash. The data are being read, and the -cmd compare confirms the data stored to the flash are correct. But when I reset the processor, it does not read anything back. It may be a connection problem with the boot pins. Thanks for your help anyway.

  • Hi,

    You can follow the below steps to debug further:

    1) Can you please confirm that all clock domain are under specification as mentioned in the datasheet "Table 17. Core and System Clock Operating Conditions" (Page No: 50 / 114)?
    2) Make sure that the Clock and Reset Timing (Page No: 58 / 114) and Power-Up Reset Timing (Page No: 59/ 104) specifications are mentioned in the datasheet is followed.
    3)Are you able to connect to DND mode, please refer the below link for more details:

    Anand Selvaraj.

  • Thanks Anand. we are following all procedures as specified. For background, we already produce a board that uses the BF706; this boots fine. If we use the same board with a BF702, it won't boot. We can run it from CCES no problem, and cldp will program the flash because we can monitor the signals to the flash.

    According to my understanding, if the boot pins are set to boot from flash with the DSP as master, after reset the processor should attempt to read something from flash even if it is empty (for example, momentarily enabling the flash). However, it does nothing. We will check the circuit again to make sure there are no bad connections.

  • Hi Anand. We found the problem. Dry solder joint on one of the boot mode pins. Sorry to waste your time.

  • Hi,

    Glad to know that issue got resolved.