-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Xtensa architecture #8
Comments
I tried to implement this about a year ago but gave up because the compiler distributed via taiki-e/portable-atomic#86 (comment)
If things haven't changed (and we need to use If it is OpenOCD semihosting (that using |
When implementing this on my end, perhaps the hardest part is setting up a proper test environment. Looking at the working branch at the time (which unfortunately contains code that cannot be made public), it appears that I tried to work around the above problem by calling SIMCALL via C FFI, but failed to properly set up the QEMU and startup code. (The implementation on the semihosting side or the testing side or both was incorrect.) Perhaps it will not be possible to implement this on my end in the near term unless you or someone else can provide a proper QEMU setup to test, or test the implementation in some other way. Therefore, marking this as help-wanted. |
Things havent change afaik.
I think this is the case, in our end, the As @MabezDev suggested, looks Ike what we need to do to get it working is having a https://github.com/espressif/esp-idf/blob/master/components/xtensa/include/xtensa/semihosting.h version of https://github.com/taiki-e/semihosting/blob/main/src/sys/arm_compat/syscall/riscv.rs |
First, I would like to thank you for your amazing work! We recently started working on HIL for esp-hal based on
embedded-test
which depends onsemihosting
.As you may know, some ESP chips are Xtensa based, so I wanted to ask if you have any plans to add support for it.
Semihosting on Xtensa
I haven't found any documentation on the Xtensa semihosting standard, so I asked some of our colleagues, here is the information that I gathered:
The text was updated successfully, but these errors were encountered: