• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Subscribers 106 subscribers
  • Views 3155 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

XDS560V2 Mezzanine no longer connects to EVM

tscheck
Mastermind 23525 points

Some helpful information below if you encounter such an issue:

Usage Note: XDS560v2 Emulator goes into SAFE Mode if it is powered off for 10 consecutive times without a complete boot

Rev: 0.2

Description:

XDS560V2 Mezzanine emulator has a processor which runs the Linux operating system. Every time the emulator is powered up, it boots its internal Linux operating system that then allows the user to connect to the EVM board via CCS. This Linux operating system running on the XDS560V2 mezzanine emulator runs from a NAND FLASH file system.  FLASH file systems contain integrated management operations for wear-leveling and other tasks.  If the power is cut before the Linux completes booting, there is risk of damage to the filesystem.  The ‘SAFE’ mode functionality is integrated to prevent file system corruption from repeated boot operations without allowing Linux to fully boot. The XDS560V2 Mezzanine emulator software keeps track of the unsuccessful boot attempts of the emulator board during the boot process. Ten consecutive unsuccessful Linux boot attempts will result in the XDS560V2 Mezzanine emulator going into ‘SAFE’ mode.

The ‘SAFE’ mode of the XDS560V2 Mezzanine emulator will not allow the user to connect to the EVM board. CCS will report a connection error when SAFE mode is activated. When SAFE mode is active the LEDs D4, D5 and D6 will blink simultaneously.

Workaround:

The ‘BH560v2 Config Utility’ is used to clear the SAFE Mode of the emulator and bring the emulator to a normal working mode. The procedure for clearing the SAFE Mode using ‘BH560v2 Config Utility’ follows.

  1. Power on the EVM containing the XDS560V2 Mezzanine emulator
  2. Open ‘BH560v2 Config Utility’ with XDS560V2 Mezzanine emulator connected to your PC via a USB cable.
  3. The utility will report the emulator in the SAFE Mode.
  4. Use the “Clear Safe Mode” button to clear the SAFE mode state of the emulator.
  5. Close the ‘BH560v2 Config Utility’ and power cycle the EVM
  6. Connect the emulator using CCS after the emulator completes its boot cycle.

The XDS560v2 Mezzanine emulator takes approximately 30 seconds to boot-up. The successful booting of the XDS560v2 Mezzanine emulator is indicated by the following LED sequence:

  • Green LED (D3) turns ON
  • Yellow LED (D2) and Red LED (D1) turns ON
  • Green LED (D3) blinks and turns OFF

