Hello, All!
I am evaluating the Ethernet traffic performance on MCB167-NET evaluation board; have license for Advanced RTX-166 suite including TcpNet library.
The board I have is populated with AX88796 Ethernet chip. To see how it works, the supplied Telnet_demo project is being used. I have successfully recompiled the project for MCB-XC167 target (no problems encountered). No changes were introduced besides the DHCP was turned off in AT166_Config.c file (working with manual IP settings). For debugging purposes the ULink2 USB/JTAG adapter is in use.
Result is that the firmware can be transferred to the board but after run is looping between addresses C0xxxx (are those TcpNet’s ?) so no expected functionality is achieved. Here is an excerpt of where firmware is typically found when IDE’s Debug Stop Running is issued
… 00C015AE F3F8FA8B MOVB RL4,DPP2:0x0BFA 00C015B2 6981 ANDB RL4,#1 00C015B4 C084 MOVBZ R4,RL4 00C015B6 3D02 JMPR CC_NZ,0xC015BC 00C015B8 CA00B000 CALLA+ CC_UC,0xC000B0 00C015BC CA00B001 CALLA+ CC_UC,0xC001B0 00C015C0 BB01 CALLR 0xC015C4 00C015C2 0DF5 JMPR CC_UC,0xC015AE 00C015C4 F3FAFA8B MOVB RL5,DPP2:0x0BFA 00C015C8 9AF57010 JNB R5.1,0xC016AC …
Quite contrary, another example supplied, EasyWEB, with a tiny TCP/IP stack from 3d party (i.e. based NOT on TcpNet library), works just fine.
What could be a problem: DIP switches are not in a proper position, project configuration does not match the latest hardware design (the board was bought this month), …?
I searched through AR166.CHM & Evaluation Board User Guide. I found the Guide is useless and outdated, describes the obsolete board design: e.g., see the page 8 and description of DIP switches…
Regards, Nikolay.