Skip to content
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.

Sign up for GitHub

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

Jump to bottom

MicroBlaze Port #53576

Draft
wants to merge 25 commits into
base: main
Choose a base branch
from
Draft

MicroBlaze Port #53576

wants to merge 25 commits into from

Conversation

alpsayin
Copy link
Contributor

@alpsayin alpsayin commented Jan 7, 2023 •
edited
Loading

I apologise that I don't know what kind of information I should be presenting here.
So please let me know and I'll do whatever you need!

Steps to test or reproduce

compiler: mb-gcc from topic-microblaze branch of sdk-ng at
https://github.com/zephyrproject-rtos/sdk-ng/tree/topic-microblaze
zephyrproject-rtos/sdk-ng#647

Dependencies to resolve known test failures

  1. First and foremost, I'll need some help making this PR build with topic-microblaze
  2. mbedTLS: Fix little-endian Microblaze does not work when MBEDTLS_HAVE_ASM is defined mbedtls#38
  3. Zephyr: Fix Zbus Benchmark Sample is smashing the stack and is too fast #53563
  4. SDK-NG: MicroBlaze Toolchain sdk-ng#621
    1. Depends on binutils-gdb: microblaze: Invalid data offsets (pointer) after relaxation. binutils-gdb#7
    2. Other gcc/bintuils/gdb fixes: microblaze: pull in gcc/bintuils/gdb patches from meta-xilinx sdk-ng#647
    3. Picolibc support picolibc: Pull in Microblaze support sdk-ng#641
    4. microblaze: apply gcc patches from meta-xilinx repository gcc#24
    5. microblaze: apply binutils patches from meta-xilinx repository binutils-gdb#10
    6. microblaze: apply gdb patches from meta-xilinx repository binutils-gdb#11

@alpsayin alpsayin changed the title Microblaze Port MicroBlaze Port Jan 7, 2023
@alpsayin alpsayin mentioned this pull request Jan 18, 2023
Merged
@alpsayin alpsayin force-pushed the microblaze_public branch 4 times, most recently from 6f89a31 to 713b955 Compare February 20, 2023 23:16
@alpsayin alpsayin force-pushed the microblaze_public branch 3 times, most recently from 0495ed2 to 1cdf4cb Compare April 21, 2023 11:26
@github-actions
Copy link

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions bot added the Stale label Jun 21, 2023
@alpsayin
Copy link
Contributor Author

alpsayin commented Jun 23, 2023 •
edited
Loading

