Hello, I was having similar problems, trying to run code from the external RAM. We are using the IAR environment, with a Macraigor clone (chamelion from amontec). But the solution should be simular for you. The solution I found was setting the PINSEL2 register to the correct value for activating the address and data bus lines. The value I used for the phytec board is 0x 0FE1 69EC (at address 0x E002 C014). Then you have to set the BCFG1 register to 0x 2000 0400 (at address 0x FFE0 0004), this to get the correct access to the RAM (zero waitstates , ...). In IAR you can do this in a macro file, so every time you upload the executable, the registers are set to these values. Otherwise there is no way of getting the executable in external RAM. I suppose there is a simular way of working for KEIL. If not, you can use the 30 day trial version of IAR (www.iar.com) The same has to be done for the external periferals (eg when using the on board ethernet controller), but for the corresponding CS register. Hope this helps you, Didier --- In lpc2000@yahoogroups.com, "wunny83" <wunny83@y...> wrote: > > Hi im new at this but im having trouble storing data to the adress > 0x81000000, while my program will run fine if internal memory is > used. > > Im using keil and uvision ulink with the gcc compiler. > > I have set up the text start 0x80000000 and data start 0x81000000 in > the linker while my top stack is 0x81010000 while I have tried many > others because i dont know the exact value of the top stack for > external memory; my linker script file is also se up properly. > I have also tried different memmap settings 0x02 and 0x03. > > When debugging using ulink jtag, the variable that are initailized > do not get values and eventually the pc will go to 0x00-0x14 range. > > Everything works fine when using internal mem with data start > 0x40000000 and top stack 0x40004000 > > Thanks in advance > > Wun
Message
Re: cant seem to use external sdram on phytec 2294
2005-02-07 by didier_edna
Attachments
- No local attachments were found for this message.