olzeke51 wrote: ↑Fri Jun 06, 2014 2:08 pm...with the LPC8xx series, they have a boot rom API that has routines for
several built in peripherals . DO the other chips have this API available?
Is there a way to CALL them ?? I2C is one I had in mind - but it requires
a buffer pointer to be passed to it (along with other variables), I figure
the INTERRUPT SUB could process the buffer contents -
a string (array) of 512 bytes could be chopped up
Bit-banging would seem to take more time , especially if this data is
being passed to other serial devices -- 'course Real World Time is a
lot slower than microcontroller time !!!!!
Just a thought -- olzeke51
Has anyone had success with making ARMbasic use of the driver code that reportedly exists in the ROM for the newer NXP devices' peripherals?
As Gary had enumerated, it could certainly serve to lighten the weight/efficiency of user ARMbasic code - i.e. offloading the serial comms stuff to the OEM driver code and on-chip peripherals vs. bit-banging is just one example use case. I almost salivate at the idea of avoiding the overhead of having to bitbang the heck out of the IO, when the resources to avoid doing so is baked into the silicon.
I'm likely to go down the path of writing ARMbasic wrappers for the onboard UART and SPI devices/drivers, having just thrown in the towel on trying to port over NXP's libs from C++ to ARMbasic (had just about got it when I ran into problems with some of the typedef structures and enumerations). I just don't want to reinvent the wheel, if someone has already written an ARMbasic wrapper for these on-chip peripherals & drivers.
Please advise. TIA.