Re: lm32 simulator configuration file question
Joel Sherrill <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <[email protected]> |
On 4/2/2015 8:41 PM, Mike Frysinger wrote: > On 02 Apr 2015 17:19, Joel Sherrill wrote: >> RTEMS has a BSP for the lm32 which runs on the simulator in gdb. >> Based on our wrapper scripts and READMEs, this is how the simulator >> is invoked in gdb: >> >> tar sim --hw-device lm32cpu \ >> --hw-device "lm32uart/reg 0x80006000 0x100" \ >> --hw-device "/lm32uart > int int0 /lm32cpu" \ >> --hw-device "lm32timer/reg 0x80002000 0x80" \ >> --hw-device "/lm32timer > int int1 /lm32cpu" \ >> --memory-region 0x08000000,0x4000000 > you can pass --hw-file to target sim too Thank you. I updated the file to this: ======================= /lm32cpu /lm32uart@0x80006000/reg 0x80006000 0x100 /lm32uart > int int0 /lm32cpu /lm32timer@0x80002000/reg 0x80002000 0x80 /lm32timer > int int1 /lm32cpu ======================= And that works with gdb using the tar sim command below. tar sim --hw-file lm32_evr.conf --memory-region 0x08000000,0x4000000 But nothing comes out from the same executable using run lm32-rtems4.11-run --hw-file lm32_evr.conf --memory-region 0x08000000,0x4000000 .hello.exe Does that make any sense to you? >> That works great. When we use lm32-rtems4.11-run, you are supposed >> to provide a hw description file matching those arguments. This is >> the file we are using: >> >> ====================== >> lm32cpu >> lm32uart/reg 0x80006000 0x100 >> /lm32uart > int int0 /lm32cpu >> lm32timer/reg 0x80002000 0x80 >> /lm32timer > int int1 /lm32cpu > put a leading / for each one missing it > -mike -- Joel Sherrill, Ph.D. Director of Research & Development [email protected] On-Line Applications Research Ask me about RTEMS: a free RTOS Huntsville AL 35805 Support Available (256) 722-9985