Question about the porting layer in v10

[Brad Minch]

Hi everyone,

I've been looking through the plat.c/plat.cpp files in the posix64 and the mbed platforms in the v10 branch.  I don't see an implementation of the plat_memGetByte() function implemented in either one of them.  Is this function no longer required in the v10 branch or is it just not needed in either of these two specific platforms?

Brad Minch.

[Dean Hall]

Prior to v10, plat_memGetByte() was used to read code images that may have been in other memory spaces (EEPROM, SEEPROM, etc). All code images were required to be present at compile time.

v10 changes in a couple ways. First, it doesn't have code images. Instead it has code objects that can be used directly from Flash without being read into a struct in RAM. Second, v10 introduces marshalled data structures and a new, optional porting API: plat_loadCodeObject(). This function loads a code object from something other than RAM or Flash such as SEEPROM, FAT FS on SD, etc. This allows p14p a platform-defined method for looking up modules that were NOT available at compile time.

For more info see comments in src/vm/plat_interface.h and all of docs/src/PlatformMarshalledModules.txt

!!Dean

> --
> --
> You are subscribed to the "python-on-a-chip" (or p14p for short) Google Group.
> Site: http://groups.google.com/group/python-on-a-chip
>
> ---
> You received this message because you are subscribed to the Google Groups "python-on-a-chip" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to python-on-a-ch...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Bradley Minch]

Hi Dean,

Thanks!

Brad.