(the calc simulator software is more annoying to work with - we/I'm not sure exactly when it decides to save stuff...)

On exit. Everything is only saved when either more memory is needed (and then it will write out loaded objects), or on power down.

Loading is also delayed until needed. Some of the mysterious bits you have trouble interpreting are flags indicating status, location in memory, or similar.

That's probably the goal of this topic, as stated by DJ in the first post ?
The hpwiki could contain such information as well.

Yeah, this time, i completely with you, weird he? Sooner or later that info will be uncovered, anyway.

SpiroH -> You might ask to people who did post in the HP-Museum topic:
http://www.hpmuseum.org/cgi-sys/cgiwrap/hpmuseum/forum.cgi?read=247985#247985

I assume they are all beta testers?

Question: What kind of data is stored into RAM? When a program is executed, for example, is it copied to a certain RAM area, forcing a size per program limit? Are programs always stored in RAM then backed up in Flash when the calc is turned OFF (to prevent them from being lost on a reset)? How large are each GROB memory areas?

It is actually quite interesting/different to see people who have never experienced "HP" calculators discovering the programming philosophy differences. There have never been arbitrary limits or things put in place to try and restrict what you can do in HP graphers. In fact, in quite a few ways the new programming in Prime is much more restrictive then anything found on HP graphers to date. Basically, none of these questions are things I've even thought about or seen posted in HP centered forums. I guess I'll have to adjust my thinking some.

RAM only contains things as/when they are loaded. Program execution can be done from anywhere provided there is enough memory to run. No limits I am aware of. In fact, I honestly have no idea how large of a program you'd have to create before any sort of issues would start happening. If you run out of memory (say, by creating an 11MB lists and trying to multiply it by itself), the calculator will reboot. There is no clean low memory cleanup yet unfortunately. Not really a real problem, but bothers me from a technical perspective.

The 10 predefined grob variables are just pointers. No limit on size. Also, any variables in a program can be any type. You are not restricted to the base 10. The only unique one is G0 which is basically just the main screen pointer.

There might be some size limits leftover from the 39gII that we forgot to remove (for example, on the 39gII lists were limited to 999 or 10000 chars per note or something), but they are not intentional.

Programs consist of 3 parts. You have a header area that contains information about exported variables/programs (so the system knows how to recognize them, and number of arguments for example), a compiled bytecode area, and the source. On poweroff, the source is saved to flash if it has been modified. The bytecode is discarded. Early in the development it was kept across power cycles, but there is basically no reason to do so since the parsing/compiling is so fast you could never notice a difference as an end user.

I was just looking at the pcb and I saw some interesting labels:
SDA, SCK : A serial bus for hooking up the little orange pcb up to the main board. The connector has 6 pins, so I think it's SPI, but it could be I2C too.
UART RX, UART TX : Serial port. Not sure what that is used for in the calculator.
BUZZ100 : Can you hook up a speaker/buzzer?

That little orange pcb had a chip on it that says Novate(and then I cannot read the rest.) I think it is the touchscreen controller.
I googled a few options including Novatel which specializes in embedded wireless modules. Could anyone confirm what the text on the chip says?

@Keoni29: Do you already know HP Prime (DVT Prototype) Hardware Details ?