I'm looking for a free AND fast flash-tool for flashing a board with C164 and AMD29F010B over serial port.
I have tried BVLDWin, but it is much too slow and it breaks at 99% with error: Error 533: error in downloading process.
I have checked http://www.keil.com/flash/utilities.asp
And I have even tried MiniMon which looks pretty good, but I am not possible to get a serial communication established. The big problem of all these tools is that they are not and no more supported.
I have found a link in this forum: http://www.keil.com/forum/docs/thread5828.asp , someone looking nearly for the same, but I do not know if they can make it happen. The Idea here is to use the Infineon Memtool for internal flash programming and adapt it to the requirements, but how ??
Please, please give me any hint how can I proceed, if not I have to buy Flashit, ....
thank you in advance for any Tips Sammy
Hallo,
I have solved my problems :-) Thank you very much for all your helps. I have used the free available port monitor from Microsoft (prev. Sysinternals): www.microsoft.com/.../Portmon.mspx Very good tool to trace everything on all serial ports. It showed to me that I do not have serial communication problems, if I use the correct Baudrate (38500, for 16MHz clocked device). To figure this out was really try and error. After that I could use the Flashit tool to get the SYSCON and BUSCON settings. Configuring these values into the Infineon Memtool, the tool works. I do not understand why they always say it is just for internal flash, it is not true. There is even a configuration specialised for a board with C164 and 2 times external AMD29F010B flashes. I hope this information will be useful.
By the way there exist a new version of the virtual serial port simulator com0com (FREE) with a nice GUI see: com0com.sourceforge.net/
When starting with a new microprocessor, I always recommend that the baudrates are verified with an oscilloscope. That will catch any "odd" baudrates caused by incorrect initialization of the processor or the baudrate generator.
I always verify timers, I2C, SPI, ... with an oscilloscope, just in case I have made a mistake that would result in marginal operation.
It is a good point, to use the scope. Just make it clearer: in some cases even with a correct baud rate set at a host side (e.g. PC) you may not have bootstrapping connection established. A reason is in too large baudrate error at MCU side, where the UART is automatically adjusted by h/w. For example, if you are trying to connect at 57600 bps to C16x running at 10 MHz, it will fail since MCU's baudrate would be too different (error ~ 9%), etc. I have not it verified so not sure whether MCU will reply at all. If yes, then you can catch the MCU identification byte (response) with "odd" timing.