teensy 3.2

[schallee]

Greetings,

I am trying to build for the teensy 3.2 using the arduino 1.6.11 + teensyduino 1.30 tool chain (on osx). I can successfully compile and run quozl's arm-teensy3 branch (ba48256599897973c17544d4c4c2b637945eb915) but I am having issues building MitchBradley/cforth (8d3e1e6aeae8cc500902f2c1e1210be1559f9849) for the teensy.

The default compile target compiles with warnings and produces app.o:

make_default_target.txt

Attempting to compile app.elf (which I believe to be the next step) fails as it depends on start.o which is nowhere to be found:

make_app_elf.txt

There also does not appear to be any target for app.hex to use with teensy loader. I can certainly objcpy as needed but a make target would be useful;)

Thanks!

[quozl]

Reminds me I should really merge my old branch with @MitchBradley's later work here.

[quozl]

@schallee, I think I see your problem now ... my aim was a standalone source tree with everything needed to build and flash, which is why I've an app.hex target, as well as mk20dx128.c and mk20dx256.ld. But probably @MitchBradley's aim was to have Teensy and CForth source trees side by side on a system, and have the Teensy source tree bring in app.o from the CForth source tree.

I've rebased my old branch on 8d3e1e6, tested, and pushed to; quozl/cforth-1 arm-teensy3 Next is merging @MitchBradley's Teensy work and mine to figure out if there's anything for me to propose as a pull-request. A quick look at the ccalls shows there's more functionality in @MitchBradley's Teensy work.

[MitchBradley]

James is correct; I was doing the
    top-level build in PJRC's Teensy subtree of the Arduino tree.
    
    I like what I see in quozl/cforth-1
      arm-teensy3 
  
  I'm looking forward to the pull request when James is ready.
  
  
  On 12/27/2016 3:29 AM, James Cameron wrote:
  

  @schallee,
      I think I see your problem now ... my aim was a standalone
      source tree with everything needed to build and flash, which
      is why I've an app.hex target, as well
      as mk20dx128.c and mk20dx256.ld.
      But probably @MitchBradley's
      aim was to have Teensy and CForth source trees side by side on
      a system, and have the Teensy source tree bring in app.o from
      the CForth source tree.
  I've rebased my old branch on 8d3e1e6, tested, and pushed
      to;  Next is merging @MitchBradley's
      Teensy work and mine to figure out if there's anything for me
      to propose as a pull-request. A quick look at the ccalls
      shows there's more functionality in @MitchBradley's
      Teensy work.
  —
    You are receiving this because you were mentioned.
    Reply to this email directly, view
        it on GitHub, or mute
        the thread.
  
    
      
       
      
    
    
  
  {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/MitchBradley/cforth","title":"MitchBradley/cforth","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/MitchBradley/cforth"}},"updates":{"snippets":[{"icon":"PERSON","message":"@quozl in #20: @schallee, I think I see your problem now ... my aim was a standalone source tree with everything needed to build and flash, which is why I've an `app.hex` target, as well as `mk20dx128.c` and `mk20dx256.ld`.  But probably @MitchBradley's aim was to have Teensy and CForth source trees side by side on a system, and have the Teensy source tree bring in app.o from the CForth source tree.\r\n\r\nI've rebased my old branch on 8d3e1e6, tested, and pushed to; [quozl/cforth-1 arm-teensy3](https://github.com/quozl/cforth-1/tree/arm-teensy3)  Next is merging @MitchBradley's Teensy work and mine to figure out if there's anything for me to propose as a pull-request.  A quick look at the `ccalls` shows there's more functionality in @MitchBradley's Teensy work.\r\n"}],"action":{"name":"View Issue","url":"https://github.com/MitchBradley/cforth/issues/20#issuecomment-269300416"}}}

[quozl]

Thanks.

I've rebased against the upstream platform code, https://github.com/quozl/cforth-1/commits/arm-teensy3

I've then squashed several commits and made a pull request, #21. Works for me, but I may have broken something of yours, Mitch!

[MitchBradley]

Very nice.  Merged.
    
    On 12/28/2016 4:52 AM, James Cameron wrote:
  

  Thanks.
  I've rebased against the upstream platform code,
    
    https://github.com/quozl/cforth-1/commits/arm-teensy3
  I've then squashed several commits and made a pull request,
    #21.
      Works for me, but I may have broken something of yours, Mitch!
  —
    You are receiving this because you were mentioned.
    Reply to this email directly, view
        it on GitHub, or mute
        the thread.
  
    
      
       
      
    
    
  
  {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/MitchBradley/cforth","title":"MitchBradley/cforth","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/MitchBradley/cforth"}},"updates":{"snippets":[{"icon":"PERSON","message":"@quozl in #20: Thanks.\r\n\r\nI've rebased against the upstream platform code,\r\nhttps://github.com/quozl/cforth-1/commits/arm-teensy3\r\n\r\nI've then squashed several commits and made a pull request, #21.  Works for me, but I may have broken something of yours, Mitch!\r\n"}],"action":{"name":"View Issue","url":"https://github.com/MitchBradley/cforth/issues/20#issuecomment-269460680"}}}

[schallee]

Thanks! I'll give it a try when I have a chance here.

[schallee]

Compiles and loads fine on my teensy 3.2.

BTW: Though a beginner at forth and little time for hobbies, I have a hankering to try to port to the Atmel Samd21 at some point. Adafruit has ported micro python to it so most of the boiler plate could be taken from there. I'd be curious to know your thoughts on such.

Thanks again!

[quozl]

Thanks for the test on Teensy 3.2.

Atmel SAMD21 would not be difficult. Sparkfun has some lower priced boards than the Adafruit ones. A quick porting method is to write a sketch to blink an LED, then enable verbose building in the Arduino IDE, and look at the linker map and use the GCC ARM objdump to disassemble the result. Then copy the critical code from somewhere.