Hi people.
I had an idea of using the 1024 bytes of scratch pad memory on an X2 chip, to store character data.
I understand this data is volatile. But I required a large volume of character messages (50+, up to 12 average per message) for my current project.
And the X2 Table feature is far too small for this.
My idea was to tell the X2 to load all the character messages into the scratch pad on power up. And do so via #slot 1. Then return to #slot 0 to run the program.
I know It would seem logical to just place all the messages into #slot 1's program memory. Considering is going to use the same amount of program memory to load them into the scratch pad. But this program using heaps of Gosub's, rather than doubling up on code.
I had thought of using #slot 1 for the messages and using Flags and Branches when returning to #slot 0. But It wasn't precise enough, if an interrupt occurred at that time.
This project uses a 5 way switch. Which will be used to toggle though many menu's, with many setting selections. Hence the reason there are so many messages.
From basic explanations and scrolling, through to simple selection choices.
Does this idea seem realistic? And If so.. What would be the simplest way to load all these bytes? To save on typing over 800 @ptr / Put commands.
Thanks guys
I had an idea of using the 1024 bytes of scratch pad memory on an X2 chip, to store character data.
I understand this data is volatile. But I required a large volume of character messages (50+, up to 12 average per message) for my current project.
And the X2 Table feature is far too small for this.
My idea was to tell the X2 to load all the character messages into the scratch pad on power up. And do so via #slot 1. Then return to #slot 0 to run the program.
I know It would seem logical to just place all the messages into #slot 1's program memory. Considering is going to use the same amount of program memory to load them into the scratch pad. But this program using heaps of Gosub's, rather than doubling up on code.
I had thought of using #slot 1 for the messages and using Flags and Branches when returning to #slot 0. But It wasn't precise enough, if an interrupt occurred at that time.
This project uses a 5 way switch. Which will be used to toggle though many menu's, with many setting selections. Hence the reason there are so many messages.
From basic explanations and scrolling, through to simple selection choices.
Does this idea seem realistic? And If so.. What would be the simplest way to load all these bytes? To save on typing over 800 @ptr / Put commands.
Thanks guys
Last edited: