On Nov 26, 2008, at 4:19 AM, Duane Ellis wrote:
rick> Is there a practical reason why the daemon cannot be started unless an interface has been specified?[snip]oyvind> I've did a lot of work a year back to support connecting to powered down targets[snip] I would add the SPI/I2C/etc type changes would have *NO* targets.Today, OpenOCD assumes there is always a target. Perhaps it needs a "target none"? for that situation.And - it should have an immediate console rather then then a console via telnet only.-Duane.
I would assume that not having a 'target create' line in a config would be sufficient to indicate no targets. It just seems that 'init' checks that an interface and target are defined before succeeding. If there isn't a technical reason for that, I'd like to change it so the daemon can start up with no interfaces or targets defined. For future use, I could even see allowing multiple interfaces to be defined at one time.
-- Rick Altherr [EMAIL PROTECTED]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
