Hi all,
I'm using codewarrior to develop hcs12c64 project. I
use a P&E usb multilik to load firmware.
After generating binary data, I can load firmware
using .abs (used as default by Hi-wave) and also using
.s19 file. However I can't do it using .phy file
(error message: error while writing to F0000...F0200 -
mo memory at this address).
Of course c24 doesn't have memory at this address and
I check it in .s19 file. However .phy file seems to
use this range of addresses to load firmware. The .phy
is importante cause I will need to use it to load
firmware by Cyclone Pro (it is not loading firmware
correcly from .phy file).
Queations:
-is there any configuration in linker options to
generate .phy file correctly;
-can hi-wave load firmware from .phy file?
Thanks in advance
Wandson
__________________________________________________
s-record files
Started by ●January 21, 2006
Reply by ●January 23, 20062006-01-23
Hi Wandson,
First, if the *.s19 works for you, stick with it.
The *.phy contains the same code, just the addresses are differently
encoded.
The Metrowerks tools are always using the format as it is used in the
*.s19 file, some other vendors use an other SRecord address encoding
schema, hence the *.phy.
Note that there is no built in knowledge about the address encoding of
the *.phy file in the tools, this encoding is completely done in the
*.bbl file which is also in your project.
So if you do need some other kind of addressing, check & modify the
*.bbl file.
For HIWAVE, use the *.s19 to load the code, not the *.phy.
Daniel
PS: In order to avoid the generation of this *.phy file, remove the
*.bbl from the project. If you need additional different formats, add
additional *.bbl files.
Wandson Santana wrote:
>Hi all,
>
>I'm using codewarrior to develop hcs12c64 project. I
>use a P&E usb multilik to load firmware.
>
>After generating binary data, I can load firmware
>using .abs (used as default by Hi-wave) and also using
>.s19 file. However I can't do it using .phy file
>(error message: error while writing to F0000...F0200 -
>mo memory at this address).
>
>Of course c24 doesn't have memory at this address and
>I check it in .s19 file. However .phy file seems to
>use this range of addresses to load firmware. The .phy
>is importante cause I will need to use it to load
>firmware by Cyclone Pro (it is not loading firmware
>correcly from .phy file).
>
>Queations:
>-is there any configuration in linker options to
>generate .phy file correctly;
>-can hi-wave load firmware from .phy file?
>
>Thanks in advance
>Wandson
>
>__________________________________________________
> >
>Yahoo! Groups Links
First, if the *.s19 works for you, stick with it.
The *.phy contains the same code, just the addresses are differently
encoded.
The Metrowerks tools are always using the format as it is used in the
*.s19 file, some other vendors use an other SRecord address encoding
schema, hence the *.phy.
Note that there is no built in knowledge about the address encoding of
the *.phy file in the tools, this encoding is completely done in the
*.bbl file which is also in your project.
So if you do need some other kind of addressing, check & modify the
*.bbl file.
For HIWAVE, use the *.s19 to load the code, not the *.phy.
Daniel
PS: In order to avoid the generation of this *.phy file, remove the
*.bbl from the project. If you need additional different formats, add
additional *.bbl files.
Wandson Santana wrote:
>Hi all,
>
>I'm using codewarrior to develop hcs12c64 project. I
>use a P&E usb multilik to load firmware.
>
>After generating binary data, I can load firmware
>using .abs (used as default by Hi-wave) and also using
>.s19 file. However I can't do it using .phy file
>(error message: error while writing to F0000...F0200 -
>mo memory at this address).
>
>Of course c24 doesn't have memory at this address and
>I check it in .s19 file. However .phy file seems to
>use this range of addresses to load firmware. The .phy
>is importante cause I will need to use it to load
>firmware by Cyclone Pro (it is not loading firmware
>correcly from .phy file).
>
>Queations:
>-is there any configuration in linker options to
>generate .phy file correctly;
>-can hi-wave load firmware from .phy file?
>
>Thanks in advance
>Wandson
>
>__________________________________________________
> >
>Yahoo! Groups Links
Reply by ●January 23, 20062006-01-23
Daniel,
Thanks for your help. I see hi-wave doesn't read .phy
file (it seems read it as .s19 record). Anyway I found
out the problem. It was on board, not in the .phy
file.
Wandson
--- Daniel Friederich <dfriederich@dfri...>
wrote:
> Hi Wandson,
> First, if the *.s19 works for you, stick with it.
> The *.phy contains the same code, just the addresses
> are differently
> encoded.
> The Metrowerks tools are always using the format as
> it is used in the
> *.s19 file, some other vendors use an other SRecord
> address encoding
> schema, hence the *.phy.
>
> Note that there is no built in knowledge about the
> address encoding of
> the *.phy file in the tools, this encoding is
> completely done in the
> *.bbl file which is also in your project.
> So if you do need some other kind of addressing,
> check & modify the
> *.bbl file.
> For HIWAVE, use the *.s19 to load the code, not the
> *.phy.
>
> Daniel
>
> PS: In order to avoid the generation of this *.phy
> file, remove the
> *.bbl from the project. If you need additional
> different formats, add
> additional *.bbl files.
>
> Wandson Santana wrote:
>
> >Hi all,
> >
> >I'm using codewarrior to develop hcs12c64 project.
> I
> >use a P&E usb multilik to load firmware.
> >
> >After generating binary data, I can load firmware
> >using .abs (used as default by Hi-wave) and also
> using
> >.s19 file. However I can't do it using .phy file
> >(error message: error while writing to
> F0000...F0200 -
> >mo memory at this address).
> >
> >Of course c24 doesn't have memory at this address
> and
> >I check it in .s19 file. However .phy file seems to
> >use this range of addresses to load firmware. The
> .phy
> >is importante cause I will need to use it to load
> >firmware by Cyclone Pro (it is not loading firmware
> >correcly from .phy file).
> >
> >Queations:
> >-is there any configuration in linker options to
> >generate .phy file correctly;
> >-can hi-wave load firmware from .phy file?
> >
> >Thanks in advance
> >Wandson
> >
> >__________________________________________________
> >
> >
> >
> >
> >Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>
__________________________________________________
Thanks for your help. I see hi-wave doesn't read .phy
file (it seems read it as .s19 record). Anyway I found
out the problem. It was on board, not in the .phy
file.
Wandson
--- Daniel Friederich <dfriederich@dfri...>
wrote:
> Hi Wandson,
> First, if the *.s19 works for you, stick with it.
> The *.phy contains the same code, just the addresses
> are differently
> encoded.
> The Metrowerks tools are always using the format as
> it is used in the
> *.s19 file, some other vendors use an other SRecord
> address encoding
> schema, hence the *.phy.
>
> Note that there is no built in knowledge about the
> address encoding of
> the *.phy file in the tools, this encoding is
> completely done in the
> *.bbl file which is also in your project.
> So if you do need some other kind of addressing,
> check & modify the
> *.bbl file.
> For HIWAVE, use the *.s19 to load the code, not the
> *.phy.
>
> Daniel
>
> PS: In order to avoid the generation of this *.phy
> file, remove the
> *.bbl from the project. If you need additional
> different formats, add
> additional *.bbl files.
>
> Wandson Santana wrote:
>
> >Hi all,
> >
> >I'm using codewarrior to develop hcs12c64 project.
> I
> >use a P&E usb multilik to load firmware.
> >
> >After generating binary data, I can load firmware
> >using .abs (used as default by Hi-wave) and also
> using
> >.s19 file. However I can't do it using .phy file
> >(error message: error while writing to
> F0000...F0200 -
> >mo memory at this address).
> >
> >Of course c24 doesn't have memory at this address
> and
> >I check it in .s19 file. However .phy file seems to
> >use this range of addresses to load firmware. The
> .phy
> >is importante cause I will need to use it to load
> >firmware by Cyclone Pro (it is not loading firmware
> >correcly from .phy file).
> >
> >Queations:
> >-is there any configuration in linker options to
> >generate .phy file correctly;
> >-can hi-wave load firmware from .phy file?
> >
> >Thanks in advance
> >Wandson
> >
> >__________________________________________________
> >
> >
> >
> >
> >Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>
__________________________________________________
