How do I Implement the flash boot for dm6446?

Eric,

In DM6446, normally the ARM boot first (via u-boot boot-loader), followed by DSP; furthermore, to save power, the DSP is kept is reset and only taken out of reset when there is a need to run a DSP algorithm; we provide a software framework (codec engine) to take DSP out of reset and provide a communication channel between ARM and DSP.

Therefore, to answer your question, theoretically, you may be able to follow a similar process to flash an application tp DM6446 DSP side as that for C6424 DSK, but there are many good reasons why you probrably do not want to do this,

The DM6446 is a bit different since it has an ARM processor and would typically be booting U-Boot and Linux, whereas the C6424 is a DSP only device. For flashing the DM6446 you will want to use the serial boot loading utility posted on the wiki here. In particular following the steps for the serial flasher should allow you to get a U-Boot image into the flash, and from there you can use the U-Boot terminal to burn whatever else you want, such as a kernel image or filesystem.

I download a project from belo link  for ARM. I modify the code for porting an OS(uC/OS-II) on ARM.

http://wiki.davincidsp.com/index.php?title=HOWTO_Turn_off_DSP_clock_and_Power

I download the .out form file to DM6446, and I test it cound run on DM6446.
I am trying to put it to flash now, so could I use u-boot or "serial boot and flah loading" method?

By the way,will could i using DSP-BIOS link for commmunication between ARM and DSP,if I use above method (not boot form linux).

Thanks.

You could take the serial boot flasher and modify it to burn your code, I believe you would end up taking the UBL and changing it to boot your code in place of U-Boot. Unfortunately we do not have a good process on what exactly you would need to do to make this happen, we only have support collateral for booting Linux.

There is a Link source porting kit you couold use to get it working with uC/OS, I am not sure if such a port has already been done somewhere.

Is there could boot from flash by U-boot, then U-boot  load the my image file?

I think a problem about DSP, if i use above method only could programming on ARM , how could I load my code for DSP?

Yes you could boot from flash via u-boot and then have u-boot load your image (arm application, and potentially even DSP image).  This is feasible, unfortunately, as Bernie suggested, we do not have a step by step process we can provide.

I suppose you can always borrow code from DSPLINK to port it to u-boot to accomplish ARM to DSP communication.  See the following wiki article: http://tiexpressdsp.com/wiki/index.php?title=DSPLink_Overview

Thanks, It is impossible step by step process that I know. I will try it.

I don't want to develope my application on Linux environment and I don't need CODEC now, I am researching in communication between ARM and DSP, so I am using CCS IDE.

The CCS only can load ARM or DSP application  into SRAM then execute the application, I want to boot from ARM  then load DSP image into memory.

Is there have any article about  how to make DSP image that ARM application can load it to DSP memory  ?

Eric,

Unfortunately, the software architecture we have developed for this product revolves around ARM running Linux (third parties provide other OS solutions for a fee);  therefore, we do not have software we can provide for CCS enviroment.  However, there is existing source code in our DVSDK offering that does just what you are describing; our ARM Linux demos (encode, decode, encodedecode) will take a DSP image (x64P file) and load the image onto DSP via Codec Engine API (Engine_open).  Therefore, we do provide a ready to run solution for these scenerios already.

Thank for Juan Grozales's help.

TI provide linux environment to develope application on ARM side . I have no idea why CCS support dm6446? If CCS support debug  function for ARM-side or DSP-side, is that could debug both simultaneously?

CCS can be used to debug ARM or DSP side; however, CCS is Linux-agnostic; this means you can debug ARM, but not necessarily Linux.  For DSP, CCS is best-in-class tool and many DSP platforms (not only DM6446) can be debugged via CCS.