There is no single __delay_cycles() function; the compiler generates inline code adjusted for the cycle count. This is why we're asking you to put a single invocation of __delay_cycles() into a separate function. Yes, you are right. The generation of code is different for different numbers of cycles. I checked, that the code generated is similar in the range: 1000001 RAM /* Global & static vars */ .data : {} > RAM /* Global & static vars */ .TI.noinit : {} > RAM /* For #pragma noinit */ .sysmem : {} > RAM /* Dynamic memory allocation area */ .stack : {} > RAM (HIGH) /* Software system stack */ #ifndef __LARGE_DATA_MODEL__ .text : {}>> FLASH /* Code */ #else .text : {}>> FLASH2 | FLASH /* Code */ #endif .text:_isr : {} > FLASH /* ISR Code space */ .cinit : {} > FLASH /* Initialization tables */ #ifndef __LARGE_DATA_MODEL__ .const : {} > FLASH /* Constant data */ #else .const : {} > FLASH | FLASH2 /* Constant data */ #endif .cio : {} > RAM /* C I/O Buffer */ .pinit : {} > FLASH /* C++ Constructor tables */ .init_array : {} > FLASH /* C++ Constructor tables */ .mspabi.exidx : {} > FLASH /* C++ Constructor tables */ .mspabi.extab : {} > FLASH /* C++ Constructor tables */ .infoA : {} > INFOA /* MSP430 INFO FLASH Memory segments */ .infoB : {} > INFOB .infoC : {} > INFOC .infoD : {} > INFOD /* MSP430 Interrupt vectors */ .int00 : {} > INT00 .int01 : {} > INT01 .int02 : {} > INT02 [...] } /****************************************************************************/ /* Include peripherals memory map */ /****************************************************************************/ -l msp430f5529.cmd All cut outs are marked with "[...]".
↧