如果XXDMA和XXDMAB之间的链接被删除,则可以建立附加的项目。但是如果增加了3个链节,它就不能放置一些USB DMA。如果许多TXDMAX被禁用,它也将被构建。我没有使用所有的DMAS -有什么问题吗?错误信息:错误:PLM.M046:E2806:无法放置固定的功能块。有关详细情况,请参阅报表文件。错误:PLMM446:“C:\程序文件(x86)\ CyPress \ PSoC创建者\ 4 \ PSoC创建者\bin /sjPalel.exe”失败(0xfffffffff)从报告文件:CypStestGame=“数字放置”& gt;错误:PLM.M046:E2806:无法放置固定的功能块。有关详细情况,请参阅报告文件。C:\CyPress \ PSOC创建者\\pSOC创建者\BION/SJPADRIE.exe”-NETLIST-VH2“TimePo.VH2”-ARCH文件“C:\程序文件(x86)\ CyPress \ PSOC创建者\ 4 \ PSOC创建者\ DEV/ARCH/P4YUDB2X4.GARK”-RRG文件“C:\程序文件(x86)\ CyPress \ PSoC创建者\ 4 \ PSoC创建者\ DEV/PSOC4AR/RRG.CyDATA文件:Cy\\程序文件(x86)\ CyPress \ PSoC创建者\ 4 \ PSoC创建者\ DeP/PSoC4//5/IRQCONN.CyDATA”-DRQ文件“C:\程序文件(x86)\ CyPress \ PSoC创建者\ 4 \ PSoC创建者\ DEV/PSoC4/4/TrigGrCON.CyDATA”-DSI CONN文件“C:\程序文件(x86)\ CyPress \ PSoC创建者\4 \ PSoC创建者\ DEV/PSoC4/5/DSCONN.CyDATA——PIN文件“Pin S124-VFBGA.XML”-LIB文件“TimePo.LIB”-SDC文件“TEMP.SDC”——IO PCF“TEMP.PCI”-Outdir。CypStestGame=“详细放置消息”& gt;i2807:不能放置以下实例:\UBFS:EP3ODMA\\:UBFS:EP4DMA\\,UBFS:EP6IDMAD:USBODMA,UBDNDMA DMA布局:DMA 0:&空;GT;DMA 1:&空;GT;DMA 2:TXDMABUD1 DMA 3:TXDMABAR0DMA 4:&空;DMA 7:&空;G.DXABAB1 DMA 10:TXDMAB1 DMA 12:RXDMAY1 DMA 13:RXDMAMA0DMA 14:\UBFS:EPS1DMA\DMA 15:\EPS2DMA\DMA 16:&空;GT;DMA 17:&空;& DMA:&空;MPT>DMA 6:&空;GTY≫DMA 21:&空;GT;DMA 23:&空;GT;DMA 25:&空;& DMA 26:&空;& DMA 27:&空;和DMA 28:&空;& DMA 29:&空;& DMA 30:&空;& DMA 31:&空;E2806:无法放置固定的功能块。有关详细情况,请参阅报表文件。和/或Cypestag & gt;Cypjj.CaseV01.Zip817.5 K 以上来自于百度翻译 以下为原文The attached project can be built if the links between XxDMA and XxDMAB are removed.But if the 3 chain links are added, it fails to place some of the USB DMA.It will also build if many of the TxDMA_X is disabled. I'm not using all the DMAs - what is the problem? Error message: Error: plm.M0046: E2806: Failed to place fixed-function blocks. See the report file for details. Error: plm.M0046: "C:\Program Files (x86)\Cypress\PSoC Creator\4.0\PSoC Creator\bin/sjplacer.exe" failed (0xFFFFFFFF) From the Report File: Error: plm.M0046: E2806: Failed to place fixed-function blocks. See the report file for details. "C:\Program Files (x86)\Cypress\PSoC Creator\4.0\PSoC Creator\bin/sjplacer.exe" --proj-name "Temp" --netlist-vh2 "Temp_p.vh2" --arch-file "C:\Program Files (x86)\Cypress\PSoC Creator\4.0\PSoC Creator\dev/arch/p4_udb2x4.ark" --rrg-file "C:\Program Files (x86)\Cypress\PSoC Creator\4.0\PSoC Creator\dev/psoc4/2/route_arch-rrg.cydata" --irq-file "C:\Program Files (x86)\Cypress\PSoC Creator\4.0\PSoC Creator\dev/psoc4/2/irqconn.cydata" --drq-file "C:\Program Files (x86)\Cypress\PSoC Creator\4.0\PSoC Creator\dev/psoc4/2/triggerconn.cydata" --dsi-conn-file "C:\Program Files (x86)\Cypress\PSoC Creator\4.0\PSoC Creator\dev/psoc4/2/dsiconn.cydata" --pins-file "pins_124-VFBGA.xml" --lib-file "Temp_p.lib" --sdc-file "Temp.sdc" --io-pcf "Temp.pci" --outdir . I2807: The following instances could not be placed: \USBFS:ep3_dma\, \USBFS:ep4_dma\, \USBFS:ep6_dma\, USBOutDMA, USBInDMA DMA placement: DMA 0: DMA 1: DMA 2: TxDMAB_1 DMA 3: TxDMAB_0 DMA 4: DMA 5: DMA 6: DMA 7: DMA 8: RxDMAB_1 DMA 9: RxDMAB_0 DMA 10: TxDMA_1 DMA 11: TxDMA_0 DMA 12: RxDMA_1 DMA 13: RxDMA_0 DMA 14: \USBFS:ep1_dma\ DMA 15: \USBFS:ep2_dma\ DMA 16: DMA 17: DMA 18: DMA 19: DMA 20: DMA 21: DMA 22: DMA 23: DMA 24: DMA 25: DMA 26: DMA 27: DMA 28: DMA 29: DMA 30: DMA 31: E2806: Failed to place fixed-function blocks. See the report file for details. Temp.cyprj_.Archive01.zip 817.5 K
2019-01-21 09:12
背景:MPLAB X IDE V4.15,XC32 V2.05,ValueV2.05,PIC32 MZ2048 EFH100I应该指出,我已经成功地获得了LIFEUPDENT来处理我的应用程序,完成了自定义条件来强制引导程序,等等。Muny驱动程序不允许您更新BFM?换句话说,它只允许编程的PFM。我得到的印象,和谐的驱动程序没有,但手摇驱动程序可以这样做:HTTP://www. MyCHIP.COM/FUMMS/M92667 5.ASPXF如果回答前一个问题是,那么有任何计划来改变这一点吗?我问的原因是,它似乎是值得的编程BFM和PFM的未使用的面板在同一时间通过可加载。这样,您可以相对容易地更新配置位,而较少担心可能会失去一致性。我真的怀疑我必须改变配置位设置经常,如果在所有,所以也许这不是那么多的价值。更糟糕的是,它似乎使设备变得更容易,就像引导加载程序被破解一样,你是怎么回来的?彻底改变配置位意味着一些严重的变化(至少对我来说),所以最好是通过传统的程序员在那个事件中更新板。我想得越多,如果不能更新BFM,那么和声的设置实际上是有意义的。用户总是可以通过应用程序更新PFM,但是Bootloader将作为回落而存在,并且更难于砖块。在配置位之外,这允许相当多的多功能性。 以上来自于百度翻译 以下为原文 Background: MPLAB X IDE v4.15, XC32 v2.05, Harmony v2.05, PIC32MZ2048EFH100 I should point out that I've successfully gotten the liveupdate to work on my application, complete with custom conditions to force the bootloader, etc. I am using Harmony's stock driver, though.Is it true that the stock Harmony driver does not allow you to update a BFM? In other words, it only allows programming of a PFM. I get the impression that Harmony's driver does not, but hand rolled drivers can and do: http://www.microchip.com/forums/m926675.aspxIf the answer to the previous question is yes, then are there any plans to change this? The reason I ask is that it seems like it might be worthwhile to program both the BFM and the PFM of the unused panel at the same time through loadables. This way you could update the configuration bits relatively easily with less fear that things might lose consistency. I truly doubt that I'll have to change the configuration bit settings that often, if at all, so perhaps this isn't of that much value. Worse, it seems like it makes bricking the device easier as if the bootloader gets crapped up how do you get back? Drastically changing the configuration bits implies some serious changes anyway (at least to me), so it's probably best to just update the board through a traditional programmer in that event.The more that I think about it, Harmony's setup actually makes a lot of sense if it can't update the BFM. The user can always update the PFM through the application, but the bootloader will be there as a fall back and it's more difficult to brick. Outside of the configuration bits, this allows for quite a bit of versatility.
2018-10-15 16:03