How to start application automatically?

I am having the same problem but with the CycloneII dev. kit.

We have spoken with an Arrow FAE but he had no ideas.

We tried an uC/OS-II example and it does NOT have the same problem.

So, it is looking to be an eCos issue.

ANY ideas are welcome.

We don't have redBoot - is this required?

Thanks

--- Quote Start ---

originally posted by pxs@Mar 31 2006, 02:28 PM

i am having the same problem but with the cycloneii dev. kit.

we have spoken with an arrow fae but he had no ideas.

we tried an uc/os-ii example and it does not have the same problem.

so, it is looking to be an ecos issue.

any ideas are welcome.

we don't have redboot - is this required?

thanks

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13952)

--- quote end ---

--- Quote End ---

Do you have any output (printf) that goes to the jtag uart? I had similar problems when the application (including the ecos lib) printed any diagnostic information. Try to suppress all output to the jtag uart (I think the rs232 uart should work) by setting the debug device and the diagnostic console device to none.

--- Quote Start ---

originally posted by orsino+apr 3 2006, 12:15 pm--><div class='quotetop'>quote (orsino @ apr 3 2006, 12:15 pm)</div>

--- quote start ---

<!--quotebegin-pxs@Mar 31 2006, 02:28 PM

i am having the same problem but with the cycloneii dev. kit.

we have spoken with an arrow fae but he had no ideas.

we tried an uc/os-ii example and it does not have the same problem.

so, it is looking to be an ecos issue.

any ideas are welcome.

we don&#39;t have redboot - is this required?

thanks

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13952)

--- quote end ---

--- Quote End ---

Do you have any output (printf) that goes to the jtag uart? I had similar problems when the application (including the ecos lib) printed any diagnostic information. Try to suppress all output to the jtag uart (I think the rs232 uart should work) by setting the debug device and the diagnostic console device to none.

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13985)</div>

[/b]

--- Quote End ---

You are may be right.

Any data sending via jtag_uart (printf) would be filling fifo of jtag_uart.

If jtag is not connected and appropriate app is not ran nios would be stoped.

Thanks,

That seems be the problem.

I have set the stdin, stdout, stderr to null and within ecos set the "debug Device" and "Diagnostic console device" to none.

The system boots without the need of nios2-terminal!

I am now testing if I can put the stdin value to /dev/uart.

I would like the printf out the rs232 port.

Thanks for the help.

We have done some further investigation:

We set the nios library application settings to:

stdin : uart1

stdout: uart1

stderr: uart1

We set the following configuration parameters in the configtool for eCos to:

NIOS2 Architechture

Debug Device /dev/uart1

Diagnostic console device /dev/uart1

HAL SOPC drivers

check the "Detected SOPC devices" box

Serial device drivers

check "Hardware serial device drivers" box

Thank you, orsino, slava!

I deleted "printf", then my application started automatically.

Thank you very much.

I&#39;m sorry for my late replay.