UNIFLASH: CLI (Linux) -> Failed: Target must be connected before calling the function

Hi Toby,

Thanks for your reply. I just try and it works well without this option.

But I use this as with fresh devices (never flashed) it was not possible to flash without this.

As I don't have fresh device anymore, I can't test it yet but do you think it will still flash without this option ?

Note: Below is the link were we discuss and I receive help for the command line and finally add the --mode noConnectFlash.

Best regards,

Antoine

Hi Antoine,

After chip-erase with Uniflash, the device should effectively become "fresh device".

Maybe before any programming, perform a chip-erase with Uniflash. Then the CLI command should work (the one without "--mode noConnectFlash").

Can you try this out on your current device after a chip-erase and test with and without the option of "--mode noConnectFlash"?

Thanks,
Toby

Hi Toby,

I was able to flash without the --mode noConnectFlash and after a mass erase, thanks.

But what is the difference between CC2640R2F & CC2340R5 that make one requires the --mode noConnectFlash and the other must not have this option ?

Anyway, the issue is fixed. Thank you.

(Here is the thread where I get the --mode noConnectFlash help)

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1340015/uniflash-flash-cc2340r5-using-standalone-command-line/5104103#5104103

Hi Antoine,

For CC2340R5, the boot sequence is such that the core (CM0+) is inaccessible on a blank device until a valid FW is loaded. (Boot sequence described in TRM section "8.1 Device Boot and Programming").
When Uniflash attempts to connect to the blank device without the noConnectFlash, it likely attempts to access the core.

Thanks,
Toby