Part Number: TMS320F2811 Preface: I'm a hardware engineer, not understanding programming or microcontrollers. I'm now managing the development of automatic production test equipment. We have developed (with outside support) an automatic test setup for…
Part Number: TMS320F2811 Other Parts Discussed in Thread: UNIFLASH Recently our JTAG programmer broke so I am trying to get a new one set up and configured. I have an XDS510 Plus emulator, and just installed Uniflash v6.3.
Uniflash will let me select…
Part Number: TMS320F2811 On the TMS320F2811, can I use the linker file to specify placing object files in non-contiguous areas of memory and have the program run correctly? For example, can I have C language code located in M0, L0, and H0 areas of SARAM…
Part Number: TMS320F2811 Other Parts Discussed in Thread: TLV320AIC3107 , Hi ,
We need to connect Audio codec TLV320AIC3107 with TMS320F2811 through I2S interface . Let me know how to configure TMS320F2811 McBSP port to compliant with standard I2S waveforms…
Part Number: TMS320F2811 We are facing programming error the TMS320F2811PBKA part with the body marking of CG-98A ( image is attached)
1) we replaced the part with new material having date code-CG-99A & programming got passed.
2)when passed (OK board…
Part Number: TMS320F2811 Tool/software: Code Composer Studio I am trying to get my emulator JTAGjet - C2000F to work in code composer. I have the latest driver but am not able to run and debug from code composer.
To see the assembly code generated by the compiler, use the command line option --src_interlist . To create an assembler listing file, use the option --asm_listing . Please search for these options in the C28x compiler manual . To learn how to set these…
Cai,
I have not heard from you for a while and presume you have been able to resolve your issue. If that is not the case, please provide the part number information I asked for and we can take it from there.
Hello Gerhard,
Assuming that the memory on the target is read accessible (not locked, etc), you can attach the debugger and dump the contents to a binary or COFF (*.out) file. Note that the COFF (*.out) file that is saved on the host will be different…
