It might be worth reaching out to maintainers of Linux's ARM port[0] or Russell King[1], the lead maintainer for Linux's port to the ARM microarchitecture. I'd imagine he'd be amenable to helping other open source projects get access to access to suitably licensed ARM documentation, headers, as well as having contacts inside ARM.
The Linux Foundation may be another good resource. Their NDA Program[2] helps open source developers gain access to developer documentation that's all too often covered by non-disclosure agreements in a way suitable to all parties. ARM is listed as a supporting member of the foundation; I'd be surprised if they the two groups hadn't already worked together to get the docs, code, and/or headers required for porting to their processors. --adam [0] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel/ [1] [email protected] [1] http://www.linuxfoundation.org/programs/developer/nda On Thu, Feb 5, 2015, 9:01 AM Joakim Gebart <[email protected]> wrote: > The only tool I've found for converting SVD to header files is the > svdconv.exe that comes with the Keil IDE. The headers it produces are > somewhat convoluted and it did not make nice indexable arrays and such > of array-like register sets, at least when feeding it with the Kinetis > SVD files that I've found. It did however give some warnings about > those SVD files so it might have been badly formed input files as > well. It is difficult to find any information about how the industry > is working with SVD files... > > Does anyone have any inside connections on the larger manufacturers > and can tell something about what tools are used "on the inside"? > > Since the SVD files are XML it is fully possible to write an xslt file > and use xsltproc to produce whatever output we want from the .svd, but > it is not going to be a small task to write such an xslt. > > Best regards, > Joakim Gebart > Managing Director > Eistec AB > > Aurorum 1C > 977 75 Luleå > Tel: +46(0)730-65 13 83 > [email protected] > www.eistec.se > > > On Thu, Feb 5, 2015 at 3:26 PM, Thomas Eichinger > <[email protected]> wrote: > > Dear list, > > > > tl;dr: Does anybody have experience with SVD files? > > > > Since it happened at least two times that ports of RIOT to new hardware > was put > > on halt because of unclear or no license statements in hardware > manufacturers > > header files I did some research into this direction. > > > > What I found yet are SVD (System View Definition) files, specified by > ARM and somehow > > distributed I was thinking about generating missing header files > directly from this > > definitions. > > > > Would it make sense to generate our own header files from these files? > > > > Does anybody have any experience with those files and license > implications with those? > > (When searching the ARM page there are a couple of EULAs to accept and > so forth) > > > > Any input on this topic is welcome. > > > > Best, Thomas > > > > _______________________________________________ > > devel mailing list > > [email protected] > > http://lists.riot-os.org/mailman/listinfo/devel > _______________________________________________ > devel mailing list > [email protected] > http://lists.riot-os.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list [email protected] http://lists.riot-os.org/mailman/listinfo/devel
