FLASH-PROGRAMMER: CLI Programmation time most longer than GUI Programmation time

Hi,

One thing that is different is that calling the CLI includes enumerating the emulators connected to your computer.

Another option that will improve speed is to tell the CLI to use 4-pin JTAG (instead of 2-in cJTAG, which is default).
You can do this by adding the -j4 (or --jtag4) option to the end of your command line arguments.

Hope this helps.

TIABO

One thing that is different is that calling the CLI includes enumerating the emulators connected to your computer.
I'm not sure to understand?

You can do this by adding the -j4 (or --jtag4) option to the end of your command line arguments
Waht wire is used in j4?
I can used only
VCC-Pin 5 TMDSEMU
GND-Pin 8 TMDSEMU
TMS-Pin 1 TMDSEMU
TCK-Pin 11 TMDSEMU

Hi,

1. Device enumeration is the detection of emulators and devices connected to your machine.
2. 4-pin JTAG uses these pins: TCK, TMS, TDI, TDO. If you have not routed up TDI and TDO pins to the CC2630 target, you cannot use 4-pin JTAG.

TIABO

Ok so, the only différence is Device enumeration.
can I remove this step? because i give directly soc(XDS-00000000,cc2630)?

One difference that I can think of is device enumeration. There may be others. I don't think you can get around it.

Can you share the file you're trying to program so that I can try reproduce what you're seeing on my side?

You want .out file?

XCMW_v1.0.out, svp.

TIABO

I can't put this file on Internet

How can I see the command used by GUI to made action?

Here a array with timing

I want to have approx Timing test.xlsxGui time

I think that CLI is create for manufacturing process and the time in manufacturing process is very important
With your help, i think that at each call srfprog.exe i loss enumerator time but I don't want check this and i want earn time
Can you help me please

Nicolas,

I do not see the same time difference as you between GUI and CLI.

These tests use an umage that programs all flash sectors of a CC1350 target (which is what I had at hand. It is very similar to CC2630 for the flash programmer (same flash size etc.). I used SmartRF Flash Programmer 2 v1.7.5, the latest version available on TI.com.

In the GUI I used these options: 

• Erase: All unprotected pages
• Program: Entire source file
• Verify: CRC check
• 2-pin vs 4-pin: Configured under the Tool icon

In the CLI I used this command:

2-pin: srfprog.exe -t soc(XDS-L4000007,CC1350) -e -p -v -f c:\cc1350-packet-tx-c5-fill.bin -a 0x0
4-pin: srfprog.exe -t soc(XDS-L4000007,CC1350) -e -p -v -f c:\cc1350-packet-tx-c5-fill.bin -a 0x0 -j4

	CLI	GUI
2-pin cJTAG	11.33 s	11.4 s
4-pin JTAG	4.81 s	5.1 s

Looking at your Excel document, I think you would benefit from pre-processing the image you want to program on the host-side and only run the flash programmer once. It should at least possible to consolidate the "Firmware" and "ID" steps in your document.

The 4 bytes that you read, is that something device-specific that you must store, or do you have that information somewhere else (that is, information you do not have to read from the target)?

TIABO

I'm ask our support frnace to directly have your mail because i can't put on web more information on our project.

But for the moment i think that i have a problem on my PC with USB port because since this morning flash programmer crash many time and i have an other problem with other devices.

Hi, add me as a friend on E2E and we can take it there.

Can you see my private message?