[Ovmsdev] Build environment

[Mark Webb-Johnson]

Olav,

Probably the easiest way is to try to build the RT_Production code. That is probably the biggest we have - if it will build then at least medium optimisations are working.

Regards, Mark.

On 12 Jun, 2014, at 8:16 am, Olav A. Antonsen <olav at ansit.no> wrote:

> I'm using the mcc18 compiler from a CD that came in the package when
> ordering the OVMS from FastTech.
> 
> MPLAB C18 v3.35 Copyright 2000-2010 Microchip Technology Inc.
> 
> Looks like 3.47 is the latest version
> (http://www.microchip.com/Developmenttools/ProductDetails.aspx?PartNO=SW0060
> 11).  Do you know if v3.35 still uses medium-optimisation? Is there a way to
> detect what level of optimisation the compiler uses?
> 
> --Olav
> 
> 
> -----Opprinnelig melding-----
> Fra: ovmsdev-bounces at lists.teslaclub.hk
> [mailto:ovmsdev-bounces at lists.teslaclub.hk] På vegne av Mark Webb-Johnson
> Sendt: 12. juni 2014 01:51
> Til: OVMS Developers
> Emne: Re: [Ovmsdev] Build environment
> 
> 
> The issue with building under windows is that the C compiler Microchip gives
> for free used to do medium-optimisation under windows, with
> high-optimisation a cost option. Then, they switched (silently, without any
> fanfare) to no-optimisation for the windows compiler. Both the Linux and OSX
> compiler continue with medium-optimisation. Without optimisation, the code
> won't fit into available flash space. They sell a commercial version of the
> C18 compiler for about US$500. Almost enough to drive one to ARM... I have
> heard rumours of people typing 'microchip c18 hack' into google.
> 
> Configurations 4 and 5 are the 'full' featured production builds for Tesla
> Roadster and Renault Twizy (provided as a convenience for owners of those
> vehicles who just want a binary .hex to flash).
> 
> Regards, Mark.
> 
> On 12 Jun, 2014, at 6:55 am, Olav A. Antonsen <olav at ansit.no> wrote:
> 
>> The document
>> 
>> https://github.com/openvehicles/Open-Vehicle-Monitoring-System/blob/ma
>> ster/d
>> ocs/OVMS_Development.pdf
>> 
>> helps a lot when it comes to setting up the dev environment. I set up 
>> the environment on windows 8, but it seems like everyone else is using 
>> linux to build the firmware.
>> 
>> I was able to build the hex file (on win 8), but I haven't been able 
>> to test the file yet because I'm still waiting for my unit.
>> 
>> https://dl.dropboxusercontent.com/u/12327518/OVMS.X.production.hex
>> 
>> Is anyone else using win 8 to build the firmware?
>> 
>> 
>> On the project in MPLAB it's possible to choose between different 
>> configurations
>> 
>> 1)V1_Production
>> 2)V2_Experimental
>> 3)V2_Production
>> 4)V2_TR_Production
>> 5)V2_RT_Production
>> 
>> The development documentation tells the user to select "V2_Experimental".
>> What is the purpose of configuration 4 and 5? 
>> 
>> 
>> --Olav
>> 
>> 
>> -----Opprinnelig melding-----
>> Fra: ovmsdev-bounces at lists.teslaclub.hk
>> [mailto:ovmsdev-bounces at lists.teslaclub.hk] På vegne av Olav A. 
>> Antonsen
>> Sendt: 11. juni 2014 00:21
>> Til: 'OVMS Developers'
>> Emne: [Ovmsdev] Build environment
>> 
>> Hello
>> 
>> Does anyone know if there exists a tutorial/quick guide on how to 
>> setup the environment needed to code and build the firmware?
>> 
>> --Olav
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev