• State Not Answered
  • Locked Locked
  • Replies 22 replies
  • Subscribers 22 subscribers
  • Views 7284 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SLIP problem

Christian Hofstetter

Hi,
Im working with an MCBSTM32E (STM32F103ZE chip) evaluation board and Im trying to create a web server on my board. Because theres no Ethernet controller on board Im using an external WiFi module (RS9110-11-21 from Redpine Signals). Ive configured UART2 as my serial connection to the module.
In the Net_Config.c file ive unchecked the Ethernet Network Interface and have enabled the SLIP interface. When I try to compile the code I get the following build output message:

Build target 'STM32 Flash'
compiling Net_Config.c...
linking...
.\Obj\Test.axf: Error: L6218E: Undefined symbol dhcp_vcid (referred from at_dhcp.o).
.\Obj\Test.axf: Error: L6218E: Undefined symbol own_hw_adr (referred from at_dhcp.o).
Target not created

The serial driver file Serial_STM32x.c is included and modified.
Has anyone encountered the same problem?

BTW if I enable the Ethernet interface I dont get the error messages but the program will get stuck in the init_TcpNet() function. (Fatal Error Handler)

Thanks,
Chris

Parents
  • 0 in reply to Christian Hofstetter

    This is the output from the debugger (SLIP full debug/ ICMP full debug):

    SLIP:Initialize SLIP interface
SLIP:Dialing number:
SLIP:Link up, SLIP Connected.
SLIP:END char Received, Frame valid.
SLIP:END char Received, Frame valid.
ICMP:*** Processing ICMP frame ***
ICMP: ECHO Request received
ICMP: Identifier: 0x0300
ICMP: Sequence: 0x0900
ICMP:Sending ECHO Reply
SLIP:Sending SLIP frame...
SLIP:Transmitting queued frame.

    If I understand this correct then the uC receives the Ping Request and transmits the Ping Reply. I think that the problem is caused by the WLAN module itself because I ruled out the connection between those two by replacing the wires. Another possibility could be that the SLIP send function is not working properly...Any idea how I could rule out the latter one?
    I already tried to use an intelligent oscilloscope to measure the levels on the Tx/Rx wires and decode the data but it seems like the oscilloscope is corrupting the data. I dont know why it's causing troubles because usually the impedance of the oscilloscopes and the probe should be high enough.

    Thanks

Reply
  • 0 in reply to Christian Hofstetter

    This is the output from the debugger (SLIP full debug/ ICMP full debug):

    SLIP:Initialize SLIP interface
SLIP:Dialing number:
SLIP:Link up, SLIP Connected.
SLIP:END char Received, Frame valid.
SLIP:END char Received, Frame valid.
ICMP:*** Processing ICMP frame ***
ICMP: ECHO Request received
ICMP: Identifier: 0x0300
ICMP: Sequence: 0x0900
ICMP:Sending ECHO Reply
SLIP:Sending SLIP frame...
SLIP:Transmitting queued frame.

    If I understand this correct then the uC receives the Ping Request and transmits the Ping Reply. I think that the problem is caused by the WLAN module itself because I ruled out the connection between those two by replacing the wires. Another possibility could be that the SLIP send function is not working properly...Any idea how I could rule out the latter one?
    I already tried to use an intelligent oscilloscope to measure the levels on the Tx/Rx wires and decode the data but it seems like the oscilloscope is corrupting the data. I dont know why it's causing troubles because usually the impedance of the oscilloscopes and the probe should be high enough.

    Thanks

Children
No data