USB Bootloader

[graaja]

Hi All,

I have the first version of a working USB bootloader. I am attaching the files here. Following are the contents.

1. Bootloader Template project. Project on which bootloader based applications can be developed.
2. Example Bootloader project. This project implements the bootloader. The main application runs with USB as HID device. And when an enter bootloader command is received over the USB, the bootloader is entered. A small VB program to issue this enter bootloader command is also attached.
3. Driver setup. This is the driver for the USB bootloader. I have used the same driver provided by Matt for his Bulk Ping Example.
4. Bulk_Ping_Host_No_MFC. I have modified the project provided by Matt for the Bulk_Ping demo to implement the bootloader host. This program can read the hex file, and send the bootloader command and packets to the psoc to execute a bootload.
5. EnterBootloader. A VB project to make the example project to enter bootloader. This is to demonstrate the capability of the application to enter bootloader from the user code
6. Bootloader document. A draft document that describes the bootloader.

The shortfalls of the above project are:
1. I have not used a dedicated driver for the bootloader. So the bootloader will enumerate as Bulkping Example. But this can be modified as per requirements by user.
2. As I am not that good in VC++, the bootload host application is a very crude implementation.

[Alejandro]

Hi,

1. I have not used a dedicated driver for the bootloader. So the bootloader will enumerate as Bulkping Example. But this can be modified as per requirements by user.

I am working in a project that involves CY8C24794 and I don't know very much about Windows programming nor VC++. The example of Bulk Ping is very useful, it seems really easy to communicate with the PSOC. But my question is: How can I modify the project to have a different enummeration name? Do I have to write a new dedicated driver (I don't know how to do it)? Can I just modify some things in AsyncPing.inf and change the name of the dll?

Thank you very much!

[graaja]

Hi Alejandro,

Yes. You can modify the bulkping.inf (I have used this as driver for bootloader, not the asyncping). Change the VID and PID at 2 places

[CMS]
%VID_PID.DeviceDesc%=BULKPING,USB\VID_04b4&PID_E001
VID_PID.Ids="USB\VID_04b4&PID_E001"

Replace 04b4 with your VID and E001 with your PID.

Also you can change the "Bulk Ping Example" string to change the way the computer reports the device.
VID_PID.DeviceDesc="Bulk Ping Example"

I think these modifications should be enough. You can keep the name of bulkping.sys as it is. Maybe someone more experienced on this subject can add their comments if I am wrong.

[Alejandro]

Thanks a lot. I will try it as soon as I have the Development Kit.

[graaja]

An updated bootloader template. Code added to clear WDT regularly, if the user code had enabled WDT prior to entering bootloader.

[graaja]

Hi All,

Probably, this is a bit late to be posting this thread.

I just thought to make clear that the code posted in this topic is not an official version and users should use it at their own risk (I believe users are already aware of this ).

Work is in progress at Cypress to finalize the bootloader.

[Boris]

Hi

I tried to use your Bootloader but not with HID but with a driver.
It doesn't work and the device is not responding.
Tne device is entering in Bootloader because the first 10 bytes packet is received and the device answer with the correct error code. The .hex file is open and read properly. But when it start to load the Code the device is not responding and reset.

Maybe you know something about this problem because i did not modify your code.

Regards

Boris

[Boris]

Hi ,

In fact the problem is when the bootloader call the flashwriteLite function in flashAPI.asm. The Store of the data is correct and when the program write the USB is deconnected so the device is not responding.

Please Help me!!!

Boris

[graaja]

Hello Boris,

The bootloader is not a HID class device. It is a vendor specific class with 64 byte IN endpoint and 64 byte OUT endpoint. Did you try doing the bootload using the VC++ application which is found in the zip file that I had posted earlier?

Also, if you are using ICE-CUBE to emulate the bootloading, it will not work. The ICE takes about 2 seconds to write a single block of flash and during this time, the USB bus will get reset. If you are satisfied that the block write and the basic bootload functions are correct, try the process on a chip directly.

[Baka_boy]

Hi guys, followed the simple steps from the app note. Created a clone project based on the template (1.1) provided. To test it I connected S1/S2 (USB eval board) to enter bootloader mode after all modules and interrupts are stopped/disabled. Seems to "work" (i.e. hear discon/re-connect beep from PC). Thing is I can't bootload it using the modified bulk_ping. The bulk_ping program can connect, parses the hex file correctly, but fails on the first read from device (i.e. device status). Anyone might know what I might be doing wrong?

[graaja]

Are you using the debugger? The bootload will not work with the debugger. You will have to disconnect the debugger and then try the bootload process.

[Baka_boy]

Hi graaja,

No I'm using the mini-programmer provided with CY3214, I also have the ICE4k but I've never used it with the 24794. Please note that I also have this very weird problem with the original "bulk_ping" program. That the FIRST ping ALWAYS fails, unless i do the following code after the USB has finished enumeration.

Code: Select all

USBFS_LoadInEP(BULK_EP_IN, g_packet, BULK_PACKET_SIZE, USB_TOGGLE);


I haven't found/read any reason why I would need to do that, but it just works that way -__-'. I've also have tried on all of my 3214 evaluation boards (i have 2), and both operate the same way. I'm trying to modify the provided example at the moment so that i can test it with the bulk_ping programmer. The VB program says it enters bootload mode successfully.

[graaja]

Hello Baka,

In the usb bootloader, this initialization of the InEP with USB_TOGGLE flag is done. Also, the bootloader code is a working version which has been tested. I have done 3 more versions after 1_1, but they are for watchdog functionality etc. I am attaching the latest version of the bootloader template and the example project. Check if this works.

[Baka_boy]

Okay, thanks for the help! I'll let you know if it works on my setup, got sidetracked a bit by some other project.

[graaja]

Yes. It should work with the bootloader utility as it is.

[AndyW]

I dont agree that the bootloader should necessarily fail when used with the debugger. There is no doubt that it does fail though. But if the issue was caused by a USB reset, why would this happen? The USB SIE should continue to NAK requests during this time and the host should not object.
A simple utility which copies the same block of data to sucessive blocks of flash (obviously not the same blocks which the code occupies) also fails with the debugger even if it does nothing related to USB. The failure always happens on the same block, but the block changes with the exact start block number. There is no doubt that there is a bug in flash writing with the cube. I posted a topic on the main forum about this.
My own bootloader works fine with the debugger if I disable the block count and simply write the same flash block repeatedly as a test. No USB reset occurs at all despite the entire process taking 30 seconds to complete.
I was intending to post a support request about this but have not had time to package up a test routine to attach. The ideal way to observe this behaviour is use the LCD display to display the incrementing block number.
Andy

[graaja]

Hello Andy,

I had come across this problem when I had started working with the bootloader. This was discussed in the following thread.

viewtopic.php?t=952

It would be great if you can give some details of the bug you have found when you can find the time. That may help in identifying the exact cause of the problem.

[saj]

Is there a boot loader that can work over the serial port
Thanks

[graaja]

Is there a boot loader that can work over the serial port
Thanks

There is an app note, AN2100 on this.

[mschwarz]

Hello Raaja,

after fiddling a little bit with your project, I saw you used the USB libs twice. One for normal mode and one for the protected mode area. Ok, this costs roundabout 3kByte extra, but much worser the copied USB code is not up to date. For example in USB.asm (which normally is USBFS.asm) there is the 12MHz workaround and the other library improvements not implemented. Is there any possibility to avoid using the libs twice? As far as I can see only the memory location is important.

Or could we do somehing like a "lib copy routine", which takes the most recent versions and patches only the location which are really need to be tweaked?

cu, Mirko.