如何直接将固件写入FX3 RAM

你好，
WHIS命令行工具（在GNU/Linux中）你在说什么？请给我指出一下。
* IMG是唯一的格式。
当做，
阿南德



     以下为原文
  Hi,
    Whis command-line tool (in GNU/Linux) are you talking about? Please point me to it.
    *.img is the only format.
    Regards,
    Anand

阿南德-
为了澄清，我意识到FX芯片只支持了.IMG内部——我在谈论通过线来转换/上传的程序。
这是我的问题中最不重要的，因为你可以把任何列出的六进制/bin文件转换成一个IMG文件——它只是一种格式。
更重要的问题是：
1）从FX3的命令行编程固件的最好方法是什么？
2）返回代码的文档在哪里？
谢谢你的时间！



     以下为原文
   Anand -
     
    Just to clarify, I realize that the FX chips have only ever supported *.img internally - I'm talking about programs that will convert/upload over the wire.
     
    This is the least important of my questions, as you can turn any of the listed hex/bin files into an img file - it's just a format.
     
    The more important questions are:
     
    1) What is the best way to program firmware from the command line for FX3?
    2) Where is documentation for return codes?
     
    Thanks for your time!

你好，
我们不支持您正在使用的实用程序。所以我没有关于错误代码的信息或者它是如何工作的。
我同意你关于格式更改的观点，但是你应该意识到你是FX2/FX2LP与FX3的意思。
目前的控制中心是用于下载固件的实用工具。我们没有一个命令行用于固件下载在这个时间点。
当做，
阿南德



     以下为原文
  Hi,
    We do not support the utility that you're using. So I don't have information on the error code or how it works.
    I agree with your point on format change but you do realize that you're something that was meant for FX2/FX2LP with FX3.
     
    Currently control center is the utility for downloading firmware. We don't have a command line for firmware download at this point of time.
    Regards,
    Anand

你能把上传的固件信号上传到USB上吗？然后客户至少可以自己制作工具。



     以下为原文
  Can you please post the signals used to upload firmware over USB?  Then customers could at least make their own tools.

干得好，
它使用类似于FX2LP的0xA0供应商请求，但是这里由于地址是4字节长，所以我们使用WALL作为最重要的字和WiDEX地址的最重要的字。使用这个，我们发送数据。
在此之后，我们将跳转到程序入口供应商请求（与上述相同的0xA0供应商请求格式，但WWORE为0字节）与地址跳到WWORD和WEDEX。（在FX2LP的情况下，类似于0xA0供应商对0xE600的请求，让CPU执行代码）。
当做，
阿南德



     以下为原文
  Here you go,
    It uses 0xA0 vendor request similar to FX2LP but here since the address is 4-byte long we use wValue for Least Significant Word and wIndex for Most Significant Word of the address. Using this we send the data.
    After this at the end we send the jump to program entry vendor request (same 0xA0 vendor request format as above but with wLength as 0 bytes) with the address to jump to in wValue and wIndex. (similar to 0xA0 vendor request to 0xE600 in the case of FX2LP to let the CPU execute code).
    Regards,
    Anand

