On 01/26/2010 04:50 AM, Waschk,Kolja wrote: >>> * add a new field 'main_part' to struct URJ_CHAIN >>> * add a new filed 'params' to struct URJ_PART and its related >> could you describe these new pieces a bit more in detail ? like why we >> had to > > I also would like to learn a bit more about these. "chain->main_part" at > first > sight seems to equal "chain->parts->len - 1" (as is chain->active_part just > after detect) so I'm not sure why an extra parameter is needed. > "chain->parts->len - 1" is just an initial value. gdbproxy will change it if needed. For example, the JTAG chain might contain multiple parts. There might be one or more Blackfin processors in those parts. gdbproxy will set main_part to the Blackfin part, which will be used in the debugging session. active_part is, as I understand of the source code of UrJTAG, the part to which UrJTAG commands apply. main_part, for Blackfin, is the core which is always available. So it's a Blackfin specific thing. Ideally I think we need a params in struct URJ_CHAIN, and put main_part in it. But I just didn't feel motivated to do this.
Originally, main_part was not in struct URJ_CHAIN, it was in a struct in gdbproxy. But later we moved most of basic emulation operations from gdbproxy to UrJTAG, I had to move it to struct URJ_CHAIN. Hope this explains well. Jie ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ UrJTAG-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/urjtag-development
