You are reading a single comment by @ThomasChr and its replies. Click here to read the full conversation.
  • Okay, I don't fear the hard work, so heres my plan.

    1. I create a file 'board/ARDUINODUE.py' and insert all Arduino Due Data.
    2. I create a file (referenced in 1.) 'boards/pins/arduinodue.csv' and insert a few Pins. The LED, the first UART and maybe some minor more for the start.
    3. I copy my complete toolchain (without gcc of course) to '/targetlibs/samd'.
    4. I create 'targets/samd/main.c' which is a 1on1 copy from the correspondending EFM32 Port File, nothing hardware dependent in here.
    5. I create 'targets/samd/jshardware.js' (copy the file from the EFM32 Port!) and modify all of it so that it does compile on an Arduino Due.
    6. I need to change the build process so that my build commandos are jused. I'm not quite sure how to do that.
    7. I try to make Espruino with BOARD=ARDUINODUE and hope for the best.


    Is this the right way to go? The one thing which is hard work seems to be 'jshardware.js' because to me it looks that this is the hardware dependent interface. Am I correct?

    Thomas

    PS: Yes, a long way to go.. :-)
    PPS: @Gordon: How do I get the Patreon Batch in the Forums?

About

Avatar for ThomasChr @ThomasChr started