This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
snippets:setspeed [2013/05/07 16:50] – created ab | snippets:setspeed [2017/11/07 22:26] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Set speed ====== | + | ====== Set Speed ====== |
+ | ** - preleminary - not tested- ** \\ | ||
+ | The setspeed VI can be used to change the clock speed in order to minimize power consumption.\\ | ||
+ | \\ | ||
+ | ** Notes about debugging: **\\ | ||
+ | * Debugging gets complicated after changing the clock speed. Thus its recommended to start working on clock changes only at the very end of a development cycle | ||
+ | * After changing the clock speed the emulator looses connection to the target. For this reason it's important **never to change the clock speed directly after power up**. Always program your application in such a way that the first clock change occurs **at least 5 seconds after power up**! \\ (After power up the processor runs with default settings, which allows to connect the emulator to the target during this 5 seconds) | ||
+ | * The program should not be executed as a *.DXE file, it's strongly recommended to always create a *.LDR file | ||
- | + | \\ | |
- | sdfsdf | + | \\ |
+ | ** No Boot **\\ | ||
+ | In case the VDSP session cannot be connected because a flashed application changes the clock settings, follow this instructions: | ||
+ | [[no_boot]] |