After the completion of booting XDS560v2 mezzanine emulator, it is ready to interface with CCS. Once CCS is connected to the target DSP, Green LED D4 turns ON.

  • 0
    TI__Mastermind 23525 points

    Usage Note: XDS560v2 Emulator goes into SAFE Mode if it is powered off for 10 consecutive times without a complete boot

    Rev: 0.2

    Description:

    XDS560V2 Mezzanine emulator has a processor which runs the Linux operating system. Every time the emulator is powered up, it boots its internal Linux operating system that then allows the user to connect to the EVM board via CCS. This Linux operating system running on the XDS560V2 mezzanine emulator runs from a NAND FLASH file system.  FLASH file systems contain integrated management operations for wear-leveling and other tasks.  If the power is cut before the Linux completes booting, there is risk of damage to the filesystem.  The ‘SAFE’ mode functionality is integrated to prevent file system corruption from repeated boot operations without allowing Linux to fully boot. The XDS560V2 Mezzanine emulator software keeps track of the unsuccessful boot attempts of the emulator board during the boot process. Ten consecutive unsuccessful Linux boot attempts will result in the XDS560V2 Mezzanine emulator going into ‘SAFE’ mode.

    The ‘SAFE’ mode of the XDS560V2 Mezzanine emulator will not allow the user to connect to the EVM board. CCS will report a connection error when SAFE mode is activated. When SAFE mode is active the LEDs D4, D5 and D6 will blink simultaneously.

    Workaround:

    The ‘BH560v2 Config Utility’ is used to clear the SAFE Mode of the emulator and bring the emulator to a normal working mode. The procedure for clearing the SAFE Mode using ‘BH560v2 Config Utility’ follows:

    1. Power on the EVM containing the XDS560V2 Mezzanine emulator
    2. Open ‘BH560v2 Config Utility’ with XDS560V2 Mezzanine emulator connected to your PC via a USB cable.
    3. The utility will report the emulator in the SAFE Mode.
    4. Use the “Clear Safe Mode” button to clear the SAFE mode state of the emulator.
    5. Close the ‘BH560v2 Config Utility’ and power cycle the EVM
    6. Connect the emulator using CCS after the emulator completes its boot cycle.

    The XDS560v2 Mezzanine emulator takes approximately 30 seconds to boot-up. The successful booting of the XDS560v2 Mezzanine emulator is indicated by the following LED sequence:

    • Green LED (D3) turns ON
    • Yellow LED (D2) and Red LED (D1) turns ON
    • Green LED (D3) blinks and turns OFF

    After the completion of booting XDS560v2 mezzanine emulator, it is ready to interface with CCS. Once CCS is connected to the target DSP, Green LED D4 turns ON.

    Usage Note: XDS560v2 Emulator fails to connect properly and it is not in Safe mode

    Rev: 0.1

    Description:

    XDS560V2 Mezzanine emulator has a processor which runs the Linux operating system which boots from a FLASH memory device. This operating system interacts with a data storage structure also contained in the FLASH memory device. If the storage for the Linux operating system or this data storage becomes corrupted, the XDS560V2 Mezzanine emulator will fail to boot correctly or to connect to CCS.

    This operating system has a 2-stage boot process. Whenever the 2nd stage fails to operate due to image corruption, the unit can be forced into the ‘Safe’ mode. ‘Safe’ mode only executes from the 1st stage and it supports image re-programming. Units that are failing due to image corruption can be forced into ‘Safe’ mode and then recovered by re-programming the operating system image.

    Workaround:

    Note: this sequence of steps should only be executed on a unit that is not in ‘Safe’ mode.  Multiple power cycles of the mezzanine emulator will be used to force it into ‘Safe’ mode, and then the image can be re-programmed. The ‘BH560v2 Config Utility’ is used to re-program the emulator and bring the emulator to a normal working mode. The procedure for programming the XDS560V2 emulator using ‘BH560v2 Config Utility’ follows:

    1. Power on the EVM containing the XDS560V2 Mezzanine emulator for about 10 seconds and then turn it back off for about 5 seconds. Repeat this sequence 10 times to force the emulator to enter the ‘Safe’ mode.
    2. Power on the EVM containing the XDS560V2 Mezzanine emulator
    3. Open ‘BH560v2 Config Utility’ with XDS560V2 Mezzanine emulator connected to your PC via a USB cable.
    4. The utility will report the emulator in the SAFE Mode.
    5. Select "Update ...".
    6. Go to Blackhawk firmware folder – normally "C:\ti\ccsv5\ccs_base\emulation\Blackhawk\Bh560v2\firmware".
    7. Select bh560v2_fw_mezzanine.
    8. Wait until the firmware update completes (do not power down during this step).
    9. After completion you should see the yellow and red LEDs on.
    10. Close the ‘BH560v2 Config Utility’ and power cycle the EVM
    11. Connect the emulator using CCS after the emulator completes its boot cycle.

    The XDS560v2 Mezzanine emulator takes approximately 30 seconds to boot-up. The successful booting of the XDS560v2 Mezzanine emulator is indicated by the following LED sequence:

    • Green LED (D3) turns ON
    • Yellow LED (D2) and Red LED (D1) turns ON
    • Green LED (D3) blinks and turns OFF

    After the completion of booting XDS560v2 mezzanine emulator, it is ready to interface with CCS. Once CCS is connected to the target DSP, Green LED D4 turns ON.

  • 0 in reply to tscheck
    Intellectual 300 points

    Hi,

    I have a DSP EVM with non functional XDS560V2 Mezzanine emulator.

    ‘BH560v2 Config Utility' is not able to detect any device connection

     Green and tellow lights are always on. Following is the log output.


    CMD: dtc_conf --version
    Version 5.0.281.0, built Jan 3 2011 23:02:23


    CMD: ipconfig

    Configurazione IP di Windows

    Scheda LAN wireless Connessione rete wireless 2:
    Stato supporto. . . . . . . . . . . . : Supporto disconnesso
    Suffisso DNS specifico per connessione:
    Scheda LAN wireless Connessione rete wireless:
    Stato supporto. . . . . . . . . . . . : Supporto disconnesso
    Suffisso DNS specifico per connessione: Belkin
    Scheda Ethernet Connessione alla rete locale (LAN):
    Suffisso DNS specifico per connessione:
    Indirizzo IPv6 locale rispetto al collegamento . : fe80::f80f:464e:9785:8611%11
    Indirizzo IPv4. . . . . . . . . . . . : 107.108.199.254
    Subnet mask . . . . . . . . . . . . . : 255.255.255.0
    Gateway predefinito . . . . . . . . . : 107.108.199.1
    Scheda Tunnel isatap.{733C672A-88D7-46E5-A073-C6E894E5EB6E}:
    Stato supporto. . . . . . . . . . . . : Supporto disconnesso
    Suffisso DNS specifico per connessione:
    Scheda Tunnel isatap.Belkin:
    Stato supporto. . . . . . . . . . . . : Supporto disconnesso
    Suffisso DNS specifico per connessione:
    Scheda Tunnel Teredo Tunneling Pseudo-Interface:
    Suffisso DNS specifico per connessione:
    Indirizzo IPv6 . . . . . . . . . . . . . . . . . : 2001:0:4137:9e76:a1:2382:9493:3801
    Indirizzo IPv6 locale rispetto al collegamento . : fe80::a1:2382:9493:3801%15
    Gateway predefinito . . . . . . . . . : ::
    Scheda Tunnel isatap.{EF5136B5-8153-41BA-83A4-476A649EA6DC}:
    Stato supporto. . . . . . . . . . . . : Supporto disconnesso
    Suffisso DNS specifico per connessione:

    CMD: Broadcasting 5 UDP DAYTIME requests...
    RES: 0 UDP DAYTIME Replies From: []


    CMD: arp -a

    Interfaccia: 107.108.199.254 --- 0xb
    Indirizzo Internet Indirizzo fisico Tipo
    107.108.199.1 00-0d-b4-07-27-d6 dinamico
    107.108.199.236 bc-30-5b-bb-da-fe dinamico
    107.108.199.242 18-03-73-a4-15-a3 dinamico
    107.108.199.245 14-fe-b5-ec-fa-33 dinamico
    107.108.199.247 14-fe-b5-ec-fa-46 dinamico
    107.108.199.248 d4-be-d9-b8-32-01 dinamico
    107.108.199.249 bc-30-5b-bb-dd-b7 dinamico
    107.108.199.252 bc-30-5b-bb-db-74 dinamico
    107.108.199.255 ff-ff-ff-ff-ff-ff statico
    224.0.0.2 01-00-5e-00-00-02 statico
    224.0.0.22 01-00-5e-00-00-16 statico
    224.0.0.252 01-00-5e-00-00-fc statico
    239.255.255.250 01-00-5e-7f-ff-fa statico
    255.255.255.255 ff-ff-ff-ff-ff-ff statico

    LAN: Filter devices...
    LAN: 0 devices found.


    CMD: dtc_conf get bh560v2u 0
    USB: 0 devices found.

    TOTAL: 0 devices found.


     How should I proceed to solve this?


  • 0 in reply to Pankaj Kumar
    TI__Mastermind 23525 points

    Did the mezzanine emulator previously work, then stop working, or did it never work?  Do you have another mezzanine emulator that does currently work with your PC and is recognized by windows when you plug in the USB?  Have you tried the second procedure above to try an force "safe mode"?  If it is truly dead and still under warranty, you will need to contact eInfochips and request an RMA# to return it to them.

    Regards,

    Travis

  • 0 in reply to tscheck
    TI__Mastermind 23525 points

    Let me clarify one thing...  The whole EVM will have to be returned, not just the mezzanine emulator.  It needs to be returned to the EVM manufacturer, so if this is a C6678 or C6670 EVM for example, this would be handled by Advantech, not eInfochips. 

    Regards,

    Travis

  • 0 in reply to Pankaj Kumar
    Intellectual 420 points

    I am not sure if it will help but here is what I did to my evm board to make it work. Basically I encountered problem described in this thread and did “Clear Safe Mode” in config utility. After this the config utility stopped detecting my board. So my guess is that not only "Safe Mode" got activated but somehow flash file was also corrupted. To enter safe mode again I plugged  and unplugged power on the board a few times (probably 7 - 10 with around 5 sec delay) until I saw 3 blinking leds. After this the config utility detected the board and I was able to upload the firmware. Everything seems fine since then.

  • 0 in reply to Alexey Naydenov
    TI__Mastermind 23525 points

    Thanks Alexy, that is good to know that the utility doesn't recognize the mezzanine card at all when the flash is fouled.  I appreciate you sharing.

    Regards,

    Travis

  • 0 in reply to Alexey Naydenov
    Intellectual 300 points

    Hello Alexey,

    I was able to correct the problem with your suggestion.

    Thanks a lot to you and Travis for very useful posts.

    Regards,

    Pankaj

     

  • 0 in reply to Pankaj Kumar
    Intellectual 300 points

    Hello Travis,

    We are facing yet another issue for other EVM, with following parameters

    TOTAL: 1 device found.


    CMD: dtc_conf get bh560v2u 0
    addrConf=:55756
    addrIo=:55755
    boardRev=0
    dtcName=none
    epkRev=5.0.161.0
    fpgaRev=0.0
    productClass=XDS560V2
    productName=Blackhawk XDS560v2-USB Mezzanine Emulator
    safeMode=false
    serialNum=08:00:28:32:06:08
    swBuildTime=Mar 14 2011 12:02:08
    swRev=5.0.161.0
    time=2012/08/23 17:55:07
    vendorName=Blackhawk

    I could see that fpgarev and boardrev as zeoros. Even upgrade using the config utility did not help.

    Do you have any suggestion how can I move ahead or program the fpga.

    Regards,

    Pankaj

  • 0 in reply to Pankaj Kumar
    TI__Mastermind 46460 points

    Pankaj,

    The configuration appears to be corrupted.  Have you tried forcing it back into Safe Mode?

    Tom

     

  • 0 in reply to tscheck
    Prodigy 180 points

    I need to re-program the emulator and I followed steps 1 to 7: the results is that I received the following message:

       " ERROR: 14 : remote procedure call failed : failed while storing a file to the DTC : version error : incorrect firmware for this emulator", the file that I tried to programmed is bh560v2_firmware_5.0.161.0. 

    Do you have any suggestions?

     I would like to notice that I cannot perform a "clear Safe Mode", since the procedure goes in a infinite loop.

    Regards

      Massimiliano Bitossi

     

  • 0 in reply to Massimiliano Bitossi
    Expert 1080 points

    Hello Massimiliano Bitossi,

    It looks like the firmware file chosen to reprogram the mezzanine card is the wrong file.

    The first thing I recommend is that you update CCS with the latest Blackhawk emupack.  This will install the latest XDS560v2 firmware files in folder: emulation\Blackhawk\Bh560v2\firmware.  Once done, you will see the file, bh560v2_fw_mezzanine, dated 16 August 2011.

    You can then use the Bh560v2Config utility to reprogram the mezzanine card with that file.

    I can't tell from the post is if the unit will boot into a mode where it enumerates and can be seen by the utility. If that is the case, you may need to force it back into safe mode to regain enumeration with Windows and be able to reprogram.

    You can also contact us directly if you have any problems with the steps outlined here.  Just email our support team at support@blackhawk-dsp.com. 

    Regards,
    Andrew

  • 0 in reply to Ferrari5699
    Prodigy 180 points

    Hello Andrew,

    It is correct the I have a old version of firmware, dated 2010. 

    I tried to upload CCS (my version is  N201105110900, the same as the DVD that I found in the EVM TMDSEVM6678LE), bu no update was found,

    Please, Could you indicate me where I can find the new version of the firmware?

    Regards,

      Massimiliano

  • 0 in reply to Massimiliano Bitossi
    Prodigy 180 points

    More exactly, my CCS version is:

       Version: 5.0.1.201105110900 

        Build id: N201105110900

  • 0 in reply to Massimiliano Bitossi
    Expert 1080 points

    Ok, the original EVM distribution (CCS v5.0.x) may not have included the firmware when it was built.

    Here is the file.  4667.XDS560v2_Mezzanine_Firmware_2011-08-16.zip

    -Andrew

  • 0 in reply to Ferrari5699
    Prodigy 180 points

    Hello, thanks a lot, I have solved the problem immediately updating the firmware with this version.