• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 1542 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

BH USB200 + TMS320F28335 prog passord

Georgii Chukhlantsev
Prodigy 50 points

Other Parts Discussed in Thread: TMS320F28335

Hello!
There was a Problem with emulator BH USB200.
Target: TMS320F28335
Used emulators: BH USB200, BH USB2000, bootloader RS232.
Programmer: FlashBurn 4.1
Procedure (using the BH USB200):
1. Erasure procedures, records, verification is successful.
2. Password blocking procedure is successful:

Programming CSM password
  Password 1234,1234,1234,1234,1234,1234,1234,1234
  Task 'PRG_password'
   Task complete
 Running DSP

Process exited with code: 0

3. The user program starts and runs.
4. DSP manually reset signal or power supply, the user program starts again and runs.
5. But, from this point on BH USB200 Emulator you can not communicate with the DSP:

BhFlashBurn.exe -p 0 0 -n -d "tixds560c28x.dvr" -f "LF28XX_BHUSB200.dat" -q- -r -c 30x10 / 2 -u 1234,1234,1234,1234,1234,1234,1234,1234 -e: ff -v -l 1234,1234,1234,1234,1234,1234,1234,1234 "C: \ Program Files \ Blackhawk \ BHFlashburn_v4.1 \ bin \ Flash28xx \ Algorithms \ 28335 \ FlashAPIInterface28335V2_10.out" "D : \ Projects \ my_prog \ 1.7 \ prog_1_7.out "
 Opening driver 'tixds560c28x.dvr', dat-file 'LF28XX_BHUSB200.dat', port 0, target 0
 Connecting to DSP
Error: gti_api :: connect failed, code -1015
(Error -1015 @ 0x0)
Internal error: Invalid error code. Restart the application. If error persists, please report the error.
(Emulation package 5.0.681.0)


Process exited with code: 2

If you do not block the DSP password, no such problem. Password (only in BH USB200) leads to a problem of connection.

Another emulyator (BH USB2000 or serial programming via the built-in RS232 bootloader) successfully binds to a DSP and unlocks it the same password. After that BH USB200 can work with him again, until the DSP will not be blocked by a password BH USB200.
If the DSP block through BH USB2000, a problemmy not.

