|
On Mon, 28 May 2001 23:34:14 -0400
"Fred G. Martin" <fredm@alum.mit.edu> wrote:
> the target of your code is probably the zero page of RAM, where the
> downloader bootstrap routine lives.
>
> so as your code is being downloaded, you're over-writing the
> hc11-ram-based dl comms code and the host side ultimately fails.
Heyho!
Hmmm, are you sure? But why does it work then when i change S0 to S1? I don´t change the memory map with this.
But can somebody tell me a site, where the different S Types are explained? I know S1 (a normal dataset) and S9 (the last dataset) (-so together the S19 Format ;)), but what is S0. My normal Motorola AS has never produced a S0 datasettype, so what does it mean.
And another question: Can someone tell me, how to tell the m68hc11 gcc (particularly the m68hc11 linker) where to put the code in memory. In AS i usually used the directive org, but how does it work here? Do i have to pass the memory location as an option to the linker?
As info: Everything here refers to the 68hc11 GNU Development Chain (http://www.gnu-m68hc11.org).
greetings
Kai
Here is again my original message (if you don´t know what the above is about):
I have problems downloading a self compiled file to my Handyboard (with 68HC11A1).
I just wrote a little test programm:
int main()
{
int foo = 0;
while (foo < 1000)
{
foo++;
}
return(0);
}
and compiled it to a .s19 file with the gnu gcc 68hc11 cross compiler under linux:
m6811-elf-gcc -o tst.s19 -Wl,--oformat=srec tst.c
Then i tried to download that file to my bootstrap switched handyboard with two different downloaders:
a) dl
$> dl tst.s19
6811 .s19 file downloader. Version 7.31 May 21 2001
Copyright Randy Sargent 1994
Using port /dev/ttyS0
Please place board in download mode and press RETURN
To quit, press Q
For help, press H
Downloading 256 byte bootstrap (229 data)
................................................................
................................................................
................................................................
.....................................___________________________
Download successful
Config is 0x0C
Loading tst.s19
Sending tst.s19
Fatal internal error:
Unrecognized .s19 record: S0
Speicherzugriffsfehler
b) dlm
$> dlm -p /dev/ttyS0 tst.s19
DLM: 6811 File downloader with Intelligent EEPROM burn by Ken Hornstein
Based on original DLM program by Fred Martin
Adapted by Matthew Stock
Downloading eeprom loader to RAM at 1200 baud ... +
Synchronizing with board ...ok
Sending tst.s19 to RAM at 9600 baud ... |Board memory error: wanted 0x00, got 0x3e at address 0x0000
|Board synchronization error.
As you can see both downloader failed to download the little program. But dl is able to download the pcode file of free-ic (dlm also does not work here; i get the same Board memory errors -but many many more- as with my program).
The strange thing is, that if i change the original first line of the tst.s19 file, which is
S00A00007473742E7331398F
to
S10A00007473742E7331398F
the downloader dl downloads this file correct.
Can someone tell me why all .s19 files compiled with the gcc cross compiler start with S0, but the downloader dl just accept S1 ? And how do i get the dlm to work? Why do i get these Board Memory Errors with every .s19 file i tried to download?
greetings
Kai
|
|
Message has 1 Reply: | | Re: download .s19 problem
|
| (...) Ok, i searched a bit in the net and found out that S0 is a header record (with no usefull information, or!?). So it seems to me that dl from Randy Sargent doesn´t work with *.s19 files with a S0 header (or does it work for anyone else?). So (...) (23 years ago, 7-Jun-01, to lugnet.robotics.handyboard)
|
Message is in Reply To:
| | download .s19 problem
|
| Hy! I have problems downloading a self compiled file to my Handyboard (with 68HC11A1). I just wrote a little test programm: int main() { int foo = 0; while (foo < 1000) { foo++; } return(0); } and compiled it to a .s19 file with the gnu gcc 68hc11 (...) (24 years ago, 28-May-01, to lugnet.robotics.handyboard)
|
4 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|