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.

How can nowFlash be used to distinguish RM42 HDK from RM48 HDK both being connected via USB XDS100 Debugger?

Other Parts Discussed in Thread: UNIFLASH

Hello,

we are developing a network of devices build on RM42/RM48 MCUs. Thus, RM48 HDK and RM42 HDK are used simultaneously now.

While flashing the RM48 HDK is done via CCS right now, the RM42 HDK needs use of "nowFlash" as figured out by my colleagues (see

https://e2e.ti.com/support/microcontrollers/hercules/f/312/p/402213/1527689#1527689 ).

Unfortunately, "nowFlash" seems to be unable to distinguish the RM42 HDK from the RM48 HDK when both are connected to the same developer PC.

Since we would prefer a scripted flash process anyway, we investigated using a direct call to "nowFlash.exe" with explicit specification of a board configuration file (e.g. board_tixds100v2_v3_cortex_rmxx.dat). This works as long as only the RM42 HDK is connected. When the RM48 HDK is connected to the PC as well, the target selection via

$ ftdi_ft2232
  usb_vid=0x0403
  usb_pid=0xa6d0

is not unique and the wrong target is selected in our case.

=> Is there some undocumented parameter to specificy the serial number (e.g., TIMCUHDKB) to distinguish several Hercules HDKs with XDS100 debugger? (Note: we already know how to program the HDKs serial number according to our needs).

If there is currently no such feature in "nowFlash", would it be possible to extend "nowFlash" accordingly?

Do you have another proposal for achieving a scripted flashing of RM42 and RM 48 HDKs connected to the same PC?

Regards,

Joachim Eggers

  • Joachim,

    The XDS100v2's can be programmed with unique ID's and you can configure your .CCXML file to open the emulator with the specific ID.
    This will work through UniFlash - which is the replacement for NowFlash. NowFlash is no longer supported. It may have a similar option but I'm not sure where it is.

    For UniFlash - again it's the CCXML file that can contain the specific emulator ID. UniFlash doesn't include a "CCXML Editor" though so you need to create the CCXML's with CCS or if you can figure out how - you can edit the CCXML manually and add the emulator ID.

    There's documentation for this here:
    processors.wiki.ti.com/.../XDS100

    FYI (for others reading this post) there is a similar capability in the XDS110 emulators that are shipping on the newer launchpads. No instructions yet for this - but the utility '<ccs_install>\ccs_base\common\uscif\xds110\xdsdfu.exe' is the tool that can change the serial # to one that is unique - and the command line help explains the switches. We are building all the new launcpads with the same serial #s. There is a tradeoff here - same serial # means same COM port is assigned - which is handy if you have more than 1 launchpad but are only working with one at a time)
  • Dear Anthony,

    thank you very much for your reply.
    Unfortunately you did not reply specifically to my RM42 HDK problem. This HDK can be programmed with "nowFlash" only right now. See the information from your colleagues within ticket e2e.ti.com/.../1527689.

    What I need, is either one of the following solutions:
    - extension of "nowFlash" to be able to specify a selected emulator ID
    - Bugfix in CCS/UniFlash so that we can use this to flash RM42 HDKs successfully (Note: CCS seems to work in this case sometimes but fails if the program to be flashed reaches a certain length that is no longer handled correctly).

    By the way: I have tried my luck with UniFlash before. It seems like that the standalone version (delivered by Uniflash_3.3.0.00058_win32.zip) just installed some XDS550 stuff. The Windows program menu has an empty entry "Texas Instruments/CCS UniFlash" but not other option to get started with UniFlash. Do you have any idea what is going wrong here?

    Regards,
    Joachim
  • Joachim,

    That's unfortunate. I think until the RM42 issue is fixed - the only real workaround is to only have 1 HDK plugged into the PC at a time during programming. -OR- you can use an external emulator for one of the HDKs.

    My colleagues are telling me though that Hercules 6.0.7 fixes the RM42 issue. I haven't tried it myself though - will try to check it out today.