AD535 | BIOS | Booting | Bootloader | C621 | C6211 | C6415 | C671 | C6711 | C6711DSK | C6713 | CCS | Chassaing | COFF | DAT | DM64 | DM642 | DMA | DSK671 | DSK6711 | EDM | EDMA | EMIF | Emulator | EVM | EVM620 | FFT | FIR | GPIO | Halting | HPI | HWI | IDK | JTAG | LDB | LDH | LDW | Linker | LMS | LOG_printf | Matlab | McBSP | MEM_alloc | MIPS | PCI | PCM3003 | Pipeline | Profiling | QDM | Reset | ROM | RTDX | Sampling | SDRAM | Stack | TEB | THS1206 | TMS320C621 | TMS320C6416 | TMS320C6711 | TMS320C6713 | UART | Vector Table | XBUS | XDS560

I'm trying to parse the COFF V2 .out file produced by Code Composer Studio 2.0 for the C6711. This is related to writing my own bootloading code. The .cinit section is different from the rest because size and address data for each initialized variable was included along with the actual initial values, at least for Version 0 of COFF. In COFF V0 the sizes in the headers were in words, but in V2 they're in bytes, according to the chapters in TI's spru035.pdf and spru186.pdf. Is this true for .cinit also? Can anyone point me toward a detailed description of .cinit for COFF V2, also including the "holes" the compiler seems to put in it for some sort of alignment reason? Thanks, Dan Eyer Mayflower Communications

(You need to be a member of c6x -- send a blank email to c6x-subscribe@yahoogroups.com )