Re: YUHUA XDS510 USB 2.0 Emulator - CCS Troubles

Update #1.
>Emulator seems to connect to the "brand new" board insted the old "tested" one ... bah. The old is not very reliable!
>The strange thing is that it is very slow in accessing registry or memory contents. If I click on a rigister set I immeditely see all values at "?????????" and after some seconds real (?) values appears.
>Load a program is not possible due to verification errors.
>
>Any suggestion?
>
>The soap opera goes on.... Stay tuned! :)
>
>Hi again,
>> I probably succeed to install correctly windows drivers and now device performs the reset via its tool, giving: "SEED USB2.0 XDS510 CARD IS RESET, HARDWARE VERSION 1"
>>
>> I installed SEED drivers for CCS but now I've problems with CCS setup. I tried to connect TWO different boards, both with TMS320C6424 (C64x+) with direct JTAG connection. A board was working and the other is brand new to debug.
>>
>> On Setup program browsing "Available Factory Boards" I choose:
>> - "C64x+" as Family
>> - "SEEDXDS510USB emulator" as Platform
>>
>> List reduces to 4 elements:
>> - C6455 SEEDXDS510USB Emulator with ICEPICK_C
>> - DM6443 SEEDXDS510USB Emulator with ICEPICK_C
>> - DM6446 SEEDXDS510USB Emulator with ICEPICK_C
>> - TCI6482 SEEDXDS510USB Emulator with ICEPICK_C
>>
>> I supposed to choose the first with C6455, because I'm not interfacing to DaVinci or other systems, right?
>> This Pre-Confiugured board has the following description:
>> "One C64x+ CPU connected via a SEEDXDS510USB Emulator set to I/O port 0x240. Automatic with faster 35.0MHz limit. Rising edge allows faster TCLK".
>>
>> Here are the imported tree items(every one is under the preceding):
>> - C6455 SEEDXDS510USB Emulator
>> - TMS320C6455_0
>> - ICEPICK_C_0 (Router)
>> - dsp (Port 0x0)
>> - C64PLUS_0 (Master/slave:N/A - Stop Mode)
>>
>> I Save&Quit and start CCS, receiving the following error message after splash screen:
>> "The port index 0x0 is undefined in icepick xml file".
>>
>> CCS starts anyway but if I try to connect here is the error message:
>> "
>> Error connecting to the target:
>> Error 0x80000240/-1146
>> Fatal Error during: Initialization, OCS,
>> Invalid data was scanned by the emulation controller.
>> Verify the board setup to make sure the scan chain is properly
>> defined.
>> If the setup is correct, then RESET EMULATOR. This will disconnect each
>> target from the emulator. The targets should then be power cycled
>> or hard reset followed by an emureset and reconnect to each target.
>> Sequence ID: 0
>> Error Code: -1146
>> Error Class: 0x80000240
>> I/O Port = 240
>>
>> Board Name: C6455 SEEDXDS510USB Emulator
>> Cpu Name: C6400PLUS_0
>> "
>> If I perform the asked resets the message is the following:
>> "
>> Error connecting to the target:
>> Error 0x80000244/-2131
>> Fatal Error during: Register, Initialization, OCS,
>> Cannot access register at 0x00000000
>> Sequence ID: 0
>> Error Code: -2131
>> Error Class: 0x80000244
>> I/O Port = 240
>>
>> Board Name: C6455 SEEDXDS510USB Emulator
>> Cpu Name: ICEPICK_C_0
>> "
>>
>> When removing power to target board the message is the following:
>> "
>> Error connecting to the target:
>> Error 0x80000240/-171
>> Fatal Error during: Initialization, OCS,
>> This error was generated by TI's USCIF driver.
>>
>> SC_ERR_REG_DETECT_CTLR
>> The wrong controller port value has been used.
>> A controller cannot be detected even though the
>> selected port does match the hardware configuration.
>> The standard 560 ports are 0x0, 0x1, 0x2 and 0x3.
>> The standard EVM ports are 0x0, 0x1, 0x2 and 0x3.
>> The standard DSK ports are 0x378, 0x278 and 0x3BC.
>> The standard 510 ports are 0x240, 0x280, 0x320 and 0x340.
>> Sequence ID: 0
>> Error Code: -171
>> Error Class: 0x80000240
>> I/O Port = 240
>>
>> Board Name: C6455 SEEDXDS510USB Emulator
>> Cpu Name: ICEPICK_C_0
>> "
>> I also tried to apply suggestions of Mike Dunn's blog. Reset commands seems to be executed correctly but JTAG scan commands breaks without chain details, here is the command window output:
>> "
>> C:\CCStudio_v3.3\cc\bin> xdsprobe -f brddat\ccBrd0.dat -i -v
>>
>> -----[Select the controller]-------------
>>
>> This utility has selected an XDS510 class product.
>> This utility will load the adapter 'seedusb2.dll'.
>> This utility will operate on port address '0x0240'.
>> The emulator adapter is named 'seedusb2.dll'.
>> The emulator adapter is titled 'Custom block-mode adapter for use with an XDS510
>> '.
>> The emulator adapter is version '33.0.0.0'.
>> The emulator adapter is using 'Block-Mode'.
>> The controller has a version number of '1' (0x0001).
>> The controller has an insertion length of '16' (0x0010).
>> The local memory has a base address of '0' (0x000000).
>> The local memory has a word capacity of '262144' (0x040000).
>>
>> -----[Perform the scan-path length test on the JTAG IR and DR]---------------
>>
>> This scan-path length test uses blocks of 512 32-bit words.
>> /
>> C:\CCStudio_v3.3\cc\bin>
>> "
>> Has anybody an idea?
>>
>> Pardon for the post length and thanks for your patience...

Imeet the same thing that it is very slow in accessing registry or memory contents. If I click on a rigister set I immeditely see all values at "?????????" and after some seconds real (?) values appears.
Load a program is not possible due to verification errors.
I have checked my circuit,but I do not find the reason.

_____________________________________ Start a New Thread