Any information or suggestion if I want to add support to AVR32 chips?
I have read all the JTAG commands of AVR32 from datasheet. And I’m reading the TRM of AVR32.
Would be a very good addition to OpenOCD but there might be problems concerning availability of information from Atmel. I couldn’t get the excellent gdb front-end Insight working with the avr32 chip due to lack of published assembler instructions - this might have been resolved by now.
I’ve lobbied with the AVR guys for openocd support for quite some time. Rught now the only way to flash them is to use their expensive and fragile JTAGMkII pod, and their proprietary avr32program bit of program.
I’ll continue to lobby. I think the AT32UT3[a/b] are really cool and would make nice arm-equivalent/replacements; but not with locked in tools…
Isn’t USBprog support it?
I’ll get one AVR32 board next week and try the programming protocol from the .
My tool can support AVR32 thru JTAG now.
Is it meaningful to add the support into OpenOCD?