Re: lm32 simulator configuration file question

Mike Frysinger <[email protected]>
Newsgroups gmane.comp.gdb.devel
Message-ID <20150403014149.GJ22171@vapier>
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

> 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
signature.asc (application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVHe/dAAoJEEFjO5/oN/WB9IcP+wbxh4VcUsRiPdVfb776cvyL
ZPbM6EcwcK3JsfILxhrzgO9gQ4fnVBo9RO5u2sGPbw5HNl51m6ZuE9KWivRdAYM9
IpWz02OL8JeGu0JoiD2r+pd76NISyDeDsEQ6VTHMKVtMMxPaJaVWVfJOja4T6BhA
GlxFTEVDy8QV38ycNINWIFL4SBv36b/tgHI3HTSZ4uFexvIxgdfX5j0dsjErWFfL
cXN+apOLvx0G9a/IFOJso9j5/8Tconpt2ehjD9yi+ZY5GbQmUyxRPLsEPt13jwIB
vDK9Rajn3KV+WcQSHtDhk1uzkmr0lLxH9zmbqpPb2+9js3H8XAXAO8UYYNi7Awxu
QI7alBHy8oe13uTICbWUcxla5sxHO8qC80/WT6n0tcZS0MyTqH2xyJfqTMirKKJd
/oY4Y36s5xBWx19ijCR691zF3A1p5bc+aZ+pnmBiB4utNlB8P+TXsEweoht5EKCE
BLsyJJF5J042rHaLEZKbLkhuSDEa4Sj2a/odcyExsC/AH0CJFw2T6e8i8+QN/UdB
QLW8kLbwxEhRqdhkhwhP9V2rAaM2PHEV436YwPiw0zmTh/KjIswwQ1ATI+B+McgO
rutZfCtbL5LWDWFE8y2XF1FO2uu9RgQLt2E8lXsbvGQBZVLhylEEwNj9kMf2gCQv
TNtYGxWy/a4GiTHFMrp5
=PWjh
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.