On 01/29/2014 11:37 PM, Tom Rini wrote:
On Mon, Jan 27, 2014 at 05:28:22PM +0100, Paul Chavent wrote:
On platform with a DSP co-processor, add a command to boot an elf on it.
- Test *
This patch has been tested on an OMAP-L138 EVM with DSP code generated with TI's code generation tools 7.4.6 with the --abi=eabi option.
- Bugs *
Some elf generated with older TI's cgt have mis-aligned header sections that lead to u-boot freeze. This point can be checked with readelf (see "Start of program headers" and/or "Start of section headers") if you experience such problem.
- Discussion *
Our first question is about the interest of the u-boot community for this feature ?
For the implementation, we tried to separate platform specific code (dsp's reset and entry point) from the elf generic code (check and load elf in memory). We would like to have your opinion on this design.
This seems like the right direction to take for things. The question I have first is, are we talking about loading something into the DSP and then letting it go, or are we talking about getting a result back from the DSP in Linux? I assume the first case.
Thank you for having considered the patch.
Indeed, this is about loading something into the DSP and then letting it go without worrying about the result.
In our use case however, later, the ARM run some programs (under Linux) that will use services provided by the DSP through its L2 cache used as shared memory. Ideally, we would like to be able to soft reset the ARM without killing the DSP that will run the critical code that should survive to hight level apps failures...
I wait for your advices to improve the patch integration (I'm not sure that the "extern" declarations on top of cmd_elf.c will be integrated like that). Moreover, i wonder if we should begin to think about a more generic "boot_companion" function that would introduce a framework in order to boot companion cpu... but perhaps it's a bit premature.
Regards.
Paul Chavent.