Sebastian Kuzminsky wrote: (snippage)
> I'm proposing instead to change the command-line syntax to something > like this: > > bfload BoardType[:BoardId]=FirmwareFile > > The BoardType would be one of the supported board names, such as 5i20, > 5i22-1, 4i68, 7i43, etc. For the PCI boards, BoardID would be like the > current BoardNum, but only counting within the specified board type. > For the EPP board, the BoardID would be the io address of the EPP port > (which uniquely identifies the board on the system). So the usage would > look like this: > > # omitted the BoardID, defaults to 0 > bfload 5i20=SV12.BIT > > # one firmware on the first 5i22-1.5, another on the second > bfload 5i22-1.5:0=SV16.BIT 5i22-1.5:1=SVST8_8.BIT > > # different firmwares on different board types > bfload 5i20:0=SV12.BIT 7i34:0x378=SV8.BIT > > This seems a little clearer to use, and a bit more flexible. bfload > will do what verification it can: matching the requested firmware file > to the requested board when possible, and trusting the user when the > situation is ambiguous (4i68, 7i43). I really like that scheme - go for it! The only thing that comes to mind is error reporting - if you have more than one target=bitfile combo on the command line, you need to document what happens when one loads and another fails, etc. Probably return success if and only if ALL boards load correctly, and failure otherwise. Print messages to stderr to identify exactly what went wrong on a failure. Thanks for all your work on this stuff. Regards, John Kasunich ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
