• 状态
  • 已锁定 已锁定
  • 回复 15 回复
  • 订户 13 订户
  • 视图 8596 视图
  • 用户 0 会员在此处
选项
选项
相关

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MCSDK Video中的TFTP出问题

lei wang2
Intellectual 440 points


软件平台：CCS5.2

硬件：6678EVM

按照这个流程走（processors.wiki.ti.com/.../MCSDK_VIDEO_2.1_CODEC_TEST_FW_User_Guide），报错如下：

附件详细说明错误：

[C66xx_0] Read tftp config file

[C66xx_0] Read testVecs file

[C66xx_0] Read codec config file name ..\..\..\siu\vct\testVecs\h264hpdec\config\codecParams.cfg

[C66xx_0] Read test file name ..\..\..\siu\vct\testVecs\h264hpdec\config\multiClip.cfg

[C66xx_0]

[C66xx_0] Creating Algorithm Instance...FYI: Attrs     | Val

[C66xx_0]      SCRATCH   |  0 

[C66xx_0]      PERSIST   |  1 

[C66xx_0]      WRITEONCE |  2 

[C66xx_0] Num. buffs requested = 23

[C66xx_0] algAlloc req. Buffer 0: space = 17, attr = 1, size = 4840

[C66xx_0] algAlloc req. Buffer 1: space = 0, attr = 0, size = 8840

[C66xx_0] algAlloc req. Buffer 2: space = 0, attr = 0, size = 78184

[C66xx_0] algAlloc req. Buffer 3: space = 0, attr = 0, size = 8992

[C66xx_0] algAlloc req. Buffer 4: space = 17, attr = 1, size = 8664

[C66xx_0] algAlloc req. Buffer 5: space = 17, attr = 1, size = 176

[C66xx_0] algAlloc req. Buffer 6: space = 17, attr = 1, size = 144

[C66xx_0] algAlloc req. Buffer 7: space = 17, attr = 1, size = 4420

[C66xx_0] algAlloc req. Buffer 8: space = 17, attr = 1, size = 24

[C66xx_0] algAlloc req. Buffer 9: space = 17, attr = 1, size = 1860480

[C66xx_0] algAlloc req. Buffer 10: space = 17, attr = 1, size = 15079680

[C66xx_0] algAlloc req. Buffer 11: space = 17, attr = 1, size = 1966080

[C66xx_0] algAlloc req. Buffer 12: space = 17, attr = 1, size = 136

[C66xx_0] algAlloc req. Buffer 13: space = 17, attr = 1, size = 144

[C66xx_0] algAlloc req. Buffer 14: space = 17, attr = 1, size = 8840

[C66xx_0] algAlloc req. Buffer 15: space = 17, attr = 1, size = 544

[C66xx_0] algAlloc req. Buffer 16: space = 17, attr = 1, size = 540

[C66xx_0] algAlloc req. Buffer 17: space = 17, attr = 1, size = 264

[C66xx_0] algAlloc req. Buffer 18: space = 17, attr = 1, size = 12672

[C66xx_0] algAlloc req. Buffer 19: space = 17, attr = 1, size = 74880

[C66xx_0] algAlloc req. Buffer 20: space = 17, attr = 1, size = 110592

[C66xx_0] algAlloc req. Buffer 21: space = 17, attr = 1, size = 8160

[C66xx_0] algAlloc req. Buffer 22: space = 17, attr = 1, size = 116

[C66xx_0] algAlloc supplied: Buffer 0: space = 17, attr = 1, size = 4840

[C66xx_0] algAlloc supplied: Buffer 1: space = 0, attr = 0, size = 8840

[C66xx_0] algAlloc supplied: Buffer 2: space = 0, attr = 0, size = 78184

[C66xx_0] algAlloc supplied: Buffer 3: space = 0, attr = 0, size = 8992

[C66xx_0] algAlloc supplied: Buffer 4: space = 17, attr = 1, size = 8664

[C66xx_0] algAlloc supplied: Buffer 5: space = 17, attr = 1, size = 176

[C66xx_0] algAlloc supplied: Buffer 6: space = 17, attr = 1, size = 144

[C66xx_0] algAlloc supplied: Buffer 7: space = 17, attr = 1, size = 4420

[C66xx_0] algAlloc supplied: Buffer 8: space = 17, attr = 1, size = 24

[C66xx_0] algAlloc supplied: Buffer 9: space = 17, attr = 1, size = 1860480

[C66xx_0] algAlloc supplied: Buffer 10: space = 17, attr = 1, size = 15079680

[C66xx_0] algAlloc supplied: Buffer 11: space = 17, attr = 1, size = 1966080

[C66xx_0] algAlloc supplied: Buffer 12: space = 17, attr = 1, size = 136

[C66xx_0] algAlloc supplied: Buffer 13: space = 17, attr = 1, size = 144

[C66xx_0] algAlloc supplied: Buffer 14: space = 17, attr = 1, size = 8840

