search

bao-project / bao-demos

A guide on how to build and use a set of Bao guest configurations for various platforms
Other
33 stars 37 forks source link

no handler for abort ec = 0x20 #8

Closed mg199 closed 1 year ago

mg199 commented 1 year ago

hello, After I write a SPI driver in the code, but while I run fatload, hypervisor report a error.

BAO ERROR: no handler for abort ec = 0x20

Is there anything wrong? or some where need to be configuration?

mg199 commented 1 year ago

it's solved

a-daydream commented 1 year ago

hello, I encounter this problem while running bare-metal demo. Can you show me your solution to this problem?

mg199 commented 1 year ago

Hello,beacuse I migrate SPI Driver to freertos over baohypervisor, It has some code error. maybe you can share your project details.

a-daydream commented 1 year ago

Hello,beacuse I migrate SPI Driver to freertos over baohypervisor, It has some code error. maybe you can share your project details.

I tried to running bare-metal demo Single-guest Baremetal , then encountered that problem. environment ： PLATFORM is qemu-aarch64-virt, and DEMO= baremetal.

I found it may have some problem in memory mapping.When I disable mmu in el1, there is a new problem BAO ERROR: no emulation handler for abort(0x9000030 at 0xd84).

I want to know where the baremetal.bin is load in uboot and the reason for my probleam. Thanks!

mg199 commented 1 year ago

Hello,beacuse I migrate SPI Driver to freertos over baohypervisor, It has some code error. maybe you can share your project details.

I tried to running bare-metal demo Single-guest Baremetal , then encountered that problem. environment ： PLATFORM is qemu-aarch64-virt, and DEMO= baremetal.

I found it may have some problem in memory mapping.When I disable mmu in el1, there is a new problem BAO ERROR: no emulation handler for abort(0x9000030 at 0xd84).

I want to know where the baremetal.bin is load in uboot and the reason for my probleam. Thanks!

I also encounter this problem before, I config the memory mapping cover the abort address this problem is solved. my environment is raspberry 4B, I'm not try in qemu. I think you can open a issue to ask josecm for help