I am having a great deal of trouble trying to configure the ISS and RISCWATCH so that I can simulate a 476FP
I have been successful with a 405S, but this does not have the instructions I need to execute.
I cannot find anything in the documentation advising how to do this, I have tried the following
(Operating system is Linux)
1. configured the iss to run as follows
2. Configured riscwatch for the 476FP
RISCWatch/rwppc -proc 476FP
When I try to load an elf program containing the first instruction at 0x00000100, I get
load file /home/moore/powerpcISS/asmtest.be.elf
STATUS : load started for file /home/moore/powerpcISS/asmtest.be.elf
STATUS : IAR = 0x00000100
STATUS : loading program segment 0 (1576(0x628) bytes @ 0x00000000)
WARNING : no .debug or .debug_info section found
ERROR : memory not configured to write address 0x00000000
ERROR : load failed
This same elf file can be loaded and executed successfully when the target is a 405S.
The instructions contained within this program are common to the 405 and 470 instruction sets
A sample session showing an elf program loaded onto a 476 environment would be a good starting point
if one exists ?
I attach the elf file, this may provide some help in diagnosing the problem.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2013-02-22T17:49:10Z by SystemAdmin
Pinned topic ppciss, riscwatch, 476FP
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-22T17:49:10Z at 2013-02-22T17:49:10Z by SystemAdmin
SystemAdmin 110000D4XK277 PostsACCEPTED ANSWER
Re: ppciss, riscwatch, 476FP2013-02-22T17:49:10Z in response to SystemAdminHi All,
OK, I think I understand what is happening here.
There is some startup code which is inserted in a script which needs to be executed before attampting
to load my program.
It looks as though the startup code sets up some TLB information, and also runs a bit of assembler code
As long as your run this prolog code before loading your own program it works