FIY，向FxLoad发布了一个补丁，支持将.img文件下载到FX3RAM：
HTTP//www. SPICIC.NET/Lists/HypLog/MSG0542.HTML
我不确定FxLoad是否被维护（我在补丁上还没有收到任何回复），所以不要在任何时候都很快地找到它。



     以下为原文
  FYI, I posted a patch to fxload to support download of an .img file to FX3 RAM:
    http://www.spinics.net/lists/hotplug/msg05452.html
    I am not sure whether fxload is being maintained (I haven't received any response yet on the patch), so don't look for it in mainline anytime real soon...

嗨，我正试着遵循你的指令并将你的补丁应用到SoxEFig（版本0.1）上的FX2LIB的当前版本。
但是看看你发布的补丁，我怀疑补丁是适用于不同版本的FX2LIB。
在第一行中，您的代码与EXUSB的代码不同，而EZUSB不存在于FX2LIB的最新版本中。我在哪里找到你使用的FX2LIB源？
谢谢你，乔尔



     以下为原文
  Hi, I was trying to follow your instruction and apply your patch to the current release of FX2Lib on sourceforge (version 0.1).
    But looking at the patch you’ve published I suspect the patch is meant to be applied to a different version of fx2lib.
     
    At the first line you are diffing your code against  ezu***.c which doesn’t exists on the latest release of FX2lib. Which version and where do I find the FX2lib source you’ve used?
     
    Thanks in advance, Joel

嗨，乔尔，我在CVStrue上安装了补丁：HTTP:/SooSurfGe.NET/SCM/？Type＝CVS和GAMPGIID＝17679，它看起来像MaMrDOMO通过清除嵌入在代码中的电子邮件地址来损坏补丁。附上补丁的干净副本。我验证了这一点适用于CVSFXLoad项目。史蒂夫
FXLAD-FX3-RAM-PATCH.TXT.ZIP
6.6 K



     以下为原文
  Hi Joel,

I based the patch on the CVS tree:

http://sourceforge.net/scm/?type=cvs&group_id=17679

It looks like majordomo damaged the patch by scrubbing out e-mail addresses that were embedded in the code. A clean copy of the patch is attached. I verified that this applies to the CVS fxload project.

Steve 

•   fxload-fx3-ram-patch.txt.zip 6.6 K  
  
  

在尝试遵循上述过程时，我遇到了类似于OP的问题。当发出如下控制转移时，如果设备不支持控制请求，则在0x4000（-9：LiBuByError管）中从设备接收错误。
INTHR＝LIB总线控制传输（UBHDL，//Road 0x40，//BMeReQuestType：主机到设备，供应商，设备0xA0，//BReQuest:DLL ADDRULL低，//WORE（LSW）DLADADRYLY高，//WINDEX（MSW）（无符号CHAR *）D，//数据BS，/WWLINE 1000）；/ /超时
本质上，这意味着我不能下载固件文件& 16384字节。
对不起，这里的格式可能是错误的。既没有预览也没有像样的格式化能力。



     以下为原文
  I run into a similar problem as the OP when trying to follow the procedure described above. When issuing a control transfer as follows, I receive an error from the device at 0x4000 (-9: LIBUSB_ERROR_PIPE if the control request was not supported by the device).
    int r = libu***_control_transfer( u***hdl, // handle 0x40, // bmRequestType: Host to Device, Vendor, Device 0xA0, // bRequest: Vendor dl_addr_low, // wValue (LSW) dl_addr_high, // wIndex (MSW) (unsigned char*)d, // data bs, // wLength 1000 ); // timeout in ms
    Essentially, this means I can't download firmware files > 16384 bytes.
    Sorry for the (presumably) bad formatting here. There's neither a preview nor decent formatting capabilities

我发现自己跳过箍，以获得FxLoad实用程序更新为FX3根据史提芬的指令，所以我虽然我会节省一些搜索者通过分拆的废弃FxLoad项目。
看看SoxEfFrFor上的FX3Load项目，它包含了史提芬的补丁并包含32位Linux可执行文件：
HTTPS://SooSurfGe.NET/PrimeSt/FX3Load



     以下为原文
   I found myself jumping through the hoops to get the fxload utility updated for the FX3 per Steven's instructions, so I though I'd save fellow seekers some time by branching off of the abandoned fxload project.
    Behold the fx3load project on SourcefForge which incorporates Steven's patch and includes a 32-bit linux executable:
    https://sourceforge.net/projects/fx3load/

谢谢！我从来没有得到任何回应，我尝试向FxLoad上游发送更改，因此“放弃”是正确的词。端口FXLoad能够在目标设备上编程闪存是很好的。控制中心似乎使用CyoBoTraceReal.img进行此操作；对于Fx3Load，我想我们必须开发一个等价的IMG，它可以适应它所找到的SPI/I2CFlash。CyPress的任何人都可以评论这样的IMG是否可以与（GPLV2）FX3Load捆绑在一起？史蒂夫



     以下为原文
  Thanks! I never did get any response to my attempt to send the changes to fxload upstream, so I guess "abandoned" is the right word.

It would be nice to port fxload's ability to program flash on the target device. Control Center seems to use CyBootProgrammer.img for this; for fx3load, I suppose we'd have to develop an equivalent .img that can adapt to whatever SPI/I2C flash it finds.

Can anyone from Cypress comment on whether such an .img could be bundled with (GPLv2) fx3load?

Steve