[C66xx_0] algAlloc supplied: Buffer 15: space = 17, attr = 1, size = 544

[C66xx_0] algAlloc supplied: Buffer 16: space = 17, attr = 1, size = 540

[C66xx_0] algAlloc supplied: Buffer 17: space = 17, attr = 1, size = 264

[C66xx_0] algAlloc supplied: Buffer 18: space = 17, attr = 1, size = 12672

[C66xx_0] algAlloc supplied: Buffer 19: space = 17, attr = 1, size = 74880

[C66xx_0] algAlloc supplied: Buffer 20: space = 17, attr = 1, size = 110592

[C66xx_0] algAlloc supplied: Buffer 21: space = 17, attr = 1, size = 8160

[C66xx_0] algAlloc supplied: Buffer 22: space = 17, attr = 1, size = 116

[C66xx_0]

[C66xx_0] Algorithm Instance Creation Done...

[C66xx_0]

[C66xx_0] Starting TFTP Get for airshow_p352x288.264... Error receive from server!      //显示应该是TFTP设置有问题吧！求解答怎么设这TFTP

[C66xx_0]

[C66xx_0] TFTP Get stopped.

[C66xx_0] TFTP Statistics-------------------+

[C66xx_0] |  RX Bytes          :          0 |

[C66xx_0] |  TX Bytes          :          0 |

[C66xx_0] |  Valid Packets     :          0 |

[C66xx_0] |  Duplicate Packets :          0 |

[C66xx_0] |  Error Packets     :          0 |

[C66xx_0] +---------------------------------+

[C66xx_0]

[C66xx_0] TFTP Put stopped.

[C66xx_0] TFTP Statistics-------------------+

[C66xx_0] |  RX Bytes          :          0 |

[C66xx_0] |  TX Bytes          :          0 |

[C66xx_0] |  Valid Packets     :          0 |

[C66xx_0] |  Duplicate Packets :          0 |

[C66xx_0] |  Error Packets     :          0 |

[C66xx_0] +---------------------------------+

[C66xx_0]

[C66xx_0]  --------------  SUMMARY --------------------

[C66xx_0]  Total number of Frames              = 1

[C66xx_0]  Width and Height                    = 0, 0

[C66xx_0]  --------------    END   --------------------

[C66xx_0]

