ConnectOne and external EEPROM

[mackrackit]

361 bytes. And that was a small example...

[dhouston]

361 bytes. And that was a small example...

That's a pretty good trade-off; 361 bytes of EEPROM saving 2350 bytes of program space. I2C EEPROM is inexpensive even for 128KB. I haven't analyzed your code but suspect you could save even more by wasting some EEPROM - using fixed length records and accessing them sequentially.

[mackrackit]

I thought about that but was not sure how the Connect One would like it. Being a little short on time I just did what I knew would work for the sample.

There is always room for improvement.

[dhouston]

Perhaps, store a length byte at the start of the strings?

But, as is, I think the EEPROM achieves our goal of reducing the PBP code burden. Others might have even better ideas.

[mackrackit]

Perhaps, store a length byte at the start of the strings?

It would be cool if the I2C command had "WAIT"...

[dhouston]

It would be cool if the I2C command had "WAIT"...

Maybe Darrel can give you a register or something where you can stick WAIT.

[mackrackit]

Or a nice small ASM routine to parse...