On Wed, 2009-04-22 at 10:35 +0200, Nico Coesel wrote: > Zach, > There are a few things missing on your list which I think are important: > > - Coldfire support (which is basically an enhanced 68000 core) would be > nice. There is no open source solution out there to program Coldfire > controllers which is a shame because the Coldfire controllers are > actually quite nice and reasonably priced. Freescale thinks their > customers should use Codewarrior or take their business somewhere else. > - Completing ARM Cortex A8 support.
These will appear in the next revision of my list. I have been thinking about what I want my next "hobby" board to be, and the Cortex A8 has been one possible choice. [[I am now hoping a board vendor reads this, recognizes their opportunity, and drops one in the mail to me. ;) ]] How much of the Coldfire support would need to be reverse-engineered? With specifications and hardware, half of the battle will have already been won, but the lack of an open source solution makes me guess unencumbered references are unavailable. Posting links to references would help plant seed for others to pick this up and run with it. > I see CFI is on your list as well. I have a slightly improved version of > cfi.c which some speed enhancements. Shall I mail it to you to have a > look at it? I agree the cfi code is not very clean; a lot of code which > basically does the same is duplicated. Also the bus width / chip width > handling is not fully implemented yet. IMHO vendor specific code could > be just a bunch of functions called through function pointers from > cfi.c. Post code to the list, but we are on the same wavelength. Completely. > I just hope people are not put off by the high frequency of changes > which causes their patches to fail. I think its best to concentrate on > one area at a time and finish it first before moving to another area. > This reduces the chance two (or more) people are working on the same > code. Thanks for this feedback. I do recognize that some of my recent widespread changes have impacted just about everyone, but there will be fewer of those as I begin to refocus on my current goals. Except for the static keywording, all of my widespread changes were driven to eliminate warnings, and that was not entirely without consequences. Still, I see potential to do minor clean-up to the high-level API (i.e. server, jtag, and flash), so those patches will be appearing someday (unless someone beats me to them). At the moment, those fall entirely under the scope of "type system fixes", but there seems to be other opportunities to change things for the better. Cheers, Zach _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
