Menu
▾
▴
[OpenOCD-devel] A new Target for opoenOCD - AHBlight
|
From: Xen M. <xen...@gm...> - 2019-01-17 08:33:54
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hey there!<br/>
<br/>
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.<br/>
<br/>
I'm going to add support to openOCD for this TAP-Device. I’m new to openOCD codebase.<br/>
I was looking for a API-Description of the TAP-Device in openOCD with no success.</div>
<div>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.<br/>
<br/>
struct target_type hinetiol_target = {<br/>
.name = TARGET_NAME,<br/>
.examine = hilnetiol_examine_target, // says hello to TAP<br/>
.init_target = netiol_init_target, // does nothing for now<br/>
.poll = netiol_poll, // dummy<br/>
};<br/>
<br/>
Question:<br/>
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?<br/>
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?<br/>
<br/>
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?<br/>
<br/>
thx Xensemann</div></div></body></html>
|
