Krazubu has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]
Bertl_oO is now known as Bertl_zZ
tsal has quit [Ping timeout: 256 seconds]
tsal has joined #openocd
Hawk777 has joined #openocd
Hawk777 has quit [Quit: Leaving.]
Hawk777 has joined #openocd
nerozero has joined #openocd
marex has quit [Ping timeout: 265 seconds]
Haohmaru has joined #openocd
Hawk777 has quit [Quit: Leaving.]
Guest25 has joined #openocd
Bertl_zZ is now known as Bertl
keshav has joined #openocd
Guest25 has quit [Quit: Client closed]
Krazubu has joined #openocd
Guest86 has joined #openocd
Guest86 is now known as epac-tom
keshav has quit [Quit: Client closed]
stipa has quit [Ping timeout: 240 seconds]
stipa has joined #openocd
nerozero_ has joined #openocd
Bertl is now known as Bertl_oO
nerozero has quit [Ping timeout: 240 seconds]
nerozero_ has quit [Ping timeout: 240 seconds]
marex has joined #openocd
Hawk777 has joined #openocd
epac-tom has quit [Quit: Client closed]
CSpegal has joined #openocd
<CSpegal>
We have a board/chip that has active high jtag trst/srst so I'm looking to implement that option. I've already edited src/jtag/adapter.c to include the options trst_inverted and srst_inverted. I also added the necessary bits to the reset_types enum. I'm wondering if you think this change is best to implement at the driver level or in the core. The
<CSpegal>
problem with doing it in the core is some drivers have hard coded reset routines in the init for options RESET_CNCT_UNDER_SRST and RESET_SRST_NO_GATING.
<PaulFertser>
CSpegal: hi. Must be some quite an unusual chip.
<PaulFertser>
CSpegal: some interface adapters can't even drive SRST high, the usual way is to use open drain to handle it.
<CSpegal>
It is, it's a custom SoC.
<PaulFertser>
CSpegal: and with TRST, does it mean you can't use other JTAG devices in the same chain if you're using TRST?
<PaulFertser>
CSpegal: isn't it better to add a custom inverter on board for the custom SoC for those signals? And fix the SoC in the next iteration.
<PaulFertser>
CSpegal: I'm just wondering if your case is so special that the best way would be for you to have a custom temporary hack instead of trying to provide a generic solution.
<CSpegal>
We did that on the second rev of the board. Working on testing the first rev now.
<PaulFertser>
CSpegal: and TRST isn't really needed for JTAG.
<PaulFertser>
If it's just for testing an early rev why bother with trying to upstream such an unusual quirk?
<CSpegal>
It probably is a very special situation. And considering the the OD issue you pointed out probably not worth a generic solution.
<PaulFertser>
CSpegal: if you have DP Busblaster adapter you can load custom CPLD config into it for inverting.
<PaulFertser>
CSpegal: so what debug adapters do you have?
<CSpegal>
We were using a ft2232 and recently tired it with a cmsis-dap (Atmel ICE). The ICE is nice because the board has an ARM standard header for the JTAG interface.
<CSpegal>
The ft2232 board they were using required a breadboard mess.
<CSpegal>
I figure I could just hack the driver for cmsis-dap to invert it but decided to go over kill and look at a generic solution.
<CSpegal>
Also the board assumed the resets were active low too so they are pulled up.
<PaulFertser>
CSpegal: not to demotivate you, but I'm not sure it's going to be useful to anybody else.
<PaulFertser>
CSpegal: btw, using bare ft2232 might prove problematic signals-integrity wise, usually jtag adapters include series resistor for source termination.
<CSpegal>
No, not at all. Honestly I appreciate you pointing out that this is a special case that probably won't be useful to anyone else.
<CSpegal>
Not worth the effort for a generic solution then.
Haohmaru has quit []
<CSpegal>
PaulFertser They were using a FT2232H Mini Module and were having trouble with is between the boardboard and level shifter they needed to use with it to connect to the chip.
<PaulFertser>
CSpegal: I see. Then the termination needs to be after level shifter, between it and target.
<CSpegal>
PaulFertser I doubt they had those. Probably something to look into. They also removed the pull-ups on the board because they caused problems they said. I wonder if lack of series termination had to do with that.
<PaulFertser>
CSpegal: assuming they're EEs they'd check signal shapes near the SoC and would see "ringing" and would implement termination if that was a problem.
CSpegal has quit [Quit: Client closed]
CSpegal has joined #openocd
<CSpegal>
They're test engineers, not really used to circuit design, but I'll have to ask them. I designed the board with the standard JTAG termination but didn't get involved with the adapter configuration until they started having problems. I was also not told the resets were active high during the design process.
<PaulFertser>
CSpegal: btw, there's a board called TUMPA, it has a nice fast buffer IC and also it push-pulls reset.