Failed to generate xparameters when sharred interrupt source accros multiple IP's
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Failed to generate xparameters.
The block design contains 4 uart_lite IP's that share one interrupt with a util_reduced_logic IP(in 'or' configuration), all the other interrupt sources have different drivers.
I think this error has something to do with assigning interrupts ID's. The interrupt numbers are incremented for each uart. Since the PS has only 16 interrupts the assigning fails on interrupt 17.
Error:
(XSDB Server)ERROR: [Hsi 55-1545] Problem running tcl command ::sw_scugic_v3_10::generate : expected integer but got ""
while executing
"format "#define XPAR_FABRIC_%s_%s_INTR %d$uSuffix" [string toupper $ip_name] [string toupper $port_name] $port_intr_id"
("foreach" body line 86)
invoked from within
"foreach periph $periphs {
# get the gic mode information
set scugic_mode [common::get_property CONFIG.C_IRQ_F2P_MODE $periph]
..."
(procedure "xdefine_gic_params" line 30)
invoked from within
"xdefine_gic_params $drv_handle"
(procedure "::sw_scugic_v3_10::generate" line 10)
invoked from within
"::sw_scugic_v3_10::generate ps7_scugic_0"
ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ::sw_scugic_v3_10::generate procedure and its xdefine_gic_params call shown in the error, especially the format statement that receives an empty interrupt value. Reproduce the design with four uart_lite IPs sharing one interrupt through util_reduced_logic and verify that xparameters generation completes without assigning invalid interrupt IDs.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100