[C66xx_0]  End of execution

  • 0
    TI__Intellectual 1470 points

    你可以先在uboot命令行或者linux命令行使用tftp命令，验证是否能够和tftp服务器通讯上。

  • 0 回复 Wei
    Intellectual 440 points

    1. 我用的是win7系统，在DOS里面测试TFTP通讯吧？是测DSP是否能够和服务器连接还是PC与服务器连接？

    2. 在PC上安装tftpd32软件之后，是把PC作为服务器吧？如果PC作为服务器，还需要在DOS中输入tftp命令吗？

    由于对tftp不是太懂，谢谢您的回答。

  • 0 回复 Wei
    Intellectual 440 points

    UBOOT命令行怎么调出来？是设置hyper terminal吗？波特率115200那个吗

  • 0 回复 Wei
    Intellectual 440 points

    在mcsdk_video目录中，dsp文件夹是在DSP上运行的程序，host目录是在PC上运行的吗？如果是这样，同时运行两个程序，CCS不是不能同时打开两个工程吗？求解，谢谢！

  • 0 回复 lei wang2
    TI__Intellectual 1470 points

    你对照网页上的步骤再对一下。PC是作为TFTP服务器的。你需要保证DSP的地址设置正确，PC的IP地址配置正确。另外你也可以检查一下tftp服务器的log，看是否有错误信息。

    你做的这个例子是不需要DSP跑linux的，所以我的建议说在linux下测试tftp不适用了。

  • 0 回复 Wei
    Intellectual 440 points

    1.  谢谢您的耐心回答，在tftp的log中显示如下：

    Connection received from 192.168.1.100 on port 51651 [11/03 13:03:40.965]
    Write request for file <input>. Mode netascii [11/03 13:03:40.966]
    Using local port 51652 [11/03 13:03:40.969]
    Peer sent unexpected message 5 [11/03 13:03:41.098]

    2. PC的ip地址我是通过DHCP方式和路由连接，然后用一根网线把DSP和路由连接，路由和外网没有没有连接，PC和外网也没有连接，同ipconfig /all命令看到IP如下：设这为192.168.1.101；DSP的IP地址设置为192.168.1.100，这应该有没有错吧

  • 0 回复 Wei
    Intellectual 440 points

    wei,您好！我做了一个这个实验(http://processors.wiki.ti.com/index.php/MCSDK_VIDEO_2.1_PKT_Demo_Guide)，但是到后期运行startMplayer.dat，就会出先这个问题，如下图：

    我的系统是WIN7，然后系统盘是D盘。在运行sendpkts.dat时，也出现路径的问题，但是通过看sendpkts.dat文件，发现指定的perl软件是C盘，通过修改，可以运行sendpkts.dat。但是运行startMplayer.dat时候，出现如上如问题。这次找不解决办法。

    还有就是WIN7的Mplayer必须是特定版本吗？

    望您能给与帮助，谢谢！

  • 0 回复 Wei
    Intellectual 440 points

    wei,您好!

    通过查看代码，siuVctTftp.c中看到，如下：

    但是TFTP_FILE_XFER_COMPLETE这个定义我在本文件包含的头文件没有找到，我想看看这个代表什么意思，查找错误出现在哪个地方？

    我怎样可以测试DSP是否与TFTP server连接呢？上面您提到UBOOT命令，这个不知道怎么使用，可否指教！谢谢

  • 0 回复 lei wang2
    TI__Intellectual 1470 points

    这个问题你查得怎么样了？

    从log上看，两边的IP设置都应该是正常的，服务器和client能够互相交换报文。可能还是文件路径配置，或者是访问权限的问题。你可以用Wireshark抓一下握手报文，看看tftp交换的具体过程，具体的参数。

  • 0 回复 Wei
    Intellectual 440 points

    你好，h264hpdec这个实验做成功了，但是在做h264hpenc这个实验一直不成功，我load完sv04.out，运行的时候，卡到了这里，截图如下：

    就不往下执行了，也没有报错。

    查看代码如下：

    这也没有输出报错信息。我想问问，这是编码需要时间长，还是怎么回事？

    好长时间都没有反应。

  • 0 回复 lei wang2
    TI__Intellectual 1470 points

    麻烦你把前面tftp遇到的问题的结论分享一下吧。

    你现在用的EVM自带的USB仿真模块，速率不是很快，如果读一个大文件会花些时间。

  • 0 回复 Wei
    Intellectual 440 points

    最开始的问题，就是我把板子和PC都连接在路由上面，结果不行。

    最后把板子和PC相连接，就好了。

    还有就是要注意ARP的设置，有时候设置完，但是运行程序的时候就没了，一定要查看。

    有没有一个比较好的方法，是读取文件速度快些呢？

  • 0 回复 Wei
    Intellectual 440 points

    您好，文件airshow_p1920*1080.yuv总共15M。您可以做次实验，谢谢。

    如果正确运行的程序，会输出如下结果：

    [C66xx_0] Read tftp config file
    [C66xx_0] Read testVecs file
    [C66xx_0] Read codec config file name ..\..\..\siu\vct\testVecs\h264hpdec\config\codecParams.cfg
    [C66xx_0] Read test file name ..\..\..\siu\vct\testVecs\h264hpdec\config\multiClip.cfg  

    ///现在是到这个地方就不再往下走了，不知道怎么回事
    [C66xx_0]
    [C66xx_0] Creating Algorithm Instance...FYI: Attrs | Val
    [C66xx_0] SCRATCH | 0
    [C66xx_0] PERSIST | 1
    [C66xx_0] WRITEONCE | 2
    [C66xx_0] Num. buffs requested = 23
    [C66xx_0] algAlloc req. Buffer 0: space = 17, attr = 1, size = 4840
    [C66xx_0] algAlloc req. Buffer 1: space = 0, attr = 0, size = 8840
    [C66xx_0] algAlloc req. Buffer 2: space = 0, attr = 0, size = 78184
              ........................

             ........................

              .......................

    [C66xx_0]
    [C66xx_0] Algorithm Instance Creation Done...
    [C66xx_0]
    [C66xx_0] Starting TFTP Get for airshow_p352x288.264... Server ACK received.  

    ////显示是通过TFTP接受数据和从板子上传回的，速度应该是比较快的。
    [C66xx_0] Decoding...
    [C66xx_0] Decoding...
    [C66xx_0]
    [C66xx_0] Decoded Frame # 0 , frame size 152064 bytes
    [C66xx_0]
    [C66xx_0]
    [C66xx_0] Starting TFTP Put for airshow_p352x288_264hpdec.yuv... Server ACK received.
    [C66xx_0] Decoding...
    [C66xx_0]

    ................

    ................

  • 0 回复 lei wang2
    TI__Intellectual 1470 points

    yuv视频数据是从网口下载的，配置文件是通过fopen，JTAG口来访问PC的文件系统，这个过程受限于100V1的速度，访问时间会比较长。如果可能你可以尝试使用560V2仿真器速度回快很多，或者直接把配置信息在代码里面直接配置，规避这个问题。

  • 0 回复 lei wang2
    Prodigy 20 points

    前辈您好，我也遇到了同样的问题：

    [C66xx_0] Read tftp config file
    [C66xx_0] Read testVecs file
    [C66xx_0] Read codec config file name ..\..\..\siu\vct\testVecs\h264hpdec\config\codecParams.cfg
    [C66xx_0] Read test file name ..\..\..\siu\vct\testVecs\h264hpdec\config\multiClip.cfg  

    6678的264enc例程到这个地方就不再往下走了，不知道怎么回事，请问您是怎么解决的啊