Thanks. I am just worried about reproducibility or the BSP and test results combined with licensing and redistribution of the TI support code. As long as everyone is comfortable with that, I am as well.
On 8/14/2014 4:04 AM, Pavel Pisa wrote: > Hello Joel, > > On Thursday 14 of August 2014 00:40:49 Joel Sherrill wrote: >> On 8/13/2014 2:48 PM, Premysl Houdek wrote: >>> --- /dev/null >>> +++ b/c/src/lib/libbsp/arm/tms570/README >>> @@ -0,0 +1,64 @@ >>> +Development Board: TMS570LS31x Hercules Development Kit from TI > ... >>> +Execution >>> + >>> + There is not used any generic bootloader. Initial complex CPU and >>> peripherals + initialization and self test are not implemented and >>> included in RTEMS BSP + right now. For testing and debuging purposes is >>> used simple Ti's HalCoGen + generated application to setup board and >>> then download RTEMS image over + OpenOCD to internal EEC SRAM or >>> external SDRAM. >> This is rough from an English viewpoint. How about: >> >> Currently, a bootloader is not used. For test and debug purposes, TI's >> HalCoGen generated >> application is used to set up the board and then the RTEMS application >> image is loaded >> using OpenOCD to internal EEC SRAM or external DRAM. The following >> features are >> not implemented in the BSP: >> >> + Initial complex CPU and peripheral initialization >> + Self-test >> >> Can you be more specific about what that first bullet covers? >> >> Is the generated setup code available? What's the license on it? > The generated setup is available, see link below > >>> + Setup application code is available there: >>> + https://github.com/hornmich/tms570ls3137-hdk-sdram >>> + >>> +Howto setup TMDS570LS31HDK? >>> + >>> + o Unpack board. >>> + o Verify that demo application runs. >>> + o Upload bootloader specified above >>> + o write BSP aplication either to sdram or intram and jump to RTEMS >>> start code >> application not aplication >> Internal RAM? > Yes, thanks for checking, English is neither Premek nor my > specialty and Pemek. > > There would be happy even to provide build binary to everybody who cares. > > But generally the hardware needs more work to be done. > Unfortuantelly, flashing to the MCU is quite complicated due > un-documented algorithm. We have used Ti tools to Flash setup > code. But we know other working solution, it is possible to > setup MCU over JTAG and the download flasher code into internal > RAM. The library with flash algorithm is available from Ti > in binary form for Cortex-R4F. So our plan is to have small > loader to allow flash application over CAN or ETHERNET. > > But it is still longer term goal. > > Best wishes, > > Pavel -- Joel Sherrill, Ph.D. Director of Research & Development joel.sherr...@oarcorp.com On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985 _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
