Thank a lot Peter and Philippe
On 9/19/21 20:46, Philippe Mathieu-Daudé wrote:
> In the "infinite loop exception" case, '-d int' might be sufficient,
> before using 'exec/cpu', since you'll see the exception raise over
> and over.
I tried -d int and see that a lot of exceptions are rising in idle
On 9/19/21 20:06, Peter Maydell wrote:
> On Sat, 18 Sept 2021 at 09:12, Ali Vatankhah wrote:
>> then to check what instructions are executing I run this command:
>>
>> qemu-system-ppc64 -nographic -M ppce500 -cpu e5500 -kernel uImage
>> -singlestep -d in_asm -D target_asm.log
>>
>> Obviously this
On Sat, 18 Sept 2021 at 09:12, Ali Vatankhah wrote:
> then to check what instructions are executing I run this command:
>
> qemu-system-ppc64 -nographic -M ppce500 -cpu e5500 -kernel uImage -singlestep
> -d in_asm -D target_asm.log
>
> Obviously this results in a Kernel panic, but the point is th
Hi Philippe, Thank for your email
I investigated your advice,
first checked the CPU's programmer's reference manual and it has wait for
interrupt instruction.
then to check what instructions are executing I run this command:
qemu-system-ppc64 -nographic -M ppce500 -cpu e5500 -kernel uImage
-sin
On 9/15/21 9:46 AM, Ali Vatankhah wrote:
> Dear qemu developers
> I built an image for e5500 cpu with yocto and run with qemu ppce500 machine:
> qemu-system-ppc64 -nographic -M ppce500 -cpu e5500 -kernel uImage
> -initrd core-image-minimal.rootfs.ext2.gz -append 'root=/dev/ram rw'
> It works well,
