Witam! Mam następujący problem : posługuję się już trochę Keilem w wersji demo (niestety) i jak na razie jest ok . Ale ostatnio potrzebowałem zapisać program przez Flipa i powstał problem , Keil tworzy mi pliki HEX-80 a Flip rozumie tylko HEX-86 , lub HEX-386 . Czy można coś na to poradzić? Pozdrawiam Roman Trochę poszperałem i wiem ,że problem wynika z możliwości adresowania pamięci. Wydaje mi się ,że rozwiązaniem jest zastosowanie Flipa w wersji 2.4.4 . Może ktoś posiada wersję źródłową Flip 2.4.4 ? Znalazłem Flip 2.2.4 zapisuje on pliki w postaci hex. Załączam wersje źródłową. Zamykam temat.
Inserting Wait States
" );}
//-- & gt;
Inserting Wait States
" );
//-- & gt;
TYPE
DIRECTIVE
OPTIONAL
ARGUMENTS
Operation
wait
Yes
[ & lt;Nsec & gt; ]
" );
//-- & gt;
The wait directive
is used to insert a pause between two ISP operations, if necessary.
& lt;Nsec & gt; = optional pause duration in seconds.
If no value is specified after the wait
directive, then batchisp waits
for the user to hit the Return
key.
Example of use :
& gt; batchisp -device at89c51rd2 -operation erase F wait 2 blankcheck 0x00 0x3FF
& nbsp;
The & lt;Nsec & gt; argument must be an integer .
& nbsp;
Setting the Debug Mode
" );}
//-- & gt;
Setting the Debug Mode
" );
//-- & gt;
TYPE
SWITCH
OPTIONAL
ARGUMENTS
Setup
-debug
Yes
& lt;traffic_log_file & gt;
" );
//-- & gt;
The - debug switch forces batchisp to display input/output traffic
on the selected medium.
Example of use :
& gt; batchisp -device at89c51rd2 -debug
& quot;C:\temp\mylogfile.txt & quot;
-operation loadbuffer & quot;C:\tmp\test.hex & quot; program verify
If no argument is given to the debug switch, a log file is created by
default in the folder containing the batchisp.exe file.
This default log file name is log.txt.
& nbsp;
& nbsp;
WebHelp 5.10
WebHelp 5.10 System Info
Start Page overview.htm
Skin Name
Generating Time 13:33 03/10/2004
Language ID 1033
Compile Script webhelp5_compile_script.xml
Compile Build Version 11.00.228
Product Name WebHelp 5.10
Authoring Tool Name RoboHelp X3
Setting the AutoISP Mode
" );}
//-- & gt;
Setting the AutoISP Mode
" );
//-- & gt;
TYPE
SWITCH
OPTIONAL
ARGUMENTS
Setup
- autoisp
Yes
{ 0 | 1 } { 0 | 1 }
" );
//-- & gt;
Example of use :
& gt; batchisp -device at89c51rd2 -autoisp
-operation erase F -demo
The - autoisp switch may have
two arguments or no argument at all; there is no other possible number
of arguments.
The first argument is the RESET signal active level. The second argument
is the PSEN signal active level.
With the above command line, batchisp displays the following :
flip2help
= len)
return getHomePage()
else
frames[ " csh " ].location = gasProj[gCurrent] + gCSHFileName;
return " " ;
}
function getRelHomePage(strLocation)
{
var strCurPPath = _getPath(strLocation);
var strOriPPath = _getPath(getHomePage());
var strRelPath = _getRelativeFileName(strOriPPath, strCurPPath);
var strURL = getHomePage() + " # " + strRelPath;
return strURL;
}
function getHomePage()
{
var strHomePage;
var strTmp = location.toString();
var nPos = strTmp.indexOf( " # " );
if (nPos != -1)
{
strHomePage = strTmp.substring(0, nPos);
}
else
{
strHomePage = strTmp;
}
var nPos1 = strHomePage.indexOf(gCSHSuffixName1);
var nPos = strHomePage.indexOf(gCSHSuffixName2);
if (nPos != -1)
{
strHomePage = strHomePage.substring(0,nPos);
if (nPos1 != -1)
strHomePage += " .html " ;
else
strHomePage += " .htm " ;
}
return strHomePage;
}
//-- & gt;
Programming Memory
" );}
//-- & gt;
Programming Memory
" );
//-- & gt;
TYPE
DIRECTIVE
OPTIONAL
ARGUMENTS
Operation
program
Yes
None
" );
//-- & gt;
The program directive is used to program the target memory
with the contents of the ISP buffer.
Before using this directive, you will probably load
the ISP buffer from an input HEX file.
If no addrange directive is
used before the program one,
the range of addresses is the HEX file one.
Example of use :
& gt; batchisp -device t89c51cc01 -hardware PEAKPCAN -operation
loadbuffer & quot;C:\labo\dev\isp\hexfile.hex & quot; program
& nbsp;
Setting Special Bits and Bytes
" );}
//-- & gt;
Setting Special Bits and Bytes
In the device frame of the main window, you can read/write or clear/set
some bytes and bits.
The following table summarizes the main bits and bytes as well as their
status (Read / Write).
" );
//-- & gt;
Bit or Byte Name
Meaning
Status
Signature Bytes
Manufacturer ID + Device ID1+ Device ID2 + Device ID3
R
Device Boot IDs
Bootloader ID1 + Bootloader ID2
R
Hardware Byte
& nbsp;
R
Bootloader Version
& nbsp;
R
BLJB
Bootloader Jump Bit (part of Hardware Byte)
RW
X2
X2 Mode Bit (part of Hardware Byte)
RW
BSB
Boot Status Byte
RW
EB
Extra Byte
RW
SBV
Software Boot Vector
RW
SSB
Software Security Byte
RW
" );
//-- & gt;
In order to modify a byte value, simply
type an hexadecimal value (without any 0x prefix) in the byte entry field;
as soon as two valid characters are typed, the byte is written; no return
key typing is necessary.
The BLJB is active low. Checking its checkbox
in the device frame enables it.
For information about the way some of these
bytes and bits control the microcontroller boot process, please read the
device and the bootloader datasheets.
Programming Memory
" );}
//-- & gt;
Programming Memory
Once you have loaded a HEX file into the buffer, you can program the
target memory by executing the Device
& gt; Program command from the top menu bar.
If you launch a programming operation with a virgin buffer (neither
loaded, nor edited) you will be prompted with the following message :
" );}
else
{ document.write( " " );}
//-- & gt;
When the programming operation completes,
FLIP sets the Boot
Status Byte ( BSB ) to 0x00.
& nbsp;
Logging Results to a File
" );}
//-- & gt;
Logging Results to a File
" );
//-- & gt;
TYPE
SWITCH
OPTIONAL
ARGUMENTS
Setup
-logf
Yes
& lt;out_logfile & gt;
" );
//-- & gt;
The - logf switch lets you specify
a text output file in which batchisp report is written.
The report contents is the same than the one displayed on screen.
Example of use :
& gt; batchisp -device at89c51rd2 -logf
& quot;C:\tmp\rd2_log.txt & quot; -operation loadbuffer & nbsp; & nbsp; & quot;C:\tmp\test.hex & quot;
program verify
& nbsp;
Overview
" );}
//-- & gt;
" ;
strNSS += " p.whs1 {margin-left:1; } " ;
strNSS += " p.whs3 {margin-left:1; } " ;
strNSS += " " ;
document.write(strNSS);
}
//-- & gt;
Overview
FLIP
is a flexible PC-application which lets you program and configure Atmel's
microcontroller devices in-system. This new major version of FLIP
offers the following capabilities :
perform
In-System Programming & nbsp;through
RS232, USB or CAN interfaces.
may
be used through its intuitive Graphical User Interface or launched from
a DOS window (see the batchisp
manual), & nbsp;from
an embedded software IDE like KEIL's uVision2, or even from your own application
(see the ISP Functions Library
manual).
runs
under Windows 9x / Me / NT / 2000 / XP.
supports
Intel MCS-86 Hexadecimal Object, Code 88 file format for data file loading
and saving.
buffer
editing capabilities : fill, search, copy, reset, modify, goto address.
target
device memory control : erase, blank check, program, verify, read, security
level and special bytes reading and setting.
parts
serialization capability (from batchisp
only).
ISP
hardware conditions may be set by software.
the
demo mode emulates ISP operations without any target hardware.
& nbsp;
& nbsp;
Disabling_the_USB_Driver_Installation_Check
" );}
//-- & gt;
Disabling the USB Driver Installation Check
" );
//-- & gt;
TYPE
DIRECTIVE
OPTIONAL
ARGUMENTS
Operation
-no_usbdrvchk
Yes
None
" );
//-- & gt;
The windrvr.sys driver must
be installed prior to performing ISP operations through the USB. By default,
batchisp checks the proper installation
of the driver by scanning the registry and stops if the searched registry
key is not found.
It may happen that the registry key cannot be found although the driver
is properly installed; you can exit this deadlock by using the no_usbdrvchk
directive.
& nbsp;