Dave, The DRC engine only checks each block and does not modify it. If you want the DRC to modify xps_objs, then the calling function (in this case gen_xps_files.m) also has to be updated. FYI, the version that I am running is crashing at the EDK portion of the program while trying to parse the system.mhs file. The mhs file identifies the ports of the adc16_interface as 'adc16x250_8_a1', 'adc16x250_8_a2', ... while the corresponding mhd file for the ADC identifies these ports as simply 'a1', 'a2', ...
-Joe Kujawski On Tue, Sep 24, 2013 at 2:18 PM, David MacMahon <[email protected]>wrote: > Hi, Joe, > > The DRC functionality is handled in the "drc" method of the xps_block > subclasses. The "base class" (i.e. xps_block) drc function is defined in > xps_library/@xps_block/drc.m. It doesn't do much right now. Various > subclasses define their own drc scripts in the various > xps_library/@xps_BLOCKNAME/src.m files. The ADC16 drc file > xps_library/@xps_adc16/drc.m is merely a placeholder function that always > returns 0 (which I guess means no error). > > It would be great if the gateway naming check (and automatic fixing) were > added to xps_library/@xps_block/drc.m and then the various subclass drc > functions were modified (if needed) to call the base class drc function. > I'm not an expert on Matlab's OO class mechanism and syntax so it seems a > little obtuse to me, but I think that's the general idea. > > Hope this helps, > Dave > > -- ************************************** * Joe Kujawski * Siena College * Dept. of Physics and Astronomy, RB 113 * 515 Loudon Road * Loudonville, NY 12211-1462 * * Email: [email protected] * Phone: 518-782-6885 * Fax: 518-783-2986 **************************************
