Linux: Use uniflash cli in combination with the ccfg option "lock debug interface"

Thomas Randl

Other Parts Discussed in Thread: UNIFLASH, CC2640

Tool/software: Linux

Hi,

I have a problem flashing my device with the uniflash cli on ubuntu.

I am able to flash the data, without the option "Lock debug interface", but I need to lock the debug interface after flashing my files.

When I do so, I get the following error text: "Cortex_M3_0: File Loader: Verification failed: Values at address 0x0001FFE6 do not match Please verify target memory and memory map."

I think, that this error occurs, because the verification can not acces the data over the locked connection.

Is there any way to lock the connection over the cli after flash and verify are finished?

Thank you

over 6 years ago

0 Biser Gatchev-XID over 6 years ago

TI__Guru**** 393215 points

Please post what device you are trying to flash.

0 Thomas Randl over 6 years ago in reply to Biser Gatchev-XID

Prodigy 70 points

I am trying to flash a CC2640

0 Thomas Randl over 6 years ago in reply to Thomas Randl

Prodigy 70 points

Sorry to bother you, but I really need an answer to my problem, since I have to finish a Project with this device.

0 Seong Kim over 6 years ago in reply to Thomas Randl

TI__Mastermind 46181 points

Thomas,

If you want to lock the debug interface, trying using:
srfprog -t lsidx(0) -w ccfg(ldbg)

Or if you want to do it together with programming a file, try using:
srfprog -t lsidx(0) -p -f "file_name.hex" -c ldbg

BR,
Seong

0 Thomas Randl over 6 years ago in reply to Seong Kim

Prodigy 70 points

Seong,

Thank you for your reply on my problem.

The problem I see here is, that I need to use the uniflash tool, because I am on an linux environment.
As far as I know the srfprog command is from the Flash Programmer 2 Tool, which is only available for windows.

Thomas

0 Seong Kim over 6 years ago in reply to Thomas Randl

TI__Mastermind 46181 points

Hey Thomas,

I apologize for the delay but I am still looking into this. I'll let you know once I get some answers.

In the meantime, can you confirm if you are configuring your device in the recommended order shown below?

Thanks,
Seong

0 Seong Kim over 6 years ago in reply to Seong Kim

TI__Mastermind 46181 points

Thomas,

The flash address points to CCFG, so I guess what happens here is that Uniflash sets the appropriate lock bits in CCFG. This causes a misalignment between the original flash image and what is read back from the chip which again triggers the error message.

An alternative way to do this, is to set the CCFG values properly before programming. This will lock the flash, but not cause the verification failure.

Hope this helps,
Seong

Bluetooth®︎

Bluetooth forum

Linux: Use uniflash cli in combination with the ccfg option "lock debug interface"