16:35 <mwette> I received my Microchip PIC64GX100 KIT yesterday. There was one udev rule that referenced `$kernel'. I'm wondering if that should be `$KERNEL'. Any ideas? Here is the rules file: https://paste.debian.net/1334715/

16:35 <mwette> ^ reference is on line 9

16:54 <karlp> take that up with whoever gave that to you :) that's not anyth9ing from openocd...

16:54 <karlp> is microchip providing a forked openocd with borked scripts?

16:55 <karlp> it might be a magic value to try and unbind the entire kernel driver?

16:56 <karlp> normally you see selective unbindign like in this answer here: https://stackoverflow.com/questions/33981056/ftdi-d2xx-conflict-with-ftdi-sio-on-linux-how-to-remove-ftdi-sio-automatically

17:01 <mwette> It looks like they are using openocd for the PolarFire Icicle kits, in the SoftConsole IDE, based on screen output I've seen on their forums.

17:01 <mwette> karlp: thanks

18:51 <mwette> found $kernel here: http://reactivated.net/writing_udev_rules.html#strsubst

20:03 <karlp> but htat's not in a udev rule... its in a shell script talking to sysfs....

20:03 <karlp> weird. it's substituing into a command, that will only work inside a udev script.

20:03 <karlp> way to make things easy to follow mchp

20:07 <karlp> most of that seems to be handling that they've never bothered to send in thier pids to get them here: https://github.com/torvalds/linux/blob/master/drivers/usb/serial/ftdi_sio_ids.h#L923-L924

20:08 <karlp> they could add an entry here and avoid that craycray: https://github.com/torvalds/linux/blob/master/drivers/usb/serial/ftdi_sio.c#L909

20:09 <karlp> right down to only binding to the channels they want like theother boards....

21:17 <mwette> So, wrt openocd, can I use "adapter driver ftdi" then, since they use a FTDI chip? Or can I use "adapter usb /dev/ttyUSB2"? The notes say ttyUSB2 is connected to console (ubuntu login) and ttyUSB1 is connected to a HART monitor.

21:45 <PaulFertser> mwette: openocd doesn't use tty devices for ftdi debug adapters, it handles them directly via libusb.

21:47 <PaulFertser> And you can't just tell it "driver ftdi", you're supposed to set appropriate modes for inputs and outputs and GPIOs for trst and srst. Most ftdi adapters are slightly different so OpenOCD needs that per-adapter configuration.

21:49 <mwette> PaulFertser: thanks - got it. I may know someone to ask about details.

21:50 <PaulFertser> mwette: you should probably ask microchip to properly upstream support...

21:51 <PaulFertser> mwette: also when you have schematics for the adapter you can write a config yourself.

22:10 <mwette> PaulFertser: Awesome, I found schematics online, with the FD4232H outputs showing port A to JTAG lines. I'll see how my queries go later.

22:35 <PaulFertser> mwette: the OpenOCD User Manual and examples in tcl/interface/ftdi/ should be enough to cook a config for your case. Feel free to ask if anything's unclear.

22:35 <PaulFertser> interface A is default

23:17 <mwette> thanks!