Hey there!
I'm going to extend openOCD. There is a new lightwight TAP AHB-Controller (AHBL) from Hilscher Companny. Depending on the chip there is a ARM9 (netX50), a RISCV(netIOL), or … below it.
I'm going to add support to openOCD for this TAP-Device. I’m new to openOCD codebase.
I was looking for a API-Description of the TAP-Device in openOCD with no success.
I'm going to extend openOCD. There is a new lightwight TAP AHB-Controller (AHBL) from Hilscher Companny. Depending on the chip there is a ARM9 (netX50), a RISCV(netIOL), or … below it.
I'm going to add support to openOCD for this TAP-Device. I’m new to openOCD codebase.
I was looking for a API-Description of the TAP-Device in openOCD with no success.
It was a journy to find the right position where to start coding and which tools to use. I'm at the first steps of reading the TAP-ID. So at the very beginning.
struct target_type hinetiol_target = {
.name = TARGET_NAME,
.examine = hilnetiol_examine_target, // says hello to TAP
.init_target = netiol_init_target, // does nothing for now
.poll = netiol_poll, // dummy
};
Question:
Is there a tutorial / guidline / headsup, … for this work I‘ve done so fare and for future steps? Maybe some lines describing the interfaces or MACROS, some ideas behind the structure of the project?
How are the naming conventions? Which code has to be placed in which file. Right now it looks a bit random to me. I got the int to develop alongside ARM codebase. The ARM stack is huge, controllers are described along several composed files and structures. Others are different, but I can‘t really figure out rules how to implement it. Is there a minimal Dummy / minimal working target? Or a "must have" description?
After I‘m done, I wold like to write such a guideline if not existing. Where to commit it, who will have a review of it?
thx Xensemann
struct target_type hinetiol_target = {
.name = TARGET_NAME,
.examine = hilnetiol_examine_target, // says hello to TAP
.init_target = netiol_init_target, // does nothing for now
.poll = netiol_poll, // dummy
};
Question:
Is there a tutorial / guidline / headsup, … for this work I‘ve done so fare and for future steps? Maybe some lines describing the interfaces or MACROS, some ideas behind the structure of the project?
How are the naming conventions? Which code has to be placed in which file. Right now it looks a bit random to me. I got the int to develop alongside ARM codebase. The ARM stack is huge, controllers are described along several composed files and structures. Others are different, but I can‘t really figure out rules how to implement it. Is there a minimal Dummy / minimal working target? Or a "must have" description?
After I‘m done, I wold like to write such a guideline if not existing. Where to commit it, who will have a review of it?
thx Xensemann
_______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
