OpenOCD - Open On-Chip Debugger / Tickets / #342 invalid command name "hla

Paul Fertser - 2022-03-17

Hi,

On Wed, Mar 16, 2022 at 08:53:17PM -0000, Andrew Eidsness wrote:

I've checked out the v0.11.0 branch and built openocd with the config parameters
listed at the end. I've actually tried several different options, the one listed
at the end is "everything I could find".
...
I've connected a FlySwatter2 to a 1294xl, but I get an error when trying to
launch with:

$ openocd -f interface/ftdi/flyswatter2.cfg -f board/ti_ek-tm4c1294xl.cfg -c

This looks more like a support request, please consider writing to the
mailing list (-devel is fine) or asking on the IRC the next time.

The problem there is that you tell OpenOCD you're using a specific
evaluation board while in fact you're connecting an external JTAG
adapter directly to the target chip. So you should be sourcing the
target config rather than the board config.

HTH

Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Andrew Eidsness - 2022-03-17

Ah, thanks! I don't see a target config for this chip, but I think I can figure that out.

This ticket can probably be closed, but I don't see a button that lets me do that.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Paul Fertser - 2022-03-17
  
  On Thu, Mar 17, 2022 at 11:27:23AM -0000, Andrew Eidsness wrote:
  
  Ah, thanks! I don't see a target config for this chip, but I think I can figure
  that out.
  
  In board/ti_ek-tm4c1294xl.cfg you can see it's just sourcing
  target/stellaris.cfg .
  
  This ticket can probably be closed, but I don't see a button that lets me do
  that.
  
  We'll close it later, thank you for caring.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Andrew Eidsness - 2022-03-17
    
    I think that the stellaris configuration is for the on-board ICDI which is accessible over the board's serial port. I'm experimenting with using an external one. There are alot of good examples in that folder though. I might start with the stellaris one, then see what else I can do.
    
    I don't know much about openocd, I'm mainly just experimenting to see what I can get to work.
    
    Thanks for your help -- this should definitely have been a forum post instead, I'll followup there if I have any actual questions.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Paul Fertser - 2022-03-17
      
      On Thu, Mar 17, 2022 at 03:43:46PM -0000, Andrew Eidsness wrote:
      
      I think that the stellaris configuration is for the on-board ICDI which is
      accessible over the board's serial port. I'm experimenting with using an
      external one. There are alot of good examples in that folder though. I might
      start with the stellaris one, then see what else I can do.
      
      All configs in target/ directory are target configs, they do not
      include the on-board ICDI or other on-board adapters. Stellaris is the
      name of the original line-up, and it should work with your part.
      
      I don't know much about openocd, I'm mainly just experimenting to see what I can
      get to work.
      
      I suggest you read the official User Manual while doing so.
      
      Thanks for your help -- this should definitely have been a forum post instead,
      I'll followup there if I have any actual questions.
      
      No idea what forum you have in mind, I suggest using the mailing list
      or our IRC channel, I do not read any forums.
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

invalid command name "hla_layout"

The Open On-Chip Debugger

Milestone

Searches

Help

#342 invalid command name "hla_layout"

Discussion

HTH