Still going on, rather slowly...
I've come across some issues while applying GDB patches to sdk-ng (https://github.com/zephyrproject-rtos/sdk-ng/actions/runs/5163487701/jobs/9301839276?pr=647).
Otherwise, gcc and binutils patches applied successfully (zephyrproject-rtos/sdk-ng#647 )
picolibc is also in a happy situation but I perceive it blocked on sdk-ng because picolibc CI would need at least the zephyr sdk-ng to have a correct toolchain.

p.s. the comment is mostly because I got a Stale label; thought best to give a bit of an update to advertise I haven't just left off.

@github-actions github-actions bot removed the Stale label Jun 24, 2023
@alpsayin alpsayin force-pushed the microblaze_public branch 4 times, most recently from afcd3d7 to 15c24c4 Compare July 2, 2023 20:55
@github-actions
Copy link

github-actions bot commented Sep 1, 2023

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions bot added the Stale label Sep 1, 2023
@alpsayin
Copy link
Contributor Author

alpsayin commented Sep 1, 2023

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

Go away github...

Anyways, I've finally managed to apply gdb patches that result in a build. But it turned out that gcc patches introduced an effin' broken microblaze64 toolchain which disrupted picolibc build. I've -literally- just found out how to disable m64 multilib from picolibc and proceeding with picolibc tests. Once that's done, will squash the patches and sdk-ng PR will be ready for reviews. Then I can start cleaning up picolibc patch getting it ready for PR. If I can have picolibc and sdk-ng ready in before 0.17, this patch can probably start building with sdk-0.17.

@github-actions github-actions bot removed the Stale label Sep 2, 2023
@github-actions GitHub Actions
Copy link

github-actions bot commented Dec 1, 2023

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions bot added the Stale label Dec 1, 2023
@alpsayin
Copy link
Contributor Author

alpsayin commented Dec 1, 2023

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

Go away github...

@github-actions github-actions bot removed the Stale label Dec 2, 2023
@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 1, 2024

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions bot added the Stale label Jul 30, 2024
@alpsayin
arch: microblaze: Early Boot Sequence
8c73945 
Internal references: FWRIVERHD-4969

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: Interrupt and Exception Handling
0f34a08 
Internal references: FWRIVERHD-4971

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: Support files (Minimal Board Support Package)
3c67b1b 
Internal references: FWRIVERHD-4980,FWRIVERHD-4990

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: Thread Context Switching
a223896 
Internal references: FWRIVERHD-4973

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
drivers: interrupt_controller: Xilinx AXI Interrupt Controller Driver
2b150b3 
Internal references: FWRIVERHD-4976,FWRIVERHD-4981

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
Copy link
Contributor Author

another comment saying that I would like to have the label removed

p.s. man I really stretched this project didn't I...

@kartben kartben removed the Stale label Jul 30, 2024
@alpsayin
drivers: timer: Xilinx AXI Timer Systick Driver
844b865 
Internal references: FWRIVERHD-4976/FWRIVERHD-4982

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: Thread Creation and Termination
b72e339 
Internal references: FWRIVERHD-4973

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: CPU Idling/Power Management
9969562 
Internal references: FWRIVERHD-4978

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: Fault Management
829df31 
Internal references: FWRIVERHD-4979

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: IRQ Offload implementation (emulated)
4be73eb 
Internal references: FWRIVERHD-5108

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: Cache API implementation
1f4dc80 
Internal references: FWRIVERHD-4554

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: Weak sys_arch_reboot implementation
6be0d41 
Internal references: FWRIVERHD-4554

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: Toolchain: introduce MicroBlaze to build system
042c51d 
Internal references: FWRIVERHD-4980,FWRIVERHD-4991

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: Linker: add linker script and define output format
fdbfc63 
Internal references: FWRIVERHD-4980,FWRIVERHD-4989

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: add MicroBlaze arch headers
a6d6963 
Internal references: FWRIVERHD-4554

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
include: arch: add MicroBlaze to cpu.h and arch_inlines.h
1285554 
Internal references: FWRIVERHD-4554

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
debug: thread_info: point MicroBlaze stack pointer to r1
e8fdca5 
Internal references: FWRIVERHD-4554

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: add MicroBlaze to arch/KConfig
1c1f8ba 
Internal references: FWRIVERHD-4554

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
arch: microblaze: add CMake files for building arch
c00668a 
Internal references: FWRIVERHD-4554

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
dts: bindings: cpu: add MicroBlaze cpu binding
0ba9b23 
Internal references: FWRIVERHD-4554, FWRIVERHD-5063

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
soc: microblaze: add demo SoC with timer, interrupt_controller and uart
b4aba6f 
Internal references: FWRIVERHD-5063

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
boards: microblaze: add QEMU demo board with qemu hw-dtb
0a7a5ba 
Internal references: FWRIVERHD-5063

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
script: logging/dictionary: add arch MicroBlaze
24c331d 
Internal references: FWRIVERHD-5201

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
tests: kernel: interrupt: MicroBlaze trigger_irq implementation (emul…
69da9dd 
…ated)

Internal references: FWRIVERHD-4554

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
@alpsayin
tests: microblaze: test specific configuration additions for MicroBlaze
b49b9dd 
Internal references: FWRIVERHD-5201

Signed-off-by: Alp Sayin <alpsayin@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dcpleung dcpleung Awaiting requested review from dcpleung dcpleung will be requested when the pull request is marked ready for review dcpleung is a code owner

@nashif nashif Awaiting requested review from nashif nashif will be requested when the pull request is marked ready for review nashif is a code owner

At least 2 approving reviews are required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@alpsayin @kartben @stephanosio