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.

What is strict procedure to follow in case of failure in JTAG connection

Other Parts Discussed in Thread: AM1808, OMAP-L138

Hello,

It's extremely frustrating using CCS on Window 7.

Recently I had to upgrade from Win-XP to Win-7, then I have too too much failure in JTAG connection.

Everything is the same, but Win-7.

Once in a while I had that problem in Win-XP, then I just try to plug/unplug JTAG, and/or recycle power to the board, then the problem went away.

Now I have to do the same, but many times 5~10 times, pulug/unplug JTAG at the board, plug/unplug USB at the hub, recycle power to the board, close/open CCS, ...

It almost happen every time I use JTAG.

I'm using CCS-5.4 for AM1808/OPMAP-L138

It's just a nightmare once using it for years to prepare for a new product and now ready for production, all sudden all kind of problems appear !!!

Any idea ?

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\DKN\AppData\Local\.TI\1435909456\
    0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Apr  1 2013'.
The library build time was '23:55:08'.
The library package version is '5.1.73.0'.
The library component version is '35.34.40.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 512 32-bit words.

The test for the JTAG IR instruction path-length failed.
The many-ones then many-zeros tested length was 6816 bits.
The many-zeros then many-ones tested length was 181 bits.

The test for the JTAG DR bypass path-length failed.
The many-ones then many-zeros tested length was 2383 bits.
The many-zeros then many-ones tested length was 720 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 68.8 percent.

The JTAG IR Integrity scan-test has failed.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 512 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 69.1 percent.

The JTAG DR Integrity scan-test has failed.

[End]

So, my question is

1) Was CCS-5.4  tested on Win-7, both 32-bit & 64-bit ?

