Sign in
Search motoroladsp
Subscribe to motoroladsp
motoroladsp by Keywords
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
Ads
Discussion Groups
Discussion Groups | Freescale DSPs | move to X memory
Technical discussions about Freescale (Motorola) DSPs (including the DSP56000, DSP56300, DSP56600, 56800 DSPs).
move to X memory - Santi Corera - Oct 10 15:11:00 2002
|
Please, read this simple code: asm{ move #$0800,r0 move #$5555,y0 move y0,X:(r0) nop } I have inserted this code in a new proyect for 56807, created with codewarrior 5.0.2, but the same applies to version 4.x It is the first code in function main. When I run it under simulator, in the memory window I can see that memory is NOT written, but if I change de addres in r0 to a value under 0x0800, the value is written. It seems that the simulated DSP is the 56803 or 56805. Does somebody know wath is wrong ? Thanks. |
|
|
(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )
RE: move to X memory - Motorola DSPD News - Oct 11 16:04:00 2002
|
This simulator is DSP56800 core simulator. All of our DSP56800 processors have the same core, so I am not surprised to see results that you are describing. Since the differences in peripherals and memory configuration are not primary concern for core simulator, I think developers decided to pick DSP56F805/803 memory map (these processors were the first ones we released). Leonard N. Elevich Motorola DSPO -----Original Message----- From: Santi Corera [mailto:] Sent: Thursday, October 10, 2002 8:12 AM To: Subject: [motoroladsp] move to X memory Please, read this simple code: asm{ move #$0800,r0 move #$5555,y0 move y0,X:(r0) nop } I have inserted this code in a new proyect for 56807, created with codewarrior 5.0.2, but the same applies to version 4.x It is the first code in function main. When I run it under simulator, in the memory window I can see that memory is NOT written, but if I change de addres in r0 to a value under 0x0800, the value is written. It seems that the simulated DSP is the 56803 or 56805. Does somebody know wath is wrong ? Thanks. _____________________________________ /groups.php3 |
(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )
RE: move to X memory - Johnson, Jerry - Oct 11 17:16:00 2002
|
In the
Codewarrior Online documentation a search for the word "Simulator" provides a list of topics
that includes "Memory Map".
If that is
what is advertised, then something needs to be corrected in the online documentation, or the
simulator program, since it implies the ability to use the entire memory map including
simulation of what would be external memory in some processors.
"Figure 8.15
Simulator Memory Map" from "CodeWarrior Development Tools for Motorola DSP56800 Version
5" is the referenced Online help page.
Jerry.
|
(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )