56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

Hi, I have a few newbie questions. I am using the SDK on the 56F807 evaluation module. If I create an Flash_Application from SDK stationary, the default project works fine. However: - If I look at the code size, the dspfunc.lib, bsp.lib, and msl c 56800.lib are larger than the availabe on chip flash/ram. It seems that I shouldn't be able to use the SDK in flash? -If I add a printf statement to the default main.c, the debugger stops at the printf when run. If I step over the statement, the debugger jumps to configUnhandledInterruptISR. Why don't I my printf in the console window? Thanks so much for any help. Aaron Edsinger MIT AI Lab

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

Hi Aaron, Comments below. Best regards, Fabio -----Original Message----- From: aaronedsinger [mailto:] Sent: sábado, 19 de julho de 2003 14:19 To: Subject: [motoroladsp] using SDK in 56F807 Hi, I have a few newbie questions. I am using the SDK on the 56F807 evaluation module. If I create an Flash_Application from SDK stationary, the default project works fine. However: - If I look at the code size, the dspfunc.lib, bsp.lib, and msl c 56800.lib are larger than the availabe on chip flash/ram. It seems that I shouldn't be able to use the SDK in flash? >>You can use SDK projects to run from Flash. The size showed in the CodeWarrior window is the total size of these libraries. However, the linker removes all unused code (deadstripping) from the SDK libraries. -If I add a printf statement to the default main.c, the debugger stops at the printf when run. If I step over the statement, the debugger jumps to configUnhandledInterruptISR. Why don't I my printf in the console window? >> printf consumes a large block of RAM, so when running from internal memory you will probably need to use another method of displaying, like SCI. Thanks so much for any help. Aaron Edsinger MIT AI Lab _____________________________________ /groups.php3

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