Debug Port Unlock on Uniflash 3.1 (and error message)

Similar experience here. Our biggest issue has been when a third party has added an ICDI-like solution on their board (which we use) and did not properly disable it. This prevented access to the debug port.

Robert

Amit Ashara said:

Hello PAk,

I have not used this cable so far. But can you check Device Manager is able to interpret it as a Stellaris ICDI. If not then remove the drivers and instead try to point it to the Stellaris ICDI drivers

Regards
Amit

Hello Amit, which FTDI device or IC did you use to unlock Tiva devices? We would like to know so we could check the functionality.

On the other hand Robert,  we would like to provide our tool to our clients to unlock our boards. We don't want to just say that they have to unlock their XXX$$ boards, using a custom made cable to one stellaris. Pretty sad, isn't it

Hello PAk,

I have used the FT2232H which has dual channel (besides the launchpad ICDI). One is used for COM port and another for JTAG

Regards
Amit

Amit Ashara said:

Hello PAk,

I have used the FT2232H which has dual channel (besides the launchpad ICDI). One is used for COM port and another for JTAG

Regards
Amit

Thank you Amit.

That cable features a FT232H which is basically the same but with just one port. I think the issue is with the configuration on the FT_prog app.

Could you provide your template file for JTAG?

Regards

My sadness is in observing the amount of effort expended to avoid standard tools. A side effect of which is to constrain the end user.

If it's worth this effort, it's probably worth exploring private labelled standard tools, which gains you all the benefits of those tools.

Robert

Robert Adsett said:

My sadness is in observing the amount of effort expended to avoid standard tools. A side effect of which is to constrain the end user.

If it's worth this effort, it's probably worth exploring private labelled standard tools, which gains you all the benefits of those tools.

Robert

Just tell me a "standard tool" that allows you to unlock a Tiva chip, which is not a custom wired launchpad....and I am sold!!

J-Link comes to mind. There are others out there I'm sure, but this one has a good reputation and works well for me. We haven't found it necessary to unlock a micro ( cb1 may have) so I can't testify from experience how well that works but the manual mentions it (as quoted earlier).

Robert

Robert Adsett said:

We haven't found it necessary to unlock a micro ( cb1 may have

Your wish - my command, Sir.     Indeed we have - and sadly - that occurred with "vendor assistance/guidance" in our office.   (a past LM3S part)

Other ARM devices (seem) "from my read of other forums" to be more resistant to such, "lock out."    In some cases the dedication of MCU pins to special, known, "Boot methods/mechanisms" frees one from the agony of "lock-out."   I note that our group has (yet) to experience "lock out" - across 4 ARM vendors' devices - beyond that long past, "vendor assisted" incident.

Language IS important - I wonder what is really - and completely - intended by, "Lock-Out?"    What is PAk really saying/meaning - via that term?

Again - the idea of having a client perform such activity - chills this reporter's spine!     (I'd love to read the "exhaustive Risk-Reward analysis/justification.")

Right tool for the Job - but "lock-out" should be avoided...

cb1- said:

Again - the idea of having a client perform such activity - chills this reporter's spine!     (I'd love to read the "exhaustive Risk-Reward analysis/justification.")

Right tool for the Job - but "lock-out" should be avoided...

I think we are in general agreement. One case I can think of where this might occur is a general purpose programming board, all the more reason to use standard tools.

Robert

Amit Ashara said:

Amit Ashara

Hello PAk,

I have used the FT2232H which has dual channel (besides the launchpad ICDI). One is used for COM port and another for JTAG

Regards
Amit

Thank you Amit.

That cable features a FT232H which is basically the same but with just one port. I think the issue is with the configuration on the FT_prog app.

Could you provide your template file for JTAG?

Regards

Hello PAk,

Could you share the xml file for programming?

Regards
Amit

Amit Ashara said:

Hello PAk,

Could you share the xml file for programming?

Regards
Amit

Hello Amit.

Which xml file are you refering to?

regards

Hello PAk,

The settings done in the FTprog can be saved as a xml file

Regards
Amit

Amit Ashara said:

Hello PAk,

The settings done in the FTprog can be saved as a xml file

Regards
Amit

Hello Amit. That is what I would like you to provide me. Could you send me your xml file setup?

Thank you

Hello PAk,

I cannot send any programming file on the forum or via PM. You would have to share yours so that I can cross verify and let you know what needs to be changed.

Regards
Amit