- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Hello,
We are trying to send video frames from one embedded system to another. As a preliminary step, we successfully sent the video frames from the transmitter to the PC using telnet session and TCP as a transport protocol. To accelerate data transmission, it is required to use UDP instead of the TCP. After changing the code and successfully compiling it, the following errors are encountered in NIOS IDE [Network]: See STDERR (FAULT_LEVEL is SYSTEM) [Network]: FAULT_LEVEL is SYSTEM [Network]: FATAL Error, Restart required [Network]: Locking scheduler - endless loop. Can any one advise me on this issue. :confused::confused::cry: Your prompt response is highly appreciated. Thanks & Regardsコピーされたリンク
8 返答(返信)
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Stop sending the same question multiple times... this isn't the first time you do it.
What IP stack are you using? I don't recognise those messages. There is probably an error in your source code, can you post it? At least the UDP part.- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Hello,
Thank you. I'd like to clarify 2 points: 1- This is the same project, but not the same question 2- Altera service center performance to our question is very slow. Any way, excuse me for my question; as it is my first time to design a project like that. Kindly find attached the source code for the UDP called (ethernet.txt) Thanks & Regards- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Hello,
We are using the NicheStack TCP/IP in our design. Thanks & Regards- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
I would strip out the asynchronous sockets and focus on getting UDP functional with simple messaging first. Do something like this (http://www.abc.se/~m6695/udp.html), first, and build from there.
Cheers and good luck, slacker- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
I did a quick search for those error messages in the Interniche stack source code and didn't find them. They seem to come from somewhere else.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
--- Quote Start --- I would strip out the asynchronous sockets and focus on getting UDP functional with simple messaging first. Do something like this (http://www.abc.se/~m6695/udp.html), first, and build from there. Cheers and good luck, slacker --- Quote End --- Hello, Thank you very much for your reply. 1- I tried to make the server as you suggested in your link and after compiling and running the code on NIOS II IDE for eclipse the following messages are encountered: panic: unlock NET dtrap - needs breakpoint 2- Do you have a method to test such a server code. Your prompt response is highly appreciated. Thanks & Regards :)
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
You should use a debugger and put a breakpoint on the dtrap() function in the iniche stack. Then go up the function call list and find out which function caused the dtrap() call.
From the message over it seems that uCOS couldn't signal a semaphore. The error code returned by OSSemPost() may tell us why.- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
--- Quote Start --- Hello, Thank you very much for your reply. 1- I tried to make the server as you suggested in your link and after compiling and running the code on NIOS II IDE for eclipse the following messages are encountered: panic: unlock NET dtrap - needs breakpoint 2- Do you have a method to test such a server code. Your prompt response is highly appreciated. Thanks & Regards :) --- Quote End --- As a reference for anyone reaching this page from a google search... I had this unlock NET error and found that my problem was that I was trying to open a UDP socket before I had run the following: --- Quote Start --- alt_iniche_init(); netmain(); while (!iniche_net_ready) TK_SLEEP(1); --- Quote End --- I moved my UDP socket code below those lines and the error went away.
