• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 124 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

UNIFLASH: UniFlash for Large Scale Production

IWR1843: Production flashing in Uniflash

Ryan T
Expert 3161 points
Part Number: IWR1843
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi Team, 

My customer is attempting to develop a program for production flashing using Uniflash--they're using the Python CLI instructions found in the UniFlash Quick-start guide.

One problem they're facing is that with each new device they connect through JTAG, the new device gets assigned a different COM port. They're wildly different depending on device. Is there a way around this? Is there a more programmatic way of solving this than using the Windows Device manager to manually change the COM port? 

Best regards,

-RT

  • 0
    TI__Mastermind 20451 points

    Hi Ryan, 

    For mass production, some customers will choose to use a gang programming setup programming the flash in batches before final assembly. Uniflash does have a CLI option for flashing but there are surely limitations as they have noticed. 

    Regarding the specific issue they are having now, when you say "wildly different", what do you mean exactly? If they are running windows I would assume it's just a different number, right? If they just need to find out what the com port name is, we have some code in the python visualizer from the radar toolbox which automatically finds the com port number for a connected device. Maybe they could refer to/use that ?

    It is in {RADAR_TOOLBOX}\tools\visualizers\Applications_Visualizer\common\gui_core.py

    Just search for list_ports

    Best Regards,

    Josh