• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 31 subscribers
  • Views 695 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.

LM Flash utility and two demo boards?

Lubomir Bogdanov1
Intellectual 865 points

Hi, guys!

Is there any way to program two evaluation boards on one computer with the LM Flash utility?

I have EK-LM4F232 and EK-LM3748. Even though I'm selecting the proper board from the "Configuration -> Quick Set" drop-down list, it seems that the .bin file is always flashed into the EK-LM4F232 board, no matter which one is selected.

Windows 7, 64-bit, LM FLash Build 1470

  • 0
    Guru 117855 points

    Thought we'd read/seen it all - but yours seems a first!

    Are you stating that both eval boards are powered - and are both connected to the PC?  Or - are you reporting that, "last config/set-up" appears to "linger" - in violation of your "Config-Quick Set" selection?  (and only one eval board is powered/connected to PC?)

    Not a big fan of that utility - suspect issues raised here may assist those better able to help...

     

  • 0 in reply to cb1_mobile
    Intellectual 865 points

    Both are connected to the PC's USB receptacles and are therefore - both powered. I can see the PWR LEDs being lit on both boards.

    The "Quick Set" selection shows the last-selected board and I have no problem with the UI at all. The problem is: I select EK-LM3748 and when I flash a .bin file it flashes to the EK-LM4F232 :-)))

      LM Flash is not OpenSource so if I have to think of a workaround, it involves writing a tool on my own. And nobody wants that :-D

  • 0 in reply to Lubomir Bogdanov1
    Guru 117855 points

    Seems as if the PC is "only seeing" (or giving priority to) the LX232.

    Don't know if the LM Flash was intended to "multi-connect" - as you're doing.  (I like your idea/method - but SW writers may not have anticipated - nor provided for such use)

    Shouldn't you be able to check under PC's, "Control Panel -> Device Settings" and see indeed if both boards show up - and thus learn why the LX232 dominates?

  • 0 in reply to cb1_mobile
    Intellectual 865 points

    Exactly! When I open the Device Manager I see only one set of:

    + Stellaris In-Circuit Debug Interface

    -----+Stellaris ICDI DFU Device

    -----+Stellaris ICDI JTAG/SWD Interface

    and

    +Universal Serial Bus controllers

    -------+Stellaris Evaluation Board A

    -------+Stellaris Evaluation Board B

    I guess this is because the JTAGs are the same. It would be a good idea if we could connect more than one though. The thing I cannot understand is - in the Ports (COM & LPT) section of the Device Manager I see two Stellaris Virtual COM Ports ... which means that somehow it distinguishes between those two.

  • 0 in reply to Lubomir Bogdanov1
    Guru 117855 points

    Oh well - while I share your motivation/curiosity - resolution here beyond this reporter's pay-grade.  (unfortunate that factory remains quiet - suspect tasked w/never-ending (unwanted) re-branding efforts...)

    To clarify - when/if you remove the LX232 board - are you then able to establish proper commo & operation with your M3 board? 

    I fear for this potential "nightmare scenario" in your, "LM Flash - multi-connect!"  Should xtals be different on your board pair - and you download code intended for board X into board Y - does not that action cause dreaded, "lock-out" from JTAG?   You may wish to further consider...

  • 0 in reply to cb1_mobile
    Intellectual 865 points

    cb1_mobile said:
    To clarify - when/if you remove the LX232 board - are you then able to establish proper commo & operation with your M3 board? 

    Nope - if I remove the EK-LM4F232, then the EK-LM3748 fails to be programmed - the LM Flash displays: **ERROR**: Unable to connect to target!

    cb1_mobile said:
    and you download code intended for board X into board Y - does not that action cause dreaded, "lock-out" from JTAG?

    Lock-out does not occur. But I have to power cycle the EK-LM3748 board and restart the LM Flash tool. Other wise I keep getting the **ERROR** message...

  • 0 in reply to Lubomir Bogdanov1
    Guru 117855 points

    While sympathetic to your goal of, "multi-board - selective use" we don't know if LM Flash anticipated (and provided for) such operation.  As the source code is held "secret" - we're held hostage by officialdom.

    We use more conventional JTAG probe - and thus only have (one board at a time) sequential program/debug capability. 

    Out of tricks/ideas on this one...

     

  • 0 in reply to cb1_mobile
    Intellectual 865 points

    Yes, thank you for your time ...

    I believe there's no solution for this question for now...

    I'm using a workaround now - by a UART bootloader. But I need to automate the process and exclude the "force boot" button. I might use a third controller or something.

    Have a nice day!

  • 0 in reply to Lubomir Bogdanov1
    Guru 117855 points

    Lubomir Bogdanov1 said:
    I might use a third controller or something.

    Your thinking/methods overlap many of ours...  (may be good or bad...)

    In the past - pre-ARM days - we we're 8051 based - and "bit-banged" the code into (xilinx) FPGAs via their JTAG pins.  Don't like the idea of PC and JTAG probe for production use - thus "3rd Controller" - which operates in conjunction w/compact TFT screen - provides compact + robust means of, "Program Selection" and JTAG programming of MCU.  (and escapes the complexity & other tradeoffs introduced by bootloaders...)