Well, I guess it depends whether it's going to be used a lot.
If it's some part of the chip that's going to be used loads, needs to be fast, or needs deep integration with the interpreter (SPI, I2C, etc) then it'd be built-in, otherwise it could be a module.
The NVRAM falls inbetween I guess - it may not get used that much and doesn't need to be fast, and especially on the classic board we're running low on available flash so I don't want to add things unless they're absolutely required.
As it stands there's currently a bug in Espruino classic (forgetting the 'high word' of the RTC time if it's restarted) that could be fixed by using some of the NVRAM, so it may well be that I end up adding support internally.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Well, I guess it depends whether it's going to be used a lot.
If it's some part of the chip that's going to be used loads, needs to be fast, or needs deep integration with the interpreter (SPI, I2C, etc) then it'd be built-in, otherwise it could be a module.
The NVRAM falls inbetween I guess - it may not get used that much and doesn't need to be fast, and especially on the classic board we're running low on available flash so I don't want to add things unless they're absolutely required.
As it stands there's currently a bug in Espruino classic (forgetting the 'high word' of the RTC time if it's restarted) that could be fixed by using some of the NVRAM, so it may well be that I end up adding support internally.