06:34 <gamiee> borneoa___ hi! Regarding to this comment: https://review.openocd.org/c/openocd/+/8527/13/src/flash/nor/bl602.c#119

06:34 <gamiee> I changed it just to `char *reg_names[]`, according to feedback, but then checkpatch.sh is complaining: ERROR:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const

06:34 <gamiee> Additionally, when changing it to `static const char *reg_names` what was suggested by Thomas, that would require recasting const char* to char* since init_reg_param accepts char*. Any suggestions please? Thanks

10:19 <karlp> tell the reviewers to read the styleguide better ;)

10:26 <Haohmaru> fuh-fuh-fuhuhuhuh-free styler

10:28 <dlezcano> Hi all

10:29 <dlezcano> Does anyone have a target configuration file for the NXP s32g board ?

10:30 <dlezcano> I'm a newbie on OpenOCD and jtag BTW ;)

10:31 <Haohmaru> uh, do you actually need a config for the _board_ ? don't you just need the target MCU?

10:32 <Haohmaru> or is there something more going on

10:50 <Haohmaru> oh well, wakamakafo

10:58 <PaulFertser> dlezcano: do you need just debug or flashing?

10:59 <dlezcano> Just for debugging

11:00 <PaulFertser> dlezcano: so it's cortex-a + cortex-m, it should be reasonably easy to write a Tcl configuration file for this SoC.

11:01 <dlezcano> I found some scripts in this directory https://people.freebsd.org/~wpaul/w00t/s32g/

11:01 <dlezcano> But I don't know how to use them

11:02 <Haohmaru> how many cores o_O

11:02 <PaulFertser> dlezcano: do you have prior experience with OpenOCD? Have you read the user manual?

11:02 <dlezcano> No, I'm very new

11:02 <dlezcano> I'm looking for a direction

11:04 <PaulFertser> dlezcano: I suggest you start with reading the official User Manual and ask questions if anything's unclear.

11:04 <dlezcano> PaulFertser: ok, thanks

11:04 <PaulFertser> I checked one of the scripts and it should be compatible with the current codebase.

11:05 <PaulFertser> Not sure if changes to ir len mentioned https://sourceforge.net/p/openocd/tickets/261/ are still needed.

11:10 <Haohmaru> huh, "unusual" JTAG

11:12 <PaulFertser> I'm not sure it's really custom, probably it's actually two taps each 4 bit long.

11:22 <PaulFertser> dlezcano: to understand basics about JTAG itself this looks reasonable https://medium.com/@aliaksandr.kavalchuk/diving-into-jtag-protocol-part-1-overview-fbdc428d3a16