This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Error with shipped AM3359.cmd file??

Other Parts Discussed in Thread: AM3359, AM3352

I'm attempting to do some bare-metal development on a beaglebone (that has am AM3359 processor on it). I'm using the latest version of CCS (fresh install) on Win 7 64. Using the new project wizard I created its basic project, looking like this:

/*
* main.c
*/
void main(void) {

}

Attempting to build it produced this linker error:

'Invoking: ARM Linker'
"C:/ti/ccsv5/tools/compiler/tms470_4.9.5/bin/cl470" -mv7A8 --code_state=32 --abi=eabi -me -g --define=am3359 --define=am3352 --diag_warning=225 --display_error_number -z --stack_size=0x800 -m"franktest3.map" --heap_size=0x800 -i"C:/ti/ccsv5/tools/compiler/tms470_4.9.5/lib" -i"C:/ti/ccsv5/tools/compiler/tms470_4.9.5/include" --reread_libs --warn_sections --display_error_number --rom_model -o "franktest3.out" "./main.obj" -l"libc.a" "../AM3359.cmd"
<Linking>
"../AM3359.cmd", line 23: error #10264: M3SHDMEM memory range overlaps existing
memory range M3SHUMEM
error #10010: errors encountered during linking

Examining file AM3359.cmd, here's a snippit of what it contains:

MEMORY
{
#ifndef M3_CORE /* A8 memory map */

SRAM: o = 0x402F0400 l = 0x0000FC00 /* 64kB internal SRAM */
L3OCMC0: o = 0x40300000 l = 0x00010000 /* 64kB L3 OCMC SRAM */
M3SHUMEM: o = 0x44D80000 l = 0x00004000 /* 16kB M3 Shared Unified Code Space */
M3SHDMEM: o = 0x44D80000 l = 0x00002000 /* 8kB M3 Shared Data Memory */
DDR0: o = 0x80000000 l = 0x40000000 /* 1GB external DDR Bank 0 */

I've highlighted in red the part the linker is complaining about. You can see those two sections have been given identical starting addresses. 

Looking in the AM335x documentation, I believe the first of those two lines should actually read like this:

M3SHUMEM: o = 0x44D00000 l = 0x00004000 /* 16kB M3 Shared Unified Code Space */

Making this change allows the build to run to completion without errors.

To be honest, I'm having great trouble believing this. I feel like I'm in one of those "candid camera" shows, waiting for the camera guy to leap around the corner and yell "surprise!". How could this apparent error occur? Surely I'm not the first person on the planet to ever attempt bare-metal coding on the AM3359 in CCS.  What am I missing - what did I mess up?

Thanks.