Building a tinyg with custom settings

Home › Forums › TinyG › TinyG Support › Building a tinyg with custom settings

Tagged: ,

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • June 21, 2013 at 6:47 am #4209
    Edward
    Member

    Dear all,

    I’m not sure if this is the right place for posting this, so please redirect me as necessary. I really just have some general questions about building the firmware.

    I’ve been having a crack at build tinyg.hex with the shapeoko rather than default settings. I’m using the master branch (the edge branch doesn’t seem to contain the necessary project file for AtmelStudio 6.1?) and I have simply modified the settings.h file to use the settings_shapeoko375.h file from the repository. This appears to build fine, but I get a couple of odd results. If I build the release configuration the resulting file (Release/tinyg.hex) reports some key settings, such as TRAVEL_PER_REV as ‘?’ when I flash it and call $m on the board. It appears that these have not been set at all?

    However, with no other changes, I now simply build the debug configuration and flash the resulting Debug/tinyg.hex I get default values back (TRAVEL_PER_REV = 1.25), but not the shapeoko specific ones I was expecting.

    I’m sure I must be missing some additional steps required for a build here as I can also see that if I simply get down the repo and build ‘as-is’ my tinyg.hex seems to be about 20k smaller than the one archived in the repo.

    I haven’t been able to find too much on the wiki about this, but I have spent a reasonable amount of time searching, so please forgive me if I have missed something crucial and any pointers are gratefully received.

    Kind regards

    E

    • This topic was modified 11 years, 4 months ago by Edward.
    June 21, 2013 at 12:31 pm #4212
    mcgyvr
    Member

    I’m no help with the coding BUT
    This is what I might suggest.. Simply create the txt file with all the settings and use coolterm (or whatever) to load/set them all at once. See here

    Update settings on TinyG with CoolTerm

    Then you are working with the default code and just dumping all the settings for your machine at once versus having to go any set them each manually one by one which I’m sure is what you are trying to avoid.

    Then its just fire up coolterm, load the text file and done. Voila all settings set to what you want.

    June 21, 2013 at 9:33 pm #4219
    alden
    Member

    I should be able to get to putting the .cproj file up on edge over the weekend.

    Alden

    June 22, 2013 at 11:48 am #4220
    Edward
    Member

    @mcgyvr – Thanks for the link, I’ve created something similar in JSON that I send on initializing and first connecting. This does indeed resolve the practical problem, I am actually interested in understanding and building the firmware for myself though, and I thought that fixing this for my specific setup would be a good first exercise.


    @Alden     – That would be great, Riley pointed me at the Edge branch in a different thread and so I assume that this is the one to keep up with? Just for the record, is my basic premise even correct that swapping out the included headers is the correct way to build a custom firmware specifically for the shapeoko?

    Cheers

    E

    June 22, 2013 at 9:30 pm #4222
    alden
    Member

    Master is the “official” stable build. But unfortunately it’s quite a bit behind the current state; something I hope to remedy this coming week as I am not (otherwise) working.

    I’d call edge the beta build. I try to push only if I think it’s stable, but it has not been shaken down beyond what I can do myself. So edge is currently the place to go.

    Dev is a sandbox environment for development. There’s not guarantee that it even compiles, let alone runs well. Often what’s in dev is test or experiment of some sort. Best to be avoided.

    The profile header is the way to go if you want to hard-wire up a profile. The best way is to create your own profile, then add it to the list of profiles and the set of profiles in profile.h, then uncomment it and comment out the rest. A rather crude form of compile-time binding, but it works.

    June 23, 2013 at 4:54 am #4223
    Edward
    Member

    Righto, thanks for the extra information on the repo structure Alden. I’ll hang on for the project file to go into the edge branch and I fully appreciate that you have many other demands, so no worries there. I’ll have another go at building once that is in.

    You might like to know that I do already have a reasonable pen drawing demo up and running for an educational science and engineering show I’m attending on Tuesday with the local school computer club I run here in the UK. Given that the shapeoko only arrived in kit form last Monday, I am very pleased with how straightforward it has all been. The nature of this forum means you probably only ever hear the negatives, so I thought I’d redress the balance a bit! 🙂

    Cheers,

    E

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.