I want to find the things I need like the eeprom, close to the place I·am, so that I will get it in less than a week and won't have to pay more for shipping than the products worth.
I know that I can use an EEPROM to extended the memory on my BS2sx, but what about flash memory ? Could I use flash memory instead of an EEPROM ? Is it more convenient since everything loads and erases at the same time, instead of in slots ?
Also, which type of flash memory is the best to you, NAND or NOR ?
I wouldn't characterize it as "extending" the memory on your BS-2SX since the memory boundaries are not coincident. On the other hand, you can certainly add additonal, external memory to be accessed by your BS-2SX.
I just didn't what you or anyone else to think you could write larger programs by "extending" the memory on the BS-2SX, or that you be able to have more internal variable space. As external memory, it can only contain data.
Well you could use it to save a lot of small programs and load them as needed, thereby effectively "extending" virtual the program space...
It's what I'm experimenting with right now.
Rafael
With a compiled or assembled language, what you're attempting to do is quite trivial, as you probably know. All you essentially need to do is make the program segments self-relocating, write your own loader/linker, maintain the necessary system data areas properly, and 95% of the job is done. This is not true however for an interpreted language, such as that used on the PBASIC Stamp.
The other problem I see, right up front, is that you have no direct access to the CPU, the instruction address register, the actual program stack, the register save areas, nor to the internal clock. Essentially you're "flying blind" and I'm not sure that's a very effective method of managing a "virtual program space". The last thing missing is PEEK/POKE which would be an alternative method of re-gaining the missing access.
I'm not sure I see a practical need for additional program banks over the 8 presently available on the more advanced Stamps. None the less, good luck with your efforts, and let us know how you progress.
Regards,
Bruce Bates
Post Edited (Bruce Bates) : 10/28/2005 4:03:57 AM GMT
I have a BS2p and what I do is I compile a program into stamp memory, go to another slot, read the program I just compiled as the ASCII tokens and write them to EEPROM. When I want the program, I read the EEPROm and write to a free slot.
That is what I'm thinkin of in theory, haven't done it yet (probably not till thanksgiving break) due to schoolwork overload.
Rafael
Actually I was just interested in that. I do not need more than the eight slots (and probably never likely). However, I will test my idea to see if it mill work for the future.
Rafael
flyingfishfinger said...(trimmed)
I have a BS2p and what I do is I compile a program into stamp memory, go to another slot, read the program I just compiled as the ASCII tokens and write them to EEPROM. When I want the program, I read the EEPROm and write to a free slot.
Why not just run the program from the slot it's loaded into instead of copying into another one to do the same thing?· That what the extra banks are there for.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Chris Savage Parallax Tech Support csavage@parallax.com
~4,000 instructions per slot, depending on the instructions.· The
slots are not contiguous (Connected together as one big block of memory) so you still have to keep it within 2K per program, then chain on to other programs/slots.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Chris Savage Parallax Tech Support csavage@parallax.com
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Jon Williams
Applications Engineer, Parallax
Also, which type of flash memory is the best to you, NAND or NOR ?
Thanks for your help !
I wouldn't characterize it as "extending" the memory on your BS-2SX since the memory boundaries are not coincident. On the other hand, you can certainly add additonal, external memory to be accessed by your BS-2SX.
I just didn't what you or anyone else to think you could write larger programs by "extending" the memory on the BS-2SX, or that you be able to have more internal variable space. As external memory, it can only contain data.
Regards,
Bruce Bates
It's what I'm experimenting with right now.
Rafael
With a compiled or assembled language, what you're attempting to do is quite trivial, as you probably know. All you essentially need to do is make the program segments self-relocating, write your own loader/linker, maintain the necessary system data areas properly, and 95% of the job is done. This is not true however for an interpreted language, such as that used on the PBASIC Stamp.
The other problem I see, right up front, is that you have no direct access to the CPU, the instruction address register, the actual program stack, the register save areas, nor to the internal clock. Essentially you're "flying blind" and I'm not sure that's a very effective method of managing a "virtual program space". The last thing missing is PEEK/POKE which would be an alternative method of re-gaining the missing access.
I'm not sure I see a practical need for additional program banks over the 8 presently available on the more advanced Stamps. None the less, good luck with your efforts, and let us know how you progress.
Regards,
Bruce Bates
Post Edited (Bruce Bates) : 10/28/2005 4:03:57 AM GMT
That is what I'm thinkin of in theory, haven't done it yet (probably not till thanksgiving break) due to schoolwork overload.
Rafael
Rafael
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Tech Support
csavage@parallax.com
slots are not contiguous (Connected together as one big block of memory) so you still have to keep it within 2K per program, then chain on to other programs/slots.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Tech Support
csavage@parallax.com
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Tech Support
csavage@parallax.com