Posted on May 17, 2011 at 11:37hi be sure when using interrupts, that your core has the same clock-speed as the peripherals. see acutal datasheet v4, there are some hints about bugs in the st9 (especially the interrupts) and some workarounds. siggi
Posted on May 17, 2011 at 11:36hi smiles, another question: which mode for XRAM-access do you have? mode mc=0 (original ST9-Mode), or mode mc=1 (compare to page 143 on st9-datasheet v4). i have trouble with mode mc=0 and 32K sram. Write axess doesnt...
Posted on May 17, 2011 at 11:36Hi Smiles, you can prevent the initialization of variables (the secinfo-table). to do this put the following options in your makefile to: CFLAGS = -DNO_SEC_INFO LDFLAGS = -Xlinker --no-secinfo-table -nostartfiles (i ac...
Posted on May 17, 2011 at 11:36hi there, another facts (problem is still existing): i attached diagramms of 4 accesses to the sram: 2x write: - write AD=2, Data=1 - write AD=3, Data=2 2x read - read AD=2: >> Data=3 (fail!!!)- read AD=3: >> Data=2 (c...
Posted on May 17, 2011 at 11:36Hi, it seems to be a timing-problem with R/W. in mode=1 (and removing the inverter for AS->ALE) the sram runs perfectly. unfortunately, we can't switch the design to mode=1, cause on the same data/adressbus there's a g...
