Hello,
I want to use the Mfg_tool (Rel. 1.0.1) to download an SW binary with a simply blinking LED into 4SPI flash device which is connected at 4SPI1 interface of Vybrid VF65xx but sofar all tryings are failed.
What should be set exactly in ucl2.xml to be able to do it ?
This was the last settings I tried with, but without any success:
<LIST name="vybrid-qspi-led" desc="Boot Vybrid FW"> | |
<CMD state="BootStrap" type="boot" body="BootStrap" file="u-boot.imx">Loading U-boot</CMD> | |
<CMD state="BootStrap" type="jump"> Jumping to OS image. </CMD> | |
<CMD state="Updater" type="push" body="qspiinit dev=0">Initializing QSPI</CMD> | |
<CMD state="Updater" type="push" body="pipeqspi addr=0x50000000" file="files/FNLD_A.bin">Sending and writing QSPI Led Sample</CMD> | |
<CMD state="Updater" type="push" body="$ !">Done</CMD> |
</LIST>
I would be very appreciated for any hints or answers, thank you in advance.
已解决! 转到解答。
Hi,
Never mind, I think I just got it working. I used a u-boot binary that is about 200K large and after checking it it was written, it seems it was.
Please use the attached file. Sorry for the delay but it was not an easy task to debug and find out the problem. I hope this is the good one. It worked on my side.
Best Regards,
Alejandro
alejandrolozano do you have an update?
alejandrolozano please continue with the follow up.
reminder
Alejandro Lozano Lozano please continue with the follow up.
alejandrolozano please help to continue with the follow up?
Hi Tai,
I have delved into this and this version of mfgtool supports only the TWR board which features a QSPI only in the QSPI0 module only.
It seems that just like you said a few changes need to be performed in the U-boot source code. On my side the only way to test it is with the auto board.
If you can, please try to first re-map the UART pins that conflict with the QSPI1 module. I will do that too and I will let you know how it goes.
/Alejandro
Hi,
According to the ucl2.xml file the uboot image loaded by mfgtool performs this commands pipeqspi.
I wonder if you can try to execute this command booting uboot from SD. I mean try to flash the qspi using uboot and that command.
Please let me know the result.
Best Regards,
Alejandro
Hi Alejandro,
perhaps I misunderstand you, or there is a missunderstanding.
I never tried to boot uboot from SD.
As I described at my initial posting, I want to use the Mfg_tool (Rel. 1.0.1) to download a SW binary file with a simply blinking LED into 4SPI flash device which is connected at 4SPI1 interface of Vybrid VF65xx.
With following settings, Mfg_tool doesn´t hang anymore, performed with status "done" and green bar, BUT the flash content has been erased only (as I verified the content of flash device with JTag debugger), binary file was not loaded into 4SPI flash device.
HW:
BOOT_MODE[1:0] = 01 (serial downloader)
ucl2.xml:
<LIST name="vybrid-qspi-led" desc="Boot Vybrid FW"> | |
<CMD state="BootStrap" type="boot" body="BootStrap" file="u-boot.vybrid">Loading U-boot</CMD> | |
<CMD state="BootStrap" type="jump"> Jumping to OS image. </CMD> | |
<CMD state="Updater" type="push" body="qspiinit dev=1">Initializing QSPI</CMD> | |
<CMD state="Updater" type="push" body="pipeqspi addr=0x50000000" file="files/FNLD_A.bin">Sending and writing QSPI Led Sample</CMD> | |
<CMD state="Updater" type="push" body="$ !">Done</CMD> |
</LIST>
Best Regards,
Tai-Phan
MfgTool.log with the last 12 log.-entries:
...
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT-Disk(E), Hub:3-Port:8
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT, Notify
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive
ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.
ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1
ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 1
ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is qspiinit dev=1
ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is ubootcmd qspierase 0x50000000
ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is pipeqspi addr=0x50000000
ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ !
Hi,
I am also getting the same issue while trying to flash Vybrid's QuadSPI.
I am using the "vybrid-qspi-led" profile for loading the binary image.
The MFG tool successfully executes the "BootStrap" commands but hangs while it tries to execute the first "Updater" command:
<CMD state="Updater" type="push" body="qspiinit dev=0">Initializing QSPI</CMD>
Attached is the log fie generated by the tool.