Posted by James on June 9, 2004, 12:53:08, in reply to "FDT failure on notebook pc!" Protocol A kernels have the crystal frequency compiled into them so you will need to recompile if your board differs from the default (see xtal.h). Protocol B Boot Mode kernels allow the crystal frequency to be set at run time in the FDT project; if this is set incorrectly, FDT will autobaud and download the microkernel but it will fail when setting the new baud rate before the main kernel is downloaded. Note that User Mode Protocol B kernels still need the initial BRR value compiled in (see gentest.h) so that they can set the SCI port to 9600 baud for initial communications. Hope this helps! --Previous Message--
194.131.190.1
It looks like the problem is that you have the project set to Kernel Resident (Kernel already running). This is only used to reconnect to a main kernel if it is still running on the target device from a previous session and it has not been reset, and it will bypass the autobaud and kernel downloading. In Boot Mode without the kernel resident option set, FDT will try to auto baud the device (which must be in Boot Mode and reset) and it will then download the kernel. The device will be automatically erased upon a successful connection and you should then be able to reprogram it.
: Hi!
: I have some problems reprogramming
: the flash of my EVB2623F board. First
: I tried FDT v1.5, but it didn't
: manage to connect. I read the
: Known_problems.txt file, and tried
: the serial port fix mentioned there
: because I run this on a notebook pc.
: But it didn't help, so I tried FDT
: v3.1 instead (with the Protocol A
: plug-in to support my EVB). I still
: have problems to connect though, and
: v3.1 doesn't feature any serial port
: fixes. Here's my log from v3.1:
: Connecting to device 'H8S/2623F' on
: 'COM1'
: Configuration: 'BOOT Mode' connection
: using the HMSE Universal Programming
: Board
: Opening port 'COM1' ...
: Loading Comms DLL
: Loaded Comms DLL
: Looking for running kernel...
: Unable to download DeviceID from
: target
: No running kernel found, booting
: device...
: Resetting interface
: Taking RESET line low (Reset On)
: Enabling 12V supply
: Enabling Vpp supply
: Enabling MDx
: Taking RESET line high (Reset Off)
: Booting FZTAT device
: Error No 15005: 'COM1:' read time out
: Using micro-Kernel :
: 'D:\Voodoo\FDT3.1\Kernels\ProtA\2623\Hitachi\0_0_00\uGen2623.cde'
: Error No 15032: Interface failed to
: respond
: Error No 15019: Download() failed
: Error No 15005: 'COM1:' read time out
: Error No 15035: Unable to get version
: information from interface
: Unloaded Comms DLL
:
: Anyone else experienced the same
: problems?
: Regards
: Henrik
:
:
:
Message Thread:
« Back to thread