Post Go back to editing

Booting Issue?

Category: Software
Product Number: blackfin 609
Software Version: CCES2.11

Hi 

Can Anyone Help me with this Error...

I Flashed Some Application Code ,Application Code Has Some peripherals like (UART,SPI,SPORT,SMC) Flashed with SPI quad . After Completion Of Flash, Custom board was Turned Off and Turned On But booting was Not happened.

I tried to Debug that Application Code with EMULATOR  ICE -2000 ,The Process was  Reaching 70% after That CCES was Not Responding

I'm Not Using DDR2(DMC).

Parents
  • Hi Shiva,
    Can you tell us if are you including the INIT file when creating the loader file?
    Initcode is primarily used for DDR initialization and changing CGU settings. You need to include the init file to have CGU (clock frequency) configurations of the processor to run your application without any bottlenecks.
     
    Generally, the init file is used to set up the system PLL, bit rates, wait states, and the external memory controllers, you can neglect the init file while creating the ldr file if you have already included the CGU configuration in your application.
     
    To address the booting failure, can you try adding the below loader switch in the additional options of project while creating the ldr file.
    -MaxBlockSize 0xFFF0
    There might be a block which is more than 64K and that may result to boot failure. Using this switch, the loader limits the block size to a max of 0xFFF0.
     
    We would suggest you refer the ADSP-BF609 Anomaly: 16000047 (SPI master Boot Fails When Block Payload Size Exceeds 65,532 Bytes) from the below link,
    Can you please keep your board in no boot mode and try loading LDR after applying RESET. Also ensure to choose the boot mode switch to 1 and try booting with a simple LED blink code to check if the system behaves correctly?
    Have you tried running your application using the latest CCES version and have you run the ICE Test utility did it run successfully or fail at any point? If the ICE test fails, please provide us with a screenshot showing the ICE Test results?
     
    Please refer to the FAQ: How to debug a target board which boots from Flash using CrossCore Embedded Studio link below:
     
    You can refer to sections "Booting", "Boot ROM and Booting the Processor" and "Reset and Power-up" in the HRM link below for more information:
     
    Regards,
    Divya.P
Reply
  • Hi Shiva,
    Can you tell us if are you including the INIT file when creating the loader file?
    Initcode is primarily used for DDR initialization and changing CGU settings. You need to include the init file to have CGU (clock frequency) configurations of the processor to run your application without any bottlenecks.
     
    Generally, the init file is used to set up the system PLL, bit rates, wait states, and the external memory controllers, you can neglect the init file while creating the ldr file if you have already included the CGU configuration in your application.
     
    To address the booting failure, can you try adding the below loader switch in the additional options of project while creating the ldr file.
    -MaxBlockSize 0xFFF0
    There might be a block which is more than 64K and that may result to boot failure. Using this switch, the loader limits the block size to a max of 0xFFF0.
     
    We would suggest you refer the ADSP-BF609 Anomaly: 16000047 (SPI master Boot Fails When Block Payload Size Exceeds 65,532 Bytes) from the below link,
    Can you please keep your board in no boot mode and try loading LDR after applying RESET. Also ensure to choose the boot mode switch to 1 and try booting with a simple LED blink code to check if the system behaves correctly?
    Have you tried running your application using the latest CCES version and have you run the ICE Test utility did it run successfully or fail at any point? If the ICE test fails, please provide us with a screenshot showing the ICE Test results?
     
    Please refer to the FAQ: How to debug a target board which boots from Flash using CrossCore Embedded Studio link below:
     
    You can refer to sections "Booting", "Boot ROM and Booting the Processor" and "Reset and Power-up" in the HRM link below for more information:
     
    Regards,
    Divya.P
Children
  • Hi Divya

    Actually Previously It's Working Fine code was Loading ...  and I Flashed Some Code with SPI Master Boot Mode ,Created LDR file and Flashed using SPI.

    After that I Observed This Kind Of Behaver in Custom Board.

    Thank you .

  • Hi Shiva,

    There could be a possibility of application getting corrupted during flashing.

    Can you provide some more information to narrow down the issue you might be facing:

    1. Does this issue occur every time you try to Debug the application after flashing?
    2.  Did you check your board in boot mode 0 and try booting with a simple LED blink code to check if the system behaves correctly?
    3. Did you run the ICE Test utility and determine the JTAG connection every time it fails?

    Let us know if the custom boards have any issues even while debugging with a simple LED code and you are facing same issues then?


    Regards,
    Divya.P

  • Hi Divya,

    After This Iteration 

    1.  Did you check your board in boot mode 0 and try booting with a simple LED blink code to check if the system behaves correctly?
    2. Did you run the ICE Test utility and determine the JTAG connection every time it fails?

    It's working Fine.

    Thank you for your Support!

    Best Regards ,

    ShivaChary.