[threadx-dev] ThreadX/netXDuo on ARM Cortex R5 on Xilinx ZCU104 Stack is

[Rudolf Weber <rwissag@xxxxxx>]

Hello,

I tried to adapt the Xilinx Ethernet-Driver to threadX/netXduo for the ARM Cortex-R5 RPU on a Xilinx Board ZCU104 (MPSoC Ultrascale+).
When I enable the Interrupts, the Stack get crashed.

ChatGPT says, that the Interrupt Service routine must be registered with the Boardsupport-Package from Xilinx.
Is that right ? I wonder.

A breakpoint on the ethernet-ISR shows, that the ISR was not called.

In the linker script is a section named '.vectors'.
objdump doesn't show this section.

The changing of the linkerscript:
vectors : {
   . = 0x000000;
   KEEP(./src/reset.o(.text))
} > psu_r5_0_atcm_MEM_0 

leads to the allocating of the section:

armr5-none-eabi-objdump -j .vectors -h threadX_netXduo_udpserver.elf

threadX_netXduo_udpserver.elf:     file format elf32-littlearm

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .vectors      00000040  00000000  00000000  00001000  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE 

The content looks strange:
bash-5.2$ armr5-none-eabi-objdump -j .vectors -s threadX_netXduo_udpserver.elf
threadX_netXduo_udpserver.elf:     file format elf32-littlearm

Contents of section .vectors:
 0000 18f09fe5 18f09fe5 18f09fe5 18f09fe5  ................
 0010 18f09fe5 18f09fe5 18f09fe5 18f09fe5  ................
 0020 00001000 f4001000 f8001000 fc001000  ................
 0030 00011000 04011000 08011000 1c011000  ................ 

I expected a 32bit function pointer, but
* 18f09fe5 appears often
* there is no 18f09fe5 in the linker-map

The behavior of stack crashing remains :-(

What must be done, that the interrupts are working correctly ?

Greetings from Ravensburg Gemany
Rudolf Weber