topic Re: Re: Re: Using Mfg_tool to flash at QuadSPI1 interface in Vybrid Processors

Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Mon, 02 Feb 2015 10:54:33 GMT

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.

Re: Using Mfg_tool to flash at QuadSPI1 interface

irfanshahid — Mon, 02 Feb 2015 11:42:53 GMT

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.

Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Mon, 02 Feb 2015 13:20:02 GMT

hello,

according to this file: ...\U-boot_src\u-boot\drivers\spi\vf610_qspi.c: qspiinit dev=1

<CMD state="Updater" type="push" body="qspiinit dev=1">Initializing QSPI</CMD>

after setting with the correct value in ucl2.xml: initializing QSPI by Mfg_tool is failed, behaviour confirmed

due to logging file:

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[1]: PortMgrDlg(0)--MSCDevice--Command Push(no file) excute failed

ModuleID[2] LevelID[10]: CmdOperation[0], current command executed failed, so SetEvent(hDevCanDeleteEvent)

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is qspiinit dev=1

ModuleID[2] LevelID[1]: PortMgrDlg(0)--MSCDevice--Command Push(no file) excute failed

ModuleID[2] LevelID[10]: CmdOperation[0], current command executed failed, so SetEvent(hDevCanDeleteEvent)

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is qspiinit dev=1

What is the reason for this failure ? Thank you in advance for any hints and answers.

Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Wed, 04 Feb 2015 15:37:05 GMT

Hello,

after several tryings I found out that BOOT_MODE[1:0] shall be set (even image in flash in invalid or flash is empty):

BOOT_MODE[1:0] = 01 (serial downloader)

Mfg_tool doesn´t hang anymore, performed with status "done" and green bar, BUT

the flash content has been erased ONLY, it seems that this CMD:

<CMD state="Updater" type="push" body="pipeqspi addr=0x50000000" file="files/FNLD_A.bin">Sending and writing QSPI Led Sample</CMD>

is NOT executed or execution is failed.

What can I look for or try out ?

Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Fri, 13 Feb 2015 09:10:20 GMT

I want to ask gently if there is any new acknowledgement about this issue ?

Re: Using Mfg_tool to flash at QuadSPI1 interface

alejandrolozan1 — Mon, 02 Mar 2015 20:47:56 GMT

Hi,

You have to remember that the image to load needs the IVT and the qspi structure so the ROM code boots correctly.

Otherwise it will not boot. Have you tried with the default image?

Best Regards,

Alejandro

Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Tue, 03 Mar 2015 09:11:51 GMT

Hi Alejandro,

thank you for your reply.

On our developement HW there is a JTag interface, and the JTag Debugger of Lauterbach is in use.

I could load the binary file with the Debugger into 4SPI flash by using the serial flash programming script provided by Lauterbach, and I can also verify the content of 4SPI flash with the debugger,

all is running well, the image with IVT is correctly set.

As I described (posting at 04.02.2015 08:37): ...Mfg_tool with status "done" and green bar, BUT the flash content has been erased ONLY.

For the series HW we need the Mfg_tool to do the initial flashing so it is absolutely essential.

I would be appreciated for any proposal to solve this problem, and thank you in advance.

Best Regards,

Tai-Phan

Re: Using Mfg_tool to flash at QuadSPI1 interface

alejandrolozan1 — Tue, 03 Mar 2015 20:22:29 GMT

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

Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Wed, 04 Mar 2015 08:48:24 GMT

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

Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Thu, 05 Mar 2015 11:34:53 GMT

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 $ !

Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Thu, 05 Mar 2015 15:13:26 GMT

Hi Alejandro,

today I was trying to evaluate the Mfg_tool with the TWR-VF65GS10 again. As I could see u-boot SW also outputs logging data via SCI1 interface:

PTB4 (SCI1_TX), PTB5 (SCI1_RX)

With HTerm at J8 (RS232) logging data can be recorded.

On our target HW the 4SPI flash device is connected at QSPI1 interface of Vybrid VF6xx:

As you can see, QSPI1_A_DATA0 is at PTB4, so there is a conflict with PTB4 of Vybrid VF6xx.

If my assumption is correct Mfg_tool cannot support booting 4SPI flash at QSPI1 interface of Vybrid VF6xx.

Can you confirm this issue ?

Best Regards,

Tai-Phan

Re: Using Mfg_tool to flash at QuadSPI1 interface

alejandrolozan1 — Thu, 05 Mar 2015 20:19:41 GMT

Hi,

As I see you should be able to boot from QSPI1, I mean that the BootROM code should be able to get the uboot image from QSPI memory. But after U-boot is runnig, this configures the SCI_Tx pin after that you won't be able to communicate with the QSPI memory.

Best Regards,

Alejandro

Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Fri, 06 Mar 2015 09:00:43 GMT

Hi Alejandro,

after this acknowledement do you schedule to provide an update for Mfg_Tool for VF65xx soon ?

Since the Mfg_tool generates itsself a log.-file also, so it is worth to reconsider if the u-boot needs to output log.-data via SCI1 interface also ?!

Currently we have got some functional HW-models to be put into operation so could you provide a quick support about this issue ?

Best Regards, and thank you in advance for any quick support

Tai-Phan

Re: Using Mfg_tool to flash at QuadSPI1 interface

karina_valencia — Fri, 13 Mar 2015 15:00:26 GMT

alejandrolozano please help to continue with the follow up?

Re: Using Mfg_tool to flash at QuadSPI1 interface

alejandrolozan1 — Fri, 13 Mar 2015 15:16:14 GMT

Sure!, but I will need more time.

/Alejandro

Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Wed, 18 Mar 2015 13:00:51 GMT

Can you give me time estimation when I can expect with an update of Mfg_tool since I need to communicate about this issue internally ?

Re: Using Mfg_tool to flash at QuadSPI1 interface

alejandrolozan1 — Wed, 18 Mar 2015 21:11:08 GMT

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

Re: Re: Using Mfg_tool to flash at QuadSPI1 interface

alejandrolozan1 — Thu, 19 Mar 2015 00:40:52 GMT

Hi,

I wonder if you can try to patch u-boot with this.

Please let me know how it goes.

/Alejandro

Re: Re: Using Mfg_tool to flash at QuadSPI1 interface

BlueJay — Thu, 19 Mar 2015 08:43:24 GMT

Hi Alejandro,

firstable thank you very much for you prompt reponse and support.

I want to ask you if you can possibly send me the "final" binary file (u-boot.imx) with the changes done by you (re-mapping the UART interface) since I currently still walk through the \U-boot_src\u-boot\README with about 6k lines how to build u-boot, and I also need to setup the tool-chain firstly until I can build a version of u-boot, so I will spend lots of time for the first steps.

So if you just need to "press a button" to generate the u-boot binary-file and provide me the binary file I would be appreciated for it very well, I can do afterwards a functional test quickly.

Cheers,

Tai-Phan

Re: Using Mfg_tool to flash at QuadSPI1 interface

alejandrolozan1 — Mon, 23 Mar 2015 14:27:24 GMT

The changes will depend on your board. As you are using a custom board I recommend you to check the pin changes according to your board.

The previous attachment corresponds to the Vybrid Auto board. In other words I suggest you to use as reference that patch according to your board.

/Alejandro