Codescape debugger unable to connect to the Minimorph board

This topic contains 20 replies, has 2 voices, and was last updated by  Jialun_Liu 4 years, 6 months ago.

Viewing 15 posts - 1 through 15 (of 21 total)
  • Author
    Posts
  • #31191

    Jialun_Liu
    Member

    Hi,

    I have reflashed the Minimorph board via the USB successfully, the shining LED shows that. And I have also pinged the IP address of the board to the host. Even further, I have added a network connection entry for the Minimorph to my host system’s network manager according to the Reference manual provided.

    But when I am trying to use the csdebugger, it just kept telling me that it is not able to connect to the target board.

    Could anyone help me please?

    Cheers.

    #36872

    Sean
    Moderator

    I have some questions to best understand what the issue is:

    • What network interface are you using to connect, USB or WiFi?
    • Are you running in a virtual machine?
    • In Codescape Debugger, are you going to File -> Connect to Remote Debug Target?
    • Are you referring to the Minimorph by name or by IP address?

    Let me know the answer to these questions and I’ll try to resolve the issue with you.

    #36873

    Jialun_Liu
    Member

    I have some questions to best understand what the issue is:

    • What network interface are you using to connect, USB or WiFi?
    • Are you running in a virtual machine?
    • In Codescape Debugger, are you going to File -> Connect to Remote Debug Target?
    • Are you referring to the Minimorph by name or by IP address?

    Let me know the answer to these questions and I’ll try to resolve the issue with you.

    I am using the USB to connect to the board. And I have installed the CenOS 6.3 system on my laptop, I was trying to run the csdebugger on my laptop.

    I tried the ‘File -> Connect to Remote Debug Target’, and also tried the connection panel which appears every time when I opened the csdebugger.

    I have pinged the IP address of the Minimorph board and also added a network connection entry for the Minimorph to my host system’s network manager according to the Reference manual provided, which supposed to connect to the board automatically everytime when I connect the board to my laptop via the USB.

    #36874

    Sean
    Moderator

    Are you referring to the Minimorph by name or by IP address?

    #36875

    Jialun_Liu
    Member

    Are you referring to the Minimorph by name or by IP address?

    I think I am referring to the Minimorph by IP address

    #36876

    Sean
    Moderator

    It sounds like you are doing everything correctly.

    To be sure of the state – the orange LED on the Minimorph is flashing 3 times every ~5 seconds?

    Can you run telnet 169.254.7.252 (replace 169.254.7.252 with your Minimorph IP address).

    Login with username default (empty password). Run the following applications and let me know the output?
    $ uname -a
    $ ifconfig
    $ ps -a

    #36877

    Jialun_Liu
    Member

    It sounds like you are doing everything correctly.

    To be sure of the state – the orange LED on the Minimorph is flashing 3 times every ~5 seconds?

    Can you run telnet 169.254.7.252 (replace 169.254.7.252 with your Minimorph IP address).

    Login with username default (empty password). Run the following applications and let me know the output?
    $ uname -a
    $ ifconfig
    $ ps -a

    Yes, the orange LED on the Minimorph is flashing 3 times every ~5 seconds.

    I don’t have the board with me now, but I will try to run it tonight. Thanks for your help.

    #36878

    Jialun_Liu
    Member

    It sounds like you are doing everything correctly.

    To be sure of the state – the orange LED on the Minimorph is flashing 3 times every ~5 seconds?

    Can you run telnet 169.254.7.252 (replace 169.254.7.252 with your Minimorph IP address).

    Login with username default (empty password). Run the following applications and let me know the output?
    $ uname -a
    $ ifconfig
    $ ps -a

    I have ran the application you gave me, and the results are the following:
    # telnet 169.254.5.44

    Entering character mode
    Escape character is '^]'.

    01TTVC22000317-Minimorph login: default
    $ uname -a
    Linux 01TTVC22000317-Minimorph 3.6.0 #2 Thu Feb 7 16:03:18 GMT 2013 metag GNU/Linux
    $ ifconfig
    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:113 errors:0 dropped:0 overruns:0 frame:0
    TX packets:113 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:6241 (6.0 KiB) TX bytes:6241 (6.0 KiB)

    usb0 Link encap:Ethernet HWaddr 02:09:F5:01:41:3D
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:13 errors:0 dropped:6 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2680 (2.6 KiB) TX bytes:0 (0.0 B)

    usb0:avahi Link encap:Ethernet HWaddr 02:09:F5:01:41:3D
    inet addr:169.254.5.44 Bcast:169.254.255.255 Mask:255.255.0.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    wlan0 Link encap:Ethernet HWaddr 00:19:F5:01:41:3D
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    $ ps -a
    PID USER COMMAND
    1 root init
    2 root [kthreadd]
    3 root [ksoftirqd/0]
    4 root [kworker/0:0]
    5 root [kworker/0:0H]
    6 root [kworker/u:0]
    7 root [kworker/u:0H]
    8 root [khelper]
    9 root [kdevtmpfs]
    10 root [bdi-default]
    11 root [kblockd]
    12 root [khubd]
    13 root [cfg80211]
    14 root [kworker/0:1]
    15 root [kswapd0]
    16 root [fsnotify_mark]
    17 root [crypto]
    27 root [img-spi.1]
    28 root [mtdblock0]
    29 root [dwc_otg]
    30 root [irq/35-hdmi-eve]
    31 root [dw-mci-card]
    32 root [deferwq]
    45 root /sbin/syslogd -m 0
    47 root /sbin/klogd
    102 root wpa_supplicant -B -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -P/v
    107 root udhcpc -t3 -b -iwlan0 -p /var/run/udhcpc-wlan0.pid
    110 root csdebug -i wlan0
    115 root /usr/sbin/ntpd
    120 default avahi-daemon: running [01TTVC22000317-Minimorph.local]
    122 root {flowworld} /bin/sh /usr/bin/flowworld
    124 root wifi-setup
    140 root [kworker/u:2]
    148 default avahi-autoipd: [usb0] bound 169.254.5.44
    149 root avahi-autoipd: [usb0] callout dispatcher
    160 root csdebug -i usb0
    161 root {flashleds} /bin/sh /etc/init.d/flashleds
    169 root /sbin/getty -L ttyS0 115200 vt100
    171 root /usr/sbin/telnetd
    257 root {acmgetty} /bin/sh /etc/init.d/acmgetty
    258 root -sh
    486 root telnet 169.254.5.44
    487 default -sh
    564 root sleep 5
    565 default ps -a
    $
    8 root [khelper]
    9 root [kdevtmpfs]
    10 root [bdi-default]
    11 root [kblockd]
    12 root [khubd]
    13 root [cfg80211]
    14 root [kworker/0:1]
    15 root [kswapd0]
    16 root [fsnotify_mark]
    17 root [crypto]
    27 root [img-spi.1]
    28 root [mtdblock0]
    29 root [dwc_otg]
    30 root [irq/35-hdmi-eve]
    31 root [dw-mci-card]
    32 root [deferwq]
    45 root /sbin/syslogd -m 0
    47 root /sbin/klogd
    102 root wpa_supplicant -B -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -P/v
    107 root udhcpc -t3 -b -iwlan0 -p /var/run/udhcpc-wlan0.pid
    110 root csdebug -i wlan0
    115 root /usr/sbin/ntpd
    120 default avahi-daemon: running [01TTVC22000317-Minimorph.local]
    122 root {flowworld} /bin/sh /usr/bin/flowworld
    124 root wifi-setup
    140 root [kworker/u:2]
    148 default avahi-autoipd: [usb0] bound 169.254.5.44
    149 root avahi-autoipd: [usb0] callout dispatcher
    160 root csdebug -i usb0
    161 root {flashleds} /bin/sh /etc/init.d/flashleds
    169 root /sbin/getty -L ttyS0 115200 vt100
    171 root /usr/sbin/telnetd
    257 root {acmgetty} /bin/sh /etc/init.d/acmgetty
    258 root -sh
    486 root telnet 169.254.5.44
    487 default -sh
    564 root sleep 5
    565 default ps -a

    #36879

    Sean
    Moderator

    Ok, everything looks correct!

    Please can you confirm your version of Codescape Debugger for me? If you goto Help -> About Codescape Debugger Mini. Please paste the contents of the text box at the bottom of the dialogue.

    Additionally, instead of using the IP address, please try connecting to “01TTVC22000317-Minimorph.local”.
    If you have a fresh install of CentOS 6.3, you will need to do a couple of steps first:

    • Enable the EPEL repository
      Instructions
    • Install nss-mdns
      host$ yum install nss-mdns
    • Update the ‘/etc/nsswitch.conf’ file.
      Look at the line which begins ‘hosts:’ – if there is no mention of ‘mdns4’ or ‘mdns4_minimal’ then they need to be added (you will need superuser privileges to edit this file):
      hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
    • You may need to reboot the host at this point.
    • Re-establish the connection with the Minimorph.
    • To confirm it is working, ping the Minimorph:
      host$ ping 01TTVC22000317-Minimorph.local
    • Now launch Codescape and connect to Linux target name “01TTVC22000317-Minimorph.local”
    #36880

    Jialun_Liu
    Member

    Hi,

    I have looked at the version of my csdebugger:
    Codescape Debugger Mini 7.1.9.1
    cslib_edu 7.1.9.1
    IMGMetaG Version tag not found in /opt/imgtec/Codescape-Debugger-Mini-7.1/../Disassembler/libimgmetadisasm-x86_64.so
    CSUtils 1.9.1.6
    IMG 1.1.1.34
    Python 2.7.3
    wxWidgets 2.9.3.1
    Linux 2.6.32-279.el6.x86_64 x86_64
    GTK+ 2.18.9

    I followed the guidelines, but I still failed to connect to the Minimorph:
    ping 01TTVC22000317-Minimorph.local
    ping: unknown host 01TTVC22000317-Minimorph.local

    I also tried to ping the Minimorph in the ‘screen’:
    Welcome to Buildroot
    01TTVC22000317-Minimorph login: root
    # ping 01TTVC22000317-Minimorph.local
    ping: bad address '01TTVC22000317-Minimorph.local'

    Please help……

    #36881

    Sean
    Moderator

    I wouldn’t expect you to be able to ping the Minimorph from its self by name so that is ok. All the information you have provided looks ok – we are running out of suggestions at the moment as everything looks setup correctly.

    I installed CentOS 6 this morning and have tested the same setup here and found no issues.

    Can you be 100% sure you have got the correct IP address in Codescape Debugger when you are connecting to the Minimorph? Sorry to ask but as I say, I do not have many more suggestions for now.

    #36882

    Jialun_Liu
    Member

    I wouldn’t expect you to be able to ping the Minimorph from its self by name so that is ok. All the information you have provided looks ok – we are running out of suggestions at the moment as everything looks setup correctly.

    I installed CentOS 6 this morning and have tested the same setup here and found no issues.

    Can you be 100% sure you have got the correct IP address in Codescape Debugger when you are connecting to the Minimorph? Sorry to ask but as I say, I do not have many more suggestions for now.

    Yes, I am using the IP address: 169.254.5.44, which really could not be wrong…..

    Actually, do I need a debug adapter called DA-net in order to connect to the Minimorph board?

    #36883

    Sean
    Moderator

    Sure, I understand, as I say – everything else that we can think of looks like it is correctly setup and configured and I have tested it and not seen the same issues. This is why I apologise when I ask you as I am sure you will have checked.

    The DA-Net is for JTAG level of debug and, whilst it would allow you to connect to the Minimorph a different way, would cost a lot of money. You do not need the DA-Net to connect to the Minimorph through the debug stub (CS Debug).

    I will ask again if my colleagues have any other suggestions – there should be nothing else standing in the way of a successful connection after all the things we have checked here.

    #36884

    Sean
    Moderator

    I have some more suggestions so we can try to get a better understanding of what is happening:

    1. Codescape has a defect report that you can submit to us – this will check for all sorts of python setup issues etc. If you launch Codescape and goto Help -> Feature Request / Defect Reporting and submit, I’ll take a look and get back to you.
    2. Please could you run on the host “ifconfig” and let me know the output.
    3. Last resort – please could you turn your firewall off in system-config-firewall
      At least open up port 59 TCP & UDP and ensure the dynamic ports above 49152 can be opened? csdebug will request a random port number to open bi-directionally in that range
    #36885

    Jialun_Liu
    Member

    I have some more suggestions so we can try to get a better understanding of what is happening:

    1. Codescape has a defect report that you can submit to us – this will check for all sorts of python setup issues etc. If you launch Codescape and goto Help -> Feature Request / Defect Reporting and submit, I’ll take a look and get back to you.
    2. Please could you run on the host “ifconfig” and let me know the output.
    3. Last resort – please could you turn your firewall off (or at least open up port 58 TCP & UDP) in system-config-firewall

    I have ran the command:
    $ ifconfig
    eth0 Link encap:Ethernet HWaddr F0:DE:F1:BC:D2:CF
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
    Interrupt:20 Memory:f2500000-f2520000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:8 errors:0 dropped:0 overruns:0 frame:0
    TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:480 (480.0 b) TX bytes:480 (480.0 b)

    wlan0 Link encap:Ethernet HWaddr 10:0B:A9:69:9F:A0
    inet addr:129.31.223.77 Bcast:129.31.223.255 Mask:255.255.248.0
    inet6 addr: 2001:630:12:2e1e:120b:a9ff:fe69:9fa0/64 Scope:Global
    inet6 addr: fe80::120b:a9ff:fe69:9fa0/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:29811 errors:0 dropped:0 overruns:0 frame:0
    TX packets:274 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:5211546 (4.9 MiB) TX bytes:47160 (46.0 KiB)

    I will send the defect report via my own e-mail, since CSdebugger could not send the report directly.

Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic.