• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 102 subscribers
  • Views 255 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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:

AM68A: USB Device, DFU FW update thought USB to eMMC

J722SXH01EVM: Official TI based dfu-util usb driver

Evan Williams
Intellectual 340 points
Part Number: J722SXH01EVM
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi,

I have J722S flashing its on-board EMMC via dfu-util, but the process is not refined for an end-user/customer in my opinion.
On windows machines, the driver does not install by default, so requires a user to manually re-install the driver twice. Once each time a new USB port is used and also again the first time the r5 core is flashed with tiboot3.bin.
It's also awkward that any dfu driver can be used, for example I can use the stellaris TI driver. However, this messaging is confusing to end-users, because this is not a stellaris product.
I've also found I can use the particle drivers, which is convenient, because that installation also includes dfu-util and adds dfu-util to the path. However this product is also not particle hardware.

The TI J722S documentation says to use a "dfu driver which is outlined by USB org."
Does TI have a branded installation package we could recommend to end-users that packages an automatically installing dfu usb driver and dfu-util which is added to the path by default?
Is there a location we could formally request this type of software?


Process flow on Windows today:
Install Particle, or Stellaris TI drivers or others.
Manually download dfu-util or use Particle's old version of dfu-util included in it's package.
Manually "update driver" when it is not appropriately recognized by Windows.
Start the flashing process.
Manually "update driver" -again- when the r5 core is loaded and it's rediscovered again as a dfu device.
Power cycle the device so the script can run from the start.
Start the flashing process again.
Finish flashing.


The process flow we would like to see is:
Install TI branded package like Uniflash which should add dfu-util to Windows path and automatically associate the dfu devices to a TI branded dfu driver, like the stellaris driver.
Start flashing
Finish flashing

  • 0
    TI__Guru* 96375 points

    Hi Evan,

    What SDK are you using? Please provide the reference to the SDK documentation reference you are talking about here.

    I am not familiar with a Particle.

    The TI SDKs are developed using Ubuntu machines (Windows is very slow for compilation in general and simply not fast enough for our development purposes), and only a few components are supported on Windows as well. Our general recommendation is to be use an Ubuntu machine for development, but it is understood that not every one wants to use a Linux-based machine.

    regards

    Suman

  • 0 in reply to Suman Anna
    TI__Mastermind 39202 points

    HI Evan,

    For Windows, our suggestion is to follow the below steps:

    1. Download the dfu-util tool (dfu-util-0.6-win32.zip.bz2) from http://dfu-util.sourceforge.net/releases/ and unzip to some folder (say c:\dfu) 
    2. Download the zdaig application (zadig_v2.0.1.160.7z) from https://sourceforge.net/projects/libwdi/files/zadig/ and unzip and execute zdaig application. Install winUSB driver.
    3. Connect the EVM (running DFU) to Windows PC via USB cable. Windows host will detect the EVM as "DFU Gadget". 
    4. Open the command prompt and go to the directory containing the dfu-util.exe (say c:\dfu folder) to use the tool.

    To use the driver,

    • To list all the DFU interfaces:
    c:\dfu> dfu-util –l
    • Flashing the SBL file to a particular memory identified by the <alt_number>
    c:\dfu> dfu-util -c 1 -i 0 -a <alt_number> -D <file-name>

    Example:   sudo dfu-util -c 1 -i 0 -a bootloader -D tiboot3.bin

    Thanks.

  • 0 in reply to Praveen Rao
    Intellectual 340 points

    Hi Praveen,

    I appreciate the response.

    Using zadig, I see the Stellaris driver is really just the the WinUSB driver:


    This tool would definitely make the installation of the driver easier, but still is not very polished.
    If we can automate the WinUSB driver installation in our own tool, this type of solution may be palatable.

  • 0 in reply to Evan Williams
    TI__Mastermind 39202 points

    Hi Evan,

    Thanks for the note. As previously noted by , our general recommendation is to use an Ubuntu machine for development. 
    No update or enhancement is planned for Windows' handling of the USB-DFU driver. The steps shared are the best option that we can suggest.

    Thanks.