Welcome in the fascinating world of PSoCs!
Ready-made bootloader interfaces are UART, USB and I2C, but you may write your own one. Look here:
The host part has to be written by you to have your logo displayed.
So are you saying the only bootloader host available is the one integrated with the Creator and each company who want their customers to be able to upload in the field need to each write their own version of bootloader host from scratch?
Are most of the current users getting their customers to install creator to give their clients to be able to upload new code or rolling their won?
Which document explains the commands and process we need to communicate with the bootloader form the PC?
I must have been spoilt with the Microchip device as there were several third party Bootloader hosts and source available (We used the TRACE systems one).
You probably misunderstood me. I tried to say, that you have to write your host yourself which usually is a C#-program, reading the Hex-file and transmitting it to the interface. Nothing very complicated.
I ran up the Bootloader Host source provided for Visual C# and it compiles ok and I can make the changes I need without having to roll my own from scratch.
i have seen you are talking about programming a psoc through a c# application,
somebody says that this is possible reading the hex file, i want to ask something about it,
i have seen a programm with the application notes, where you can convert a hex file to a .c file
in that .c file you can see a large vector. is that the information i have to send? if the answer is yes, i can send it
through a serial port like in the UART example in the notes?
I'm new in this world so please forgive me i f i'm saying something without sense.
I implemented a bootloader transport based on raw CANbus frames for use on one of our products.
Added the host support to https://github.com/arachnidlabs/cyflash
Since commit f57187751 it also includes the relevant C code on target side (PSOC3 tested only). The C code is GPL licensed; as far as I'm concerned it may be included as "official" transport by Cypress.
Right now it must be used as "custom interface", I've been too lazy to add all the bells&whistles, besides not being really confortable with C# and windows stuff.