[SOLVED]Porting core micropython: architecture-specific functions

C programming, build, interpreter/VM.
Target audience: MicroPython Developers.
Post Reply
Posts: 628
Joined: Thu Sep 07, 2017 8:57 pm

[SOLVED]Porting core micropython: architecture-specific functions

Post by jickster » Mon May 21, 2018 6:44 pm

This isn't about all the peripherals, just the portions of the code to run core micropython.

What functions are unique to a given architecture (x86, ARM, TI-DSP)?

1. nlr-related assembly code
2. mp_uint_t gc_helper_get_regs_and_sp(mp_uint_t *regs)

Anything else?
Last edited by jickster on Tue May 22, 2018 2:15 pm, edited 1 time in total.

User avatar
Posts: 3152
Joined: Mon Jan 06, 2014 6:08 pm
Location: Peachland, BC, Canada

Re: Porting core micropython: architecture-specific functions

Post by dhylands » Mon May 21, 2018 6:56 pm

I think that the nlr code (which I'm pretty sure can be done using setjmp/longjmp), the gchelper function, and the startup/ISR code are the primary non-peripheral things.

Supporting the native and viper code generators also requires architecture specific code, but this functionality isn't required to get MicroPython up and running.

Post Reply