What can be wrong?

  • 0
    TI__Mastermind 32995 points
    Hi Georgii,

    If the device is locked and running from secure memory, you will not be able to connect the emulator. You will need to hold the device in reset or connect the device when it is running/waiting in unsecure memory.

    Does the device have a Wait Boot option you can reset to so that the emulator has time to connect?

    sal
  • 0 in reply to Sal Pezzino
    Prodigy 50 points

    Hi sal,

    The problem is partially solved.
    The document Literature Number: SPRS439G June 2007-Revised February 2010 on page 44 Table 3-6. Boot Mode Selection. In my project DSP is always working in the Jump to Flash mode (MODE F). For firmware via RS232 DSP boot loader runs in the SCI-A boot mode (MODE E). I have completed the above procedure with the emulator BH USB200 mode (MODE E):
    - Start mode (MODE E);
    - Programmed user program and password (BH USB200);
    - Start mode (MODE F). Problems with communication password after blocking no longer exist. Everything is working.

    One moment, every time the mode for programming change is not convenient and in the finished product takes a long time. Are there any other ways? BH USB2000 worked in the mode (MODE F).

  • 0 in reply to Georgii Chukhlantsev
    TI__Mastermind 32995 points

    The question is unclear to me. Can you please clarify the problem and your question?

    sal

  • 0 in reply to Sal Pezzino
    Prodigy 50 points

    I am sorry for my English, I write through the translator. 
    Earlier for work with DSP TMS320F28335 I used the BH USB2000 emulator. Everything was good. 
    Now I started to use the BH USB200 emulator and found a problem. After wright of the password and reset DSP, the emulator cannot be connected to DSP: Error: gti_api:: connect failed, code-1015. 
    I program DSP in the following sequence: 
    unlook, erasing, programming, verify, look, manual reset DSP. (full programming) 
    If to use BH USB 200, in such a way to program DSP it is possible only once. 
    The following attempt of programming leads to a mistake: Error: gti_api:: connect failed, code-1015. 
    I found 3 ways of restoration of communication of the BH USB 200 emulator with this DSP: 
    1. full programming of this DSP using BH USB 2000. 
    2. Unlook and programming of this DSP using bootloader in SCI-A boot mode (CodeSkin and USB -> UART converter) 
    3. full programming of this DSP using BH USB 200 in SCI-A boot mode! 
    I will specify to switch DSP in SCI-A boot mode: pull down GPIO84 and pull up GPIO85, GPIO85, GPIO85 and reset DSP, according to SPRS439G. In a usual mode, pull up all this GPIO - Jump to Flash mode. 
    Now procedure of programming of New DSP, using BH USB200, looks as follows: 
    1) the first programming of DSP - full programming of this DSP using BH USB 200; 
    2) all subsequent updatings of the program: 
    a. switch DSP in SCI-A boot mode; 
    b. full programming of this DSP using BH USB 200; 
    c. switch DSP in Jump to Flash mode; 
    At such sequence of actions of Error code-1015 does not arise. 
    I can carry out it at myself on a table, but in a final product there is no access to the lines GPIO85, GPIO85, GPIO85, GPIO84. 
    On how many I understand at switch DSP in SCI-A boot mode DSP running/waiting in unsecure memory therefore BH USB 200 is possible to be connected. Strange, BH USB 2000 works in any case. 
    If initially to exclude the operation "look" from sequence of programming, the BH USB200 emulator works without problems. But I should use “look” surely. 
    Question: how, full programming using BH USB200 without changing boot mode and not to receive error code-1015? I will specify, full programming using BH USB2000 never was such problem!

  • 0 in reply to Georgii Chukhlantsev
    Prodigy 50 points

    I was mistaken concerning BH USB2000. With it too there is a similar problem (Error: gti_api :: connect failed, code -233). It decides so: 
    - Before full programming (unlook, erasing, programming, verify, look, manual reset DSP) it is necessary to give reset signal on DSP 
    - To start programming process. BH USB2000 connect with DSP, finds DSP reset, waits. 
    - To remove reset signal from DSP 
    - BH USB 2000 begins programming process. 
    With BH USB200 this method does not work. switch DSP in SCI-A boot mode for the period of programming and the subsequent switch DSP in Jump to Flash mode works only.
    I did not check other boot mode. 

  • 0 in reply to Georgii Chukhlantsev
    TI__Mastermind 32995 points
    The device needs to be in a WAIT BOOT mode for you to connect to a locked device via JTAG. You may also be able to connect the JTAG with the SCI Boot mode option.

    What boot mode is the device in when you are trying to connect to the device with JTAG?

    sal
  • 0 in reply to Sal Pezzino
    Prodigy 50 points
    The device is in the Jump to Flash mode (MODE F) when I connect JTAG. 
    In the SPRS439G document it is written: 
    When initially debugging a device with the password locations in flash programmed (i.e., secured), the 
    emulator takes some time to take control of the CPU. During this time, CPU will start running and may 
    execute an instruction that performs an access to a protected ECSL area. If this happens, ECSL will 
    trip and cause the emulator connection to be cut. Two solutions to this problem exist: 
    1. The first is to use the Wait-In-Reset emulation mode, which will hold the device in reset until the 
    emulator takes control. The emulator must support this mode for this option. 
    2. The second option is to use the “Branch to check boot mode” boot option. This will sit in a loop and 
    continuously poll the boot mode select pins. The user can select this boot mode and then exit this 
    mode once the emulator is connected by re-mapping the PC to another address or by changing the 
    boot mode selection pin to the desired boot mode. 

    I think the BH-USB-2000 emulator supports Wait-In-Reset emulation mode, and the BH-USB-200 emulator does not support therefore switch a device in other Boot Mode, for example in SCI-A is necessary.