Re: separate flash space problem -- solved

Hi,

There was no SPM in the original AVR instruction set that SwiftX/AVR was
built on. Further, SwiftX doesn't use it (and nobody asked for it), so it
still isn't there.

But we will add it in our next SwiftX release (current is 3.2.19, so next
will be 3.2.20), in the next few weeks. I'll post a note here when it's
ready.

BTW, it's not hard to extend the assembler! Just browse through the
existing assembler source (SwiftX\Xcomp\AVR\Asm.f) for examples.

Best regards,

Leon Wagner
FORTH, Inc.

> -----Original Message-----
> From: swiftx-bounce_at_forth.com
> [mailto:swiftx-bounce_at_forth.com] On Behalf Of Jach Fong
> Sent: Monday, August 07, 2006 7:57 PM
> To: swiftx_at_forth.com
> Subject: [swiftx] Re: separate flash space problem -- solved
>
> Hi! Frank,
>
> Mine(2.04.2A) didn't work too.
>
> Jach
>
> ----- Original Message -----
> From: "Frank Boon" <fboon_at_runbox.com>
> To: <swiftx_at_forth.com>
> Sent: Monday, August 07, 2006 5:48 PM
> Subject: [swiftx] Re: separate flash space problem -- solved
>
>
> > Can somebody check whether the SPM instruction works on the AVR
> > platform? (It doesn't work on my Swiftx 3.2.4 AVR)
> >
> > CODE SPM RET END-CODE
> >
> > And why should the instruction be not supported?
> >
> > Best regards,
> > Frank Boon
> > Metatronics
> >
> > Jach Fong schreef:
> > > Hi!
> > >
> > > I usually use another way to put the codes into the
> upper 64KB area
> of
> > > ATMega128.(need new compiler
> > > words to support their execution, but it is not concerned in this
> problem).
> > > The codes can be correctly saved
> > > into TARGET.HEX. My SWiftX version is 2.04.2A. Not sure
> if it will work
> on
> > > other versions.
> > >
> > > $12000 EQU TopCode
> > > ....
> > > THERE ( --adr) TopCode OVER - GAP
> > > : boot 12 . ; \ put the codes into the upper 64KB
> > > THERE EQU TopCode \ save it for next time usage
> > > ( --adr) THERE - GAP \ restore the pointer in lower 64KB
> > >
> > > Best Regards,
> > >
> > > Jach Fong
> > >
> > > At 01:55 AM 2006/8/4, you wrote:
> > >
> > >> This is another example of somebody who should read the
> manual better
> > >> !!! :-[
> > >> if
> > >>
> > >> [BUILD.F]
> > >> [...]
> > >> FLASH SAVE-CODE TARGET.HEX
> > >> FLASHBOOT APPEND-CODE
> > >> [...]
> > >>
> > >> then
> > >>
> > >> [TARGET.HEX]
> > >> [...]
> > >> :1017D000C7DF0895F894F2E0E2E4B0E0A8EAD2E0CE
> > >> :1017E000C6E9F3E0E9E3EDBFFEBF7894D8CFFFFF91
> > >> :103800000E9428000C000E94C9050895FFFFFFFFD9
> > >> :00000001FF
> > >>
> > >> Frank Boon wrote:
> > >>
> > >>
> > >>> guess what happens is I change BUILD.F
> > >>>
> > >>> [BUILD.F]
> > >>> [...]
> > >>> SAVE-CODE TARGET.HEX
> > >>> [...]
> > >>>
> > >>> to
> > >>>
> > >>> [BUILD.F]
> > >>> [...]
> > >>> FLASHBOOT SAVE-CODE TARGET.HEX
> > >>> [...]
> > >>>
> > >>> then
> > >>>
> > >>> [TARGET.HEX]
> > >>> :103800000E9428000C000E94C9050895FFFFFFFFD9
> > >>> :00000001FF
> > >>>
> > >>> But both sections in one file? I think it's not
> possible as I can't
> look
> > >>> into/change the compiler.
> > >>>
> > >>> Any comments? I will make a work-around, but it's not pretty!
> > >>>
> > >>> best regards,
> > >>> Frank Boon
> > >>>
> > >>> Frank Boon wrote:
> > >>>
> > >>>
> > >>>
> > >>>> I use SWIFTX to program the flash. I think the compiler is the
> culprit
> > >>>> here..
> > >>>>
> > >>>> I looked at the TARGET.HEX file, and the section
> doesn't show up in
> the
> > >>>> HEX-file.
> > >>>>
> > >>>>
> > >>>> [TARGET.HEX]
> > >>>> :100000000C94EA0B18950000189500001895000054
> > >>>> :1000100018950000189500000C9497091895000099
> > >>>> :100020001895000018950000189500000C94210800
> > >>>> :10003000189500001895000018950000189500000C
> > >>>> :1000400018950000189500001895000018950000FC
> > >>>> :10005000BA93AA93FF91EF913196EF93FF93319763
> > >>>> :10006000EE0FFF1FC895A02D3196C895B02D0895AD
> > >>>> [...]
> > >>>> :1016E000AA930E94280008000E9491010E94B7005E
> > >>>> :1016F0000E942800FF000E94540108950E94A80241
> > >>>> :101700000E942800080051DA0E94990208950E9460
> > >>>> :10171000A8020E942800100048DA0E949902089549
> > >>>> :10172000AC91BB27EBDF08950D90BC91A02DEFDFAE
> > >>>> :1017300008950E9428000C002CDA0895B0D90954AD
> > >>>> :10174000455354424F415244E4D808950C9105BB8F
> > >>>> :10175000A991B99108950C9102BBA991B9910895ED
> > >>>> :101760007ADFA5DD08950C043A03003A0300000077
> > >>>> :1017700000960200000A00D001D001DD5EFFBA939E
> > >>>> :10178000AA93F7E1E6E6B0E0A0E690E085E1C8952F
> > >>>> :1017900031960D920197D9F7A991B99108950E94B8
> > >>>> :1017A00028003A030E944A020E941F02E8DF0CDF71
> > >>>> :1017B00012960E945702BA93AA930E9428003600FC
> > >>>> :1017C0003BD80E94280011000E946103C2DD9CDD0D
> > >>>> :1017D000C7DF0895F894F2E0E2E4B0E0A8EAD2E0CE
> > >>>> :1017E000C6E9F3E0E9E3EDBFFEBF7894D8CFFFFF91
> > >>>> :00000001FF
> > >>>>
> > >>>> Leon Wagner wrote:
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>> Looks like you're not burning both CDATA sections into flash.
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>> -----Original Message-----
> > >>>>>> From: swiftx-bounce_at_forth.com
> > >>>>>> [mailto:swiftx-bounce_at_forth.com] On Behalf Of Frank Boon
> > >>>>>> Sent: Thursday, August 03, 2006 7:36 AM
> > >>>>>> To: swiftx_at_forth.com
> > >>>>>> Subject: [swiftx] separate flash space problem
> > >>>>>>
> > >>>>>> Can anybody see what I'm doing wrong?
> > >>>>>>
> > >>>>>> Platform: ATMEL MEGA16.
> > >>>>>>
> > >>>>>> What: I'm trying to setup a bootloader, which must reside in
> > >>>>>> a particular space in de flash (last 2k).
> > >>>>>>
> > >>>>>> Problem: A simple word isn't compiled in the
> separate flash space.
> > >>>>>>
> > >>>>>> Thanks in advance,
> > >>>>>> Frank Boon
> > >>>>>> Metatronics
> > >>>>>>
> > >>>>>>
> > >>>>>> [config.f]
> > >>>>>> [...]
> > >>>>>> 3800 3FFF CDATA SECTION FLASHBOOT \ Flash code space
> > >>>>>> BOOTLOADER 2K
> > >>>>>> (byte addressed)
> > >>>>>> 0000 37FF CDATA SECTION FLASH \ Flash code space
> > >>>>>> (byte addressed)
> > >>>>>> FLASH
> > >>>>>> 0060 01CF IDATA SECTION IRAM \ Internal
> initialized data
> > >>>>>> 01D0 045F UDATA SECTION URAM \ Internal
> uninitialized
> data
> > >>>>>> [...]
> > >>>>>>
> > >>>>>> [app.f]
> > >>>>>> [...]
> > >>>>>> FLASHBOOT
> > >>>>>> : boot 12 . ;
> > >>>>>> FLASH
> > >>>>>> : noboot 12 . ;
> > >>>>>> [...]
> > >>>>>>
> > >>>>>>
> > >>>>>> [command window output]
> > >>>>>> [...]
> > >>>>>> INCLUDE BUILD
> > >>>>>> Start End Size Used Unused Type Name
> > >>>>>> 0000 37FF 14336 6126 8210 CDATA FLASH
> > >>>>>> 3800 3FFF 2048 12 2036 CDATA FLASHBOOT
> > >>>>>> 0060 01CF 368 21 347 IDATA IRAM
> > >>>>>> 01D0 045F 656 429 227 UDATA URAM ok
> > >>>>>> [...]
> > >>>>>> CONNECT TARGET ok
> > >>>>>> [...]
> > >>>>>> boot
> > >>>>>> TARGET READY ok
> > >>>>>> [...]
> > >>>>>> noboot 12 ok
> > >>>>>> [...]
> > >>>>>> See noboot
> > >>>>>> 1732 |TIB| CALL 0E942800
> > >>>>>> 1736 LITERAL C 0C00
> > >>>>>> 1738 . RCALL 2CDA
> > >>>>>> 173A RET 0895 ok
> > >>>>>> [...]
> > >>>>>> See boot
> > >>>>>> 3800 7 R31 SBRS FFFF
> > >>>>>> 3802 7 R31 SBRS FFFF
> > >>>>>> 3804 7 R31 SBRS FFFF
> > >>>>>> 3806 7 R31 SBRS FFFF
> > >>>>>> 3808 7 R31 SBRS FFFF
> > >>>>>> 380A 7 R31 SBRS FFFF
> > >>>>>> 380C 7 R31 SBRS FFFF
> > >>>>>> 380E 7 R31 SBRS FFFF
> > >>>>>> 3810 7 R31 SBRS FFFF
> > >>>>>> 3812 7 R31 SBRS FFFF
> > >>>>>> 3814 7 R31 SBRS FFFF
> > >>>>>> 3816 ETC...
> > >>>>>> [...]
> >
> >>>>>>
> ---------------------------------------------------------------------
> -
> > >>>>>> swiftx_at_forth.com The SwiftX programming
> discussion email
> list
> > >>>>>> To unsubscribe, send subject "unsubscribe" to
> > >>>>>> swiftx-request_at_forth.com For list command help, send subject
> > >>>>>> "help" to swiftx-request_at_forth.com Message archives are
> > >>>>>> located at http://www.forth.com/archive/swiftx
> >
> >>>>>>
> ---------------------------------------------------------------------
> -
> > >>>>>> This list is a forum for SwiftX users. For product support
> > >>>>>> and bug reports, please send email to support_at_forth.com
> >
> >>>>>>
> ---------------------------------------------------------------------
> -
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> >
> >>>>>
> ----------------------------------------------------------------------
> > >>>>> swiftx_at_forth.com The SwiftX programming
> discussion email
> list
> > >>>>> To unsubscribe, send subject "unsubscribe" to
> swiftx-request_at_forth.com
> > >>>>> For list command help, send subject "help" to
> swiftx-request_at_forth.com
> > >>>>> Message archives are located at
> http://www.forth.com/archive/swiftx
> >
> >>>>>
> ----------------------------------------------------------------------
> > >>>>> This list is a forum for SwiftX users. For product
> support and bug
> > >>>>> reports, please send email to support_at_forth.com
> >
> >>>>>
> ----------------------------------------------------------------------
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>
> > >>
> ----------------------------------------------------------------------
> > >> swiftx_at_forth.com The SwiftX programming
> discussion email list
> > >> To unsubscribe, send subject "unsubscribe" to
> swiftx-request_at_forth.com
> > >> For list command help, send subject "help" to
> swiftx-request_at_forth.com
> > >> Message archives are located at
> http://www.forth.com/archive/swiftx
> > >>
> ----------------------------------------------------------------------
> > >> This list is a forum for SwiftX users. For product
> support and bug
> > >> reports, please send email to support_at_forth.com
> > >>
> ----------------------------------------------------------------------
> > >>
> > >
> > >
> > >
> ----------------------------------------------------------------------
> > > swiftx_at_forth.com The SwiftX programming
> discussion email list
> > > To unsubscribe, send subject "unsubscribe" to
> swiftx-request_at_forth.com
> > > For list command help, send subject "help" to
> swiftx-request_at_forth.com
> > > Message archives are located at
> http://www.forth.com/archive/swiftx
> > >
> ----------------------------------------------------------------------
> > > This list is a forum for SwiftX users. For product
> support and bug
> > > reports, please send email to support_at_forth.com
> > >
> ----------------------------------------------------------------------
> > >
> > >
> > >
> >
> >
> ----------------------------------------------------------------------
> > swiftx_at_forth.com The SwiftX programming discussion
> email list
> > To unsubscribe, send subject "unsubscribe" to
> swiftx-request_at_forth.com
> > For list command help, send subject "help" to
> swiftx-request_at_forth.com
> > Message archives are located at http://www.forth.com/archive/swiftx
> >
> ----------------------------------------------------------------------
> > This list is a forum for SwiftX users. For product support and bug
> > reports, please send email to support_at_forth.com
> >
> ----------------------------------------------------------------------
> >
>
>
> ----------------------------------------------------------------------
> swiftx_at_forth.com The SwiftX programming discussion email list
> To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
> For list command help, send subject "help" to swiftx-request_at_forth.com
> Message archives are located at http://www.forth.com/archive/swiftx
> ----------------------------------------------------------------------
> This list is a forum for SwiftX users. For product support and bug
> reports, please send email to support_at_forth.com
> ----------------------------------------------------------------------
>
>

----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Mon Aug 07 2006 - 20:11:44 PDT