My plan from here out on rex is to cap any new functions here and just fix
bugs if and when they occur.
Ken is right.. a lot of software work in rex to make it more flexible wrt
how blocks are used.
into.
I would do rex differently if starting from scratch....
Post by Kurt McCullumThanks for the clarification Ken. I didn't mean to stir the pot, I was
just curious if it was possible. 512k is plenty of storage in my case. I
asked because I use 2-4 ROMS depending on the situation, so the extra ROM
image space sits dormant. Not a deal killer for me considering I can
save to my phone when needed.
Kurt
I don't mean to speak for Steve, but I have seen the code. It isn't
really a space issue but more of a control issue. Increasing beyond 16
entries means additional space on the LDC to represent them, additional
code in the control path to manage > 16 entries, additional bits in the
image "dictionary" stored in the FLASH, etc. It would be an architecture
change.
Ken
Perhaps more space can be accomplished with some sort of compression of
backup data?
Bogdan
Kurt, 16 is the max envisioned. To change that would be a some effort.
Let me think about a solution.
..steve
That's great news Steve! Quick question. Is rex limited to 16 RAM images
or can more of the 768k be used?
Kurt
All,
I have an updated software load for REX which I will be posting shortly.
Now that it is working well again, I feel ok selling REXNEC.
I have 3 units available. Contact me if you have interest in one.
thanks,
Steve