On 21 Aug 2012 01:52 , Pete Batard wrote: > Will you at least be available to test libusbx' fxload with your > platform? The obvious goal for spending time on this effort is, provided > the FX3 becomes one of the leading USB 3.0 development target out there, > to promote libusbx among developers who may only come for the FX > firmware upload tool. But without a platform to validate against, this > will be a bit of a challenge...
Of course, this should not pose a problem at all. > Right now, I'm still spending/wasting time on eeprom flashing support > for the FX2 (doesn't work for my board yet), but once that's sorted, > I'll switch to adding FX3 support. Let me know then. > "Added support in the firmware to jump back to the boot firmware image, > without disconnecting the USB connection. This feature allows users to > modify the application code without breaking the USB connection." > > I'd see the implementation above as an extension of the .IMG format > rather than a brand new one. Probably something in the same vein as the > 80 01 E6 00 00 reset block added at the end of the FX2's iic > (fx2_trm.pdf chapter 3.4.3). It even looks as if they just added a simple SDK helper function, while the functionality was always available. You first have to retrieve the entry point of course. There's a suggestion to nail this address down by modifying the linker here: http://www.cypress.com/?app=forum&id=167&rID=54054 This would be very project specific then. Alternatively, the Cypress elf2img converter binary outputs the address when called in verbose mode. That's what the SDK docs suggest. If the address is known, it should suffice to issue a 0xA0 vendor request with wValue (LSW) and wIndex (MSW) containing the address dword. Should work the same way as writing firmware to the device. As the entry address is not static in general, the functionality is of limited value unless we feed the elf files to xusb and convert them to img by ourselves (which is not very realistic); this way, we'd know the entry address. Otherwise we might make the entry address an optional argument to the FX3 upload call and leave it to the user to retrieve it. As this is not mission-critical, I dare say that I can take over this. All the best, /Markus ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