2) What is the strict procedure to foolow once the problem occurs ?

  • Hi Duy-ky,

    Duy-Ky Nguyen88210 said:
    1) Was CCS-5.4  tested on Win-7, both 32-bit & 64-bit ?

    Sharing my personal experience CCS v5.4 was bit unstable on Win-7 but upgrading to CCS v5.5 solved all the instabilities.

    Regards,

    Gautam

  • Hi Gautam,

    I already had CCS-5.5 installed and it's used for Beaglebone and I have quite too much trouble with it too !!!

    I still need some kind of guide-line on the procedure to eliminate the connection problem, one it happens.

    For now, I have to do all I can do at random order : plub/unplug JTAG at the board, plug/unplug USB at the hub, recycle power, close-open CCS. Too many, so is there any order to follow ?

    I have to say that CCS-Eclipse is very powerful, I believe there're a lot of features I never use them

    Why TI didn't reserve that effort for fancy feature to make the basic features work properly! It's just a bad technical approach!

    Thanks for your response.

    ~Duy-Ky

  • Hi Gaulam,

    I'm using CCS-5.5 and still get the same frustrating problem!!!

    It's extremely frustrating

    Hi TI Employee,

    Look at the capture below to see what happen to JTAG under CCS-5.5 running on Win-7 64-bit

    Did TI test it seriously on Win7 64bit ??????????????????????????

    [Start]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\DKN\AppData\Local\.TI\617458536\
        0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioserdesusb.dll'.
    The library build date was 'Aug 20 2013'.
    The library build time was '22:56:19'.
    The library package version is '5.1.232.0'.
    The library component version is '35.34.40.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the FTDI FT2232 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for FTDI FT2232 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[The log-file for the JTAG TCLK output generated from the PLL]----------

    There is no hardware for programming the JTAG TCLK frequency.

    -----[Measure the source and frequency of the final JTAG TCLKR input]--------

    There is no hardware for measuring the JTAG TCLK frequency.

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 512 32-bit words.

    The test for the JTAG IR instruction path-length failed.
    The many-ones then many-zeros tested length was 19 bits.
    The many-zeros then many-ones tested length was -16384 bits.

    The test for the JTAG DR bypass path-length failed.
    The JTAG DR bypass scan-path is stuck-at-ones.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 2, skipped: 0, failed: 1
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 2
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 3
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 4
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 5
    Some of the values were corrupted - 83.3 percent.

    The JTAG IR Integrity scan-test has failed.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 2, skipped: 0, failed: 1
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 2
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 3
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 4
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 5
    Some of the values were corrupted - 83.3 percent.

    The JTAG DR Integrity scan-test has failed.

    [End]

  • Hi Duy-Ky,

    Sorry for all your struggles with CCS. Unstable emulation errors are always the most difficult to debug. There is no specific procedure or set of steps that will work for all. It really varies quite a bit on the environment.

    I see that the basic JTAG connectivity test is failing often. It means that the basic JTAG connection is unstable. The first thing to try is to update your emulator pack version. You are using 5.1.232.0. The latest is 5.1.507.1. You can update the emulator pack via the CCS update manager

    If that fails to help at all, check your USB cable and also check for any potential interference in the environment that can impact the signal integrity. This is a common cause of unstable JTAG connections.

    CCS is certainly tested on Windows 7-64. It is the primary OS that we use to test CCS with and all the CCS developers use Window 7-64 as their primary OS on their workstations (including me).

    hope this helps

    ki

  • Hi Ki,

    I may have some kind of conclusion, now

    1) Having done all kind of trials & errors, what I found was

       1.1) Unplug the JTAG from the board

        1.2) Recycle the power

       1.3) Plub back in the JTAG

    So, the JTAG should be hot-plugged!!! Only this way it gives me the best chance to clear "bad connection error"

    2) Recently I had some wierd problem with Win7-64 in some cases, but the outstanding case is to install "7-zip", it does not give me "right click menu" where to select what zip to use. So I install Win-7 32bit, so far JTAG behaves fine as in Win-XP

    3) Window7-64 fails to compile run-time library for AM335x-starterware with example bootloader. But it's fine on WinXP and 32-bit Ubuntu Linux. I'm using 32-bit Ubuntu Linux as I'm using only 32-bit MCU.

    So, my conclusion is it's wise not to use Windows-7 64-bit  at all !?!?

    Thanks for your response, Ki

    Regards,

    ~Duy-Ky

  • Duy-Ky Nguyen88210 said:
    So, the JTAG should be hot-plugged!!! Only this way it gives me the best chance to clear "bad connection error"

    What kind of emulator are you using? It looks like an XDS100. Are you using a custom board?

    Duy-Ky Nguyen88210 said:
    2) Recently I had some wierd problem with Win7-64 in some cases, but the outstanding case is to install "7-zip", it does not give me "right click menu" where to select what zip to use. So I install Win-7 32bit, so far JTAG behaves fine as in Win-XP

    7-zip is just a freeware zip utility. I'm not sure what problem you are referring to here and how it impacts the JTAG behavior

    Duy-Ky Nguyen88210 said:
    3) Window7-64 fails to compile run-time library for AM335x-starterware with example bootloader. But it's fine on WinXP and 32-bit Ubuntu Linux. I'm using 32-bit Ubuntu Linux as I'm using only 32-bit MCU.

    What error are you seeing? I was able to build the bootloader example in my AM335x StarterWare 2.0.1 installation successfully with CCSv5.5. This is on my Win 7-64 laptop.

    Duy-Ky Nguyen88210 said:
    So, my conclusion is it's wise not to use Windows-7 64-bit  at all !?!?

    This is the main OS that most people in TI use right now so I would certainly disagree. If there is any OS that the majority of SW is tested with, it would be Win 7-64. There is certainly something strange with your Win 7-64 environment.

  • 1) I've been using XDS100v2 on the board for the last 2 years as it's one of our new product with 1 AM1808 and 2 OMAP-L138, so 3 ARM core and 2 DSP cores in series.

    2) 7-Zip relates indirectly to JTAG problem as I have a serious JTAG problem on Win 7-64. Now Win7-32 and Win7-64 behave totally differently to 7-zip installation. In addition, 7-zip is the only tool to unzip image to update Debian Linux for BeagleBoard. It's freeware, but unable to use WinRAR  for this job!!!

    3) Below is the capture to compile "bootloader from AM335x-Starterware". I'm using Win7 Ultimate 64-bit on pretty new DELL-9010 with 8 GB RAM. There's no error using WinXP and Linux

    BTW, as you did compile bootloader from this starterware, I'm wondering if you're able to load and debug BeagleBoard. I'm not able to do it using on-board JTAG on original BeagleBone (BeagleBone White)

    Thanks, Ki

    ~Duy-Ky
    **** Build of configuration Debug_MMCSD for project boot ****

    "C:\\TI\\5_5\\ccsv5\\utils\\bin\\gmake" -j 4 -s -k all
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/bl_copy.c'
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/bl_hsmmcsd.c'
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/armv7a/cgt/bl_init.asm'
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/bl_main.c'
    'Invoking: ARM Compiler'
    'Invoking: ARM Compiler'
    'Invoking: ARM Compiler'
    'Invoking: ARM Compiler'
    "../../../../../../../include/hw/hw_hs_mmcsd.h", line 102: warning #1557-D: white space between backslash and newline in line splice ignored
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/armv7a/cgt/bl_init.asm'
    ' '
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/armv7a/am335x/bl_platform.c'
    'Invoking: ARM Compiler'
    "../../../../../../../include/hw/hw_cm_cefuse.h", line 72: warning #1557-D: white space between backslash and newline in line splice ignored
    "../../../../../../../include/hw/hw_cm_device.h", line 71: warning #1557-D: white space between backslash and newline in line splice ignored
    "../../../../../../../include/hw/hw_cm_dpll.h", line 84: warning #1557-D: white space between backslash and newline in line splice ignored
    "../../../../../../../include/hw/hw_cm_gfx.h", line 76: warning #1557-D: white space between backslash and newline in line splice ignored
    "../../../../../../../include/hw/hw_cm_mpu.h", line 72: warning #1557-D: white space between backslash and newline in line splice ignored
    "../../../../../../../include/hw/hw_cm_per.h", line 139: warning #1557-D: white space between backslash and newline in line splice ignored
    "../../../../../../../include/hw/hw_cm_rtc.h", line 72: warning #1557-D: white space between backslash and newline in line splice ignored
    "../../../../../../../include/hw/hw_cm_wkup.h", line 125: warning #1557-D: white space between backslash and newline in line splice ignored
    "../../../../../../../include/hw/hw_control_AM335x.h", line 335: warning #1557-D: white space between backslash and newline in line splice ignored
    "../../../../../../../include/hw/hw_emif4d.h", line 116: warning #1557-D: white space between backslash and newline in line splice ignored
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/bl_copy.c'
    "../../../../../../../include/hw/hw_gpmc.h", line 122: warning #1557-D: white space between backslash and newline in line splice ignored
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/bl_main.c'
    "../../../../../../../include/hw/hw_watchdog.h", line 91: warning #1557-D: white space between backslash and newline in line splice ignored
    ' '
    "../../../../../../../include/hw/hw_hsi2c.h", line 104: warning #1557-D: white space between backslash and newline in line splice ignored
    ' '
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/system_config/armv7a/cache.c'
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/system_config/armv7a/cgt/cp15.asm'
    'Invoking: ARM Compiler'
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/bl_hsmmcsd.c'
    'Invoking: ARM Compiler'
    ' '
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/system_config/armv7a/am335x/device.c'
    'Invoking: ARM Compiler'
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/system_config/armv7a/cgt/cp15.asm'
    "../../../../../../../include/hw/hw_control_AM335x.h", line 335: warning #1557-D: white space between backslash and newline in line splice ignored
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/system_config/armv7a/cache.c'
    ' '
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/third_party/fatfs/port/fat_mmcsd.c'
    ' '
    'Invoking: ARM Compiler'
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/third_party/fatfs/src/ff.c'
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/system_config/armv7a/am335x/device.c'
    'Invoking: ARM Compiler'
    ' '
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/bootloader/src/armv7a/am335x/bl_platform.c'
    'Building file: D:/__AM335x/AM335X_StarterWare_02_00_01_01/system_config/armv7a/mmu.c'
    ' '
    'Invoking: ARM Compiler'
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/third_party/fatfs/port/fat_mmcsd.c'
    ' '
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/system_config/armv7a/mmu.c'
    ' '
    'Finished building: D:/__AM335x/AM335X_StarterWare_02_00_01_01/third_party/fatfs/src/ff.c'
    ' '
    'Building target: ../../../../../../../binary/armv7a/cgt_ccs/am335x/beaglebone/bootloader/Debug_MMCSD/boot.out'
    'Invoking: ARM Linker'
    <Linking>
    warning #10366-D: automatic library build: using library "C:\TI\5_5\ccsv5\tools\compiler\arm_5.1.1\lib\rtsv7A8_A_le_eabi.lib" for the first time, so it must be built.  This may take a few minutes.
      -->  error: '*.obj
    ' not found
    gmake.exe[1]: *** [library] Error 1
    >> ERROR: mklib: gmake error during rtsv7A8_A_le_eabi.lib build
    warning #10207-D: automatic RTS selection:  resolving index library "libc.a" to "C:\TI\5_5\ccsv5\tools\compiler\arm_5.1.1\lib\rtsv7A8_A_le_eabi.lib", but "C:\TI\5_5\ccsv5\tools\compiler\arm_5.1.1\lib\rtsv7A8_A_le_eabi.lib" was not found


     undefined        first referenced                                                                                   
      symbol              in file                                                                                        
    >> Compilation failure
     ---------        ----------------                                                                                   
     __TI_auto_init   ./bl_init.obj                                                                                      
     __aeabi_uidivmod ./ff.obj                                                                                           
     __stack          ./bl_init.obj                                                                                      
     memcmp           ./ff.obj                                                                                           
     memcpy           ./ff.obj                                                                                           
     memset           ./ff.obj                                                                                           
     strcmp           ../../../../../../../binary/armv7a/cgt_ccs/am335x/beaglebone/platform/Debug/platform.lib<board.obj>
     strncmp          ../../../../../../../binary/armv7a/cgt_ccs/am335x/beaglebone/platform/Debug/platform.lib<board.obj>

    error #10234-D: unresolved symbols remain
    error #10010: errors encountered during linking; "../../../../../../../binary/armv7a/cgt_ccs/am335x/beaglebone/bootloader/Debug_MMCSD/boot.out" not built
    gmake: *** [../../../../../../../binary/armv7a/cgt_ccs/am335x/beaglebone/bootloader/Debug_MMCSD/boot.out] Error 1
    gmake: Target `all' not remade because of errors.

    **** Build Finished ****

  • Duy-Ky Nguyen88210 said:
    1) I've been using XDS100v2 on the board for the last 2 years as it's one of our new product with 1 AM1808 and 2 OMAP-L138, so 3 ARM core and 2 DSP cores in series.

    Ok. Custom board with external XDS100v2?

    Duy-Ky Nguyen88210 said:
    2) 7-Zip relates indirectly to JTAG problem as I have a serious JTAG problem on Win 7-64. Now Win7-32 and Win7-64 behave totally differently to 7-zip installation. In addition, 7-zip is the only tool to unzip image to update Debian Linux for BeagleBoard. It's freeware, but unable to use WinRAR  for this job!!!

    Yeah I used to use WinRAR also. It supported most zip formats. I guess the debian linux zip is some strange zip format

    Duy-Ky Nguyen88210 said:
    3) Below is the capture to compile "bootloader from AM335x-Starterware". I'm using Win7 Ultimate 64-bit on pretty new DELL-9010 with 8 GB RAM. There's no error using WinXP and Linux

    Duy-Ky Nguyen88210 said:
    >> ERROR: mklib: gmake error during rtsv7A8_A_le_eabi.lib build

    The building of the rts lib failed. Why this happened I don't know. But i will attach the one I built (with cgt 5.1.1) so you can use it while I investigate.

    2330.rtsv7A8_A_le_eabi.zip

    Duy-Ky Nguyen88210 said:
    BTW, as you did compile bootloader from this starterware, I'm wondering if you're able to load and debug BeagleBoard. I'm not able to do it using on-board JTAG on original BeagleBone (BeagleBone White)

    Yes, no problems at all. I built it with CCSv5.5, ARM CGT 5.1.1 and loaded on to my beaglebone white using the onboard XDS100 emulator. This is also Windows 7-64 bit laptop.

    Thanks

    ki

  • FYI: i built the Release_MMCSD configuration because StarterWare ships with the release libraries of utils.lib, libmmcsd.lib, drivers.lib, platforms.lib. It doesn't ship with the debug versions (why, I don't know - you can ask Sitara team) so building the Debug_MMCSD configuration will fail unless you build debug versions of those libraries yourself first.

  • Hi Ki,

    1) In the link below, you'll find the info how to update BB (BeagleBone) Linux with zipped XZ image and only 7-ZIP can handle it properly, while WINRAR gives option tp ZIP, not UNZIP!!!

    http://beagleboard.org/getting-started

    2) In connecting USB for onboard JTAG to BB-W (BeagleBone White), the "SUBARCTIC" keeps come and go in the Device Manager. Did you experience this problem ? I believe it's the root cause I'm not able to have successful JTAG to BB-W

  • Duy-Ky Nguyen88210 said:

    1) In the link below, you'll find the info how to update BB (BeagleBone) Linux with zipped XZ image and only 7-ZIP can handle it properly, while WINRAR gives option tp ZIP, not UNZIP!!!

    http://beagleboard.org/getting-started

    Ok i'll take your word for it. We are not allowed to use WinRAR here anyway so I can't try myself.

    Duy-Ky Nguyen88210 said:
    2) In connecting USB for onboard JTAG to BB-W (BeagleBone White), the "SUBARCTIC" keeps come and go in the Device Manager. Did you experience this problem ? I believe it's the root cause I'm not able to have successful JTAG to BB-W

    You mean this, right?

    Yeah it is very annoying. But it doesn't prevent me from connecting to the device.

    Did you install the latest FTDI drivers (mentioned in step 2 of the url your gave me)?

    ki

  • Hi Ki,

    It is!

    I've just installed the latest FTDI driver to make sure and updates to the latest Emulatror, but still have connection problem

    CortxA8: Trouble Writing Memory Block at 0x80018eb4 on Page 0 of Length 0x50: (Error -2130 @ 0x80018EB4) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.232.0)
    CortxA8: GEL: File: F:\__AM335x\_BB_01\_SD_MMC_2\Debug\_SD_MMC_2.out: Load failed.

    1) Do you have any SD card in slot ?

    2) What GEL file are you using ?

    Thanks, Ki

    ~Duy-Ky

  • Duy-Ky Nguyen88210 said:
    1) Do you have any SD card in slot ?

    No

    Duy-Ky Nguyen88210 said:
    2) What GEL file are you using ?

    ..\..\emulation\boards\beaglebone\gel\beaglebone.gel

    I've attached the ccxml file I am using:

    5822.beaglebone.ccxml

    What rev is your beaglebone?

    And are you trying to connect to a target running linux?

  • IT WORKS!!! Your CCXML file really works great, Ki!!!

    It's unbelievable, I've been struggling long hours for many days and wrongly thought the key point is GEL file, now it turns out the CCXML is the key factor! It took me a big surprise.

    Please update this valued info to the forum to make sure nobody in pain due to the missing of this info

    I have both BB-Black and BB-White. I had BB-Black first and ran into problem where I'm not able to do set pin mux in  my SPI driver. The only way to I could set pin mux is to stop u-boot and set pinmux before boot the kernel!!! I wish I could find some spare time to use CCS to debug U-Boot and kernel.

    Thats's why I bought BB-White to debug using Starterware as I'm quite familiar with AM18 / OMAP starterware

    Thanks so so much for your very excellent support, Ki!!

    All the Best,

    ~Duy-Ky

  • Glad to hear it is working now!

    Can you share your ccxml file? I'm curious what your settings were. I just used the default beaglebone settings in my ccxml file.

    Duy-Ky Nguyen88210 said:
    I wish I could find some spare time to use CCS to debug U-Boot and kernel.

    If you ever do get that time, here are some links that may be useful (of course for your BB-Black you'll need to solder JTAG header on the board (P2) ):

    http://processors.wiki.ti.com/index.php/U-boot_Debug_in_CCSv5

    http://processors.wiki.ti.com/index.php/CCS_Modules_Library#Linux_Debug

    thanks

    ki

  • 4263.5822.beaglebone.rarHi Ki,

    I just use the CCXML you sent me via the link "5822.beaglebone" in the previous post

    I select the gel file "beaglebone.gel" from AM335x-Starterware for the core "ARM Cortex"

    Somehow, this CCXML file takes over the MCU control while it's looking for "serial boot" using X-MODEM protocol. If we connects tera-term to serial port, we can see "C" keeps displayed while X-MODEM hand-shake for the boot. I belive that accounts for "SUBARCTIC"

    Before, in order to load, I had to fool it by creating an SD Card with boot-loader to hold the MCU, but it's just temporarily while waiting for a real solution, and you provided me that solution

    I'd like to use BB-White due to its on-board JTAG for debugging and use BB-Blk just for Linux. I just got it to work with all network supports, like NFS, Telnet and even Samba. Now I'm able to looking around BB filesystem from my PC, it' a lot of fun. I even to use it as  SVN server (SubVersion) using external HDD for file storage

    Thanks, again, for your outstanding support, Ki. it's greatly appreciated

    ~Duy-Ky

    PS, I had to zip the CCXML for the attach as it original ext "CCXML" is not allowed