2 replies to this topic

[mmw119]

Hi,
I am following Tutorial 2: Complex FIR Filtering in the "Xilinx Platform Support Package,
including MicroBlaze" help. But when I go to the step "Importing the Application Software"
and select menu Software -> Generate Linker Script..., after I choose ComplexFIR as the
software application, the error below just appears:

ERROR:MDT - dcm_module_0 (dcm_module) - can not find channel named "stdout"
while executing
"puts "WARNING ***********************************************************************""
(procedure "::hw_dcm_module_v1_00_c::check_iplevel_settings" line 116)
invoked from within
"::hw_dcm_module_v1_00_c::check_iplevel_settings 550254872"
ERROR:MDT - dcm_module_0 (dcm_module) - can not find channel named "stdout"
while executing
"puts "WARNING ***********************************************************************""
(procedure "::hw_dcm_module_v1_00_c::check_iplevel_settings" line 116)
invoked from within
"::hw_dcm_module_v1_00_c::check_iplevel_settings 550254872"
ERROR:MDT - Hardware system has errors. Aborting Linker script generation
ERROR:MDT - Hardware system has errors. Aborting Linker script generation

I try to google, but got nothing helping. Can angbody help me? Or just give me a Complex FIR Filtering EDK project that can run correctly in you computer, then maybe i can find out where is the problem. Thanks very much!
BTW, My EDK is 9.2i, Impulse CoDeveloper is 3.30a.
mmw119

[RalphBodenner]

Hi,

This looks like a configuration problem with the Xilinx tools. Do you have the latest service pack for EDK and the IP core library? I would suggest opening a support ticket with Xilinx.

Regards,
Ralph

[meix]

Hi mmw119,

It seems like your EDK complained no peripheral instance is assigned for "stdout". Please check the Software Platform Setting, you can find the "stdout" and "stdin" in the OS and Libraries tab. Make sure they both have the value RS232_Uart_1. I'm using Xilinx EDK 10.1, so I cannot replicate your problem. EDK 10.1 sets the "stdout" and "stdin" value to RS232_Uart_1 by default. You may need to do so manually in EDK 9.2.

If this is not the cause of your problem, we can try other solutions next time.

Regards,

Mei