tarekb has quit [Read error: Connection reset by peer]
Helmholtz has quit [Changing host]
Helmholtz has joined #openocd
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #openocd
PReDiToR has joined #openocd
PReDiToR has quit [Client Quit]
emeb has joined #openocd
Hawk777 has joined #openocd
renrelkha has quit [Quit: bye]
renrelkha has joined #openocd
Boban has joined #openocd
<Boban>
hello team openocd
<Boban>
I'm trying to create a cfg script to connect to two ARM chips on two different boards
<Boban>
I'm trying to do this with minimum changes to the original files
Haohmaru has quit []
<Boban>
I would like to know what parameters need to be specifically named for each core
<olerem>
Boban: i do not really understand you question. Lest start from beginning, "two ARM chips" - what are the names of this chips?
<olerem>
are this configs already mainline?
<Boban>
they are ARM A5 chips
<Boban>
they have cfg and tcl files which work on their own
<Boban>
I'm trying to create a single cfg script to access each board
<olerem>
ARM A5 - means ARM Cortex-A5?
<Boban>
yes
<olerem>
ok, it is architeture name or CPU core name. What are the chip names?
<Boban>
CPU core name
<Boban>
right now my chip names are the names of the development boards
<olerem>
i'm confused
<olerem>
ok, you have some secret chip based on ARM Cortex-A5, which is on some secret board. All of this secret things are not part of mainline OpenOCD. Correct?
<PaulFertser>
Boban: if you have two identical CPUs you should set CHIPNAME before sourcing the config.
<PaulFertser>
And use it inside the config of course as the other targets do.
<olerem>
PaulFertser: are we talking about multi chip or multi core config?
<PaulFertser>
So you can e.g. source stm32f1x.cfg twice if you set CHIPNAME before the second time.
<PaulFertser>
olerem: two different boards were mentioned.
<PaulFertser>
So I guess same chip but on two boards connected in JTAG chain.
<Boban>
yes
<olerem>
ok
<olerem>
Boban: then lissen to PaulFertser
<Boban>
ok
<PaulFertser>
What company are you working for Boban and do you think the OpenOCD team can do something so that the configs would be properly contributed upstream by you when the chips are released?
<Boban>
PaulFertser I work for Analog Devices. We're still working on implementing OpenOCD support for customers.
<Boban>
I can ask and confirm if our configs will be part of the upstream repo
<Boban>
The eventual goal is to do that
<PaulFertser>
Boban: I see, thank you. I hope you'll eventually manage to upstream everything useful to the general public.
<Boban>
ok
<PaulFertser>
You can also consider helping to review other patches, especially Cortex-A related since you have a suitable test setup.
<PaulFertser>
Everyone's welcome to review.
<Boban>
ok
<Boban>
PaulFertser so should there be a separate cfg file to set CHIPNAME twice and then two other cfg files to source these chipnames?
<PaulFertser>
Boban: if it's a single board that has two distinct chips, then there should be a board config that sets chipname and then sources the target config, sets the chipname again to something different and sources the target config again (the same config)
<PaulFertser>
If it's just two boards that you connect for some test then you can either create openocd.cfg to do that or specify it all on command line when starting openocd.
<PaulFertser>
So basically it's enough to have a single target.cfg then run openocd -f interface/jlink.cfg -f target.cfg -c "set CHIPNAME thesecond" -f target.cfg
<Boban>
ok
<Boban>
if there are differences between the two boards, then I can set CHIPNAME for each board before sourcing the respective target.cfg file on the command line right?
<olerem>
hm, i feel like we need more advanced names, automatically generated
<Boban>
yes but just for the case of two boards, would it be enough to specify them on the command-line?
<olerem>
yes, it should be possible
<Boban>
ok thanks guys
<Boban>
will let you know if it works
<olerem>
"-c "set CHIPNAME thesecond"" will set it globally, so what ever config you will load after this command, it will be affected
<olerem>
ok, happy hacking
<Boban>
ok thanks for that too
Boban has quit [Quit: Client closed]
akaWolf has quit [Ping timeout: 268 seconds]
nerozero has quit [Remote host closed the connection]
tarekb has joined #openocd
akaWolf has joined #openocd
borneoa_ has quit [Quit: Connection closed for inactivity]
emeb has quit [Ping timeout: 268 seconds]
klys has quit [Read error: Connection reset by peer]