Twizy Build, Section Overflow

Question

Twizy Build, Section Overflow

gluca opened this issue 11 years ago · 13 comments

Building twizy version with:
OVMS_CAR_NONE
OVMS_CAR_RENAULTTWIZY
OVMS_HW_V2
OVMS_LOGGINGMODULE
OVMS_INTERNALGPS
OVMS_TWIZY_CFG
OVMS_TWIZY_BATTMON

produce a link error (section VEHICLE. can not fit the section. Section VEHICLE length=0x00000043

Building with MpLab X and C18 v3.40 for os x (free version)

Answer 1 · 2014-06-03T01:27:12.000Z

Please make sure you are building in 'release' mode, not 'debug' mode. I also suggest you try without OVMS_LOGGINGMODULE defined.

Does the normal RT specific build work for you?

Answer 2 · 2014-06-03T04:55:03.000Z

Normal rt builds. It seems udata segment VEHICLE cannot handle battmon data
(191 bytes) even with overlays.
Il 03/giu/2014 03:27 "Mark Webb-Johnson" notifications@github.com ha
scritto:

Please make sure you are building in 'release' mode, not 'debug' mode. I
also suggest you try without OVMS_LOGGINGMODULE defined.

Does the normal RT specific build work for you?

—
Reply to this email directly or view it on GitHub
#132 (comment)
.

Answer 3 · 2014-06-03T04:58:08.000Z

Can you try without OVMS_LOGGINGMODULE?

Answer 4 · 2014-06-03T05:07:37.000Z

Still having such error.

Error - section 'VEHICLE' can not fit the section. Section 'VEHICLE' length=0x00000043
Errors : 1
make[2]: *** [dist/V2_RT_Production_CFG_BATTMON/production/OVMS.X.production.hex] Error 1

I have the free version of the compiler. As stated it doesn't make any optimization. Maybe the error is related to that?

Gianluca Magalotti
ITIL V3 Certified

email: gianluca@magalotti.net
Mob: +39 340 7418648
Mob: +39 3474 3474 25
Linkedin: http://www.linkedin.com/in/gianlucamagalotti/

Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:

Can you try without OVMS_LOGGINGMODULE?

—
Reply to this email directly or view it on GitHub.

Answer 5 · 2014-06-03T06:03:11.000Z

Ok,
some other info. I've tried using BATTMON and removing CFG. Now it states:
Error - section 'MD5_DATASTORE' can not fit the section. Section 'MD5_DATASTORE' length=0x00000040

Compiling RT_Ptoduction or RT_Production with OVMS_TWIZY_CFG works well.

Gianluca Magalotti

Il giorno 03/giu/2014, alle ore 06:58, Mark Webb-Johnson notifications@github.com ha scritto:

Can you try without OVMS_LOGGINGMODULE?

—
Reply to this email directly or view it on GitHub.

Answer 6 · 2014-06-03T08:38:06.000Z

Gianluca,

check if the actual acc and logging modules also
are excluded from the build (.o files context menu).

Regards,
Michael

Am 03.06.2014 08:03, schrieb Gianluca:

Ok,
some other info. I've tried using BATTMON and
removing CFG. Now it states:
Error - section 'MD5_DATASTORE' can not fit the
section. Section 'MD5_DATASTORE' length=0x00000040

Compiling RT_Ptoduction or RT_Production with
OVMS_TWIZY_CFG works well.

Gianluca Magalotti

Il giorno 03/giu/2014, alle ore 06:58, Mark
Webb-Johnson notifications@github.com ha scritto:

Can you try without OVMS_LOGGINGMODULE?

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub
#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

Answer 7 · 2014-06-03T09:03:59.000Z

Ok,
in the configuration I've excluded logging.c from build and now it works.
Now I've enabled OVMS_DIAGMODULE too and it works.

This means if battery monitor is needed no logging available, right?

Is there any way to avoid this?

Il giorno 03/giu/2014, alle ore 10:38, Michael Balzer notifications@github.com ha scritto:

Gianluca,

check if the actual acc and logging modules also
are excluded from the build (.o files context menu).

Regards,
Michael

Am 03.06.2014 08:03, schrieb Gianluca:

Ok,
some other info. I've tried using BATTMON and
removing CFG. Now it states:
Error - section 'MD5_DATASTORE' can not fit the
section. Section 'MD5_DATASTORE' length=0x00000040

Compiling RT_Ptoduction or RT_Production with
OVMS_TWIZY_CFG works well.

Gianluca Magalotti

Il giorno 03/giu/2014, alle ore 06:58, Mark
Webb-Johnson notifications@github.com ha scritto:

Can you try without OVMS_LOGGINGMODULE?

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub
#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
—
Reply to this email directly or view it on GitHub.

Answer 8 · 2014-06-03T11:51:53.000Z

The logging module is not used by the Twizy firmware.

Don't confuse logging with the server/history
record functionality, that will work without the
logging module.

The logging module provides a charge log, a more
simple version of that feature also is available
in the Twizy firmware by means of history records.

Regards,
Michael

Am 03.06.2014 11:04, schrieb Gianluca:

Ok,
in the configuration I've excluded logging.c
from build and now it works.
Now I've enabled OVMS_DIAGMODULE too and it works.

This means if battery monitor is needed no
logging available, right?

Is there any way to avoid this?

Il giorno 03/giu/2014, alle ore 10:38, Michael
Balzer notifications@github.com ha scritto:

Gianluca,

check if the actual acc and logging modules also
are excluded from the build (.o files context
menu).

Regards,
Michael

Am 03.06.2014 08:03, schrieb Gianluca:

Ok,
some other info. I've tried using BATTMON and
removing CFG. Now it states:
Error - section 'MD5_DATASTORE' can not fit the
section. Section 'MD5_DATASTORE'
length=0x00000040

Compiling RT_Ptoduction or RT_Production with
OVMS_TWIZY_CFG works well.

Gianluca Magalotti

Il giorno 03/giu/2014, alle ore 06:58, Mark
Webb-Johnson notifications@github.com ha
scritto:

Can you try without OVMS_LOGGINGMODULE?

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub

#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal

Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub
#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

Answer 9 · 2014-06-03T20:39:53.000Z

Ok. Now I've added a full featured configuration for twizy.

Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:

The logging module is not used by the Twizy firmware.

Don't confuse logging with the server/history
record functionality, that will work without the
logging module.

The logging module provides a charge log, a more
simple version of that feature also is available
in the Twizy firmware by means of history records.

Regards,
Michael

Am 03.06.2014 11:04, schrieb Gianluca:

Ok,
in the configuration I've excluded logging.c
from build and now it works.
Now I've enabled OVMS_DIAGMODULE too and it works.

This means if battery monitor is needed no
logging available, right?

Is there any way to avoid this?

Il giorno 03/giu/2014, alle ore 10:38, Michael
Balzer notifications@github.com ha scritto:

Gianluca,

check if the actual acc and logging modules also
are excluded from the build (.o files context
menu).

Regards,
Michael

Am 03.06.2014 08:03, schrieb Gianluca:

Ok,
some other info. I've tried using BATTMON and
removing CFG. Now it states:
Error - section 'MD5_DATASTORE' can not fit the
section. Section 'MD5_DATASTORE'
length=0x00000040

Compiling RT_Ptoduction or RT_Production with
OVMS_TWIZY_CFG works well.

Gianluca Magalotti

Il giorno 03/giu/2014, alle ore 06:58, Mark
Webb-Johnson notifications@github.com ha
scritto:

Can you try without OVMS_LOGGINGMODULE?

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub

#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal

Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub
#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
—
Reply to this email directly or view it on GitHub.

Answer 10 · 2014-06-03T20:48:34.000Z

I am trying to understand the logging vs. history records, but can not put this in context.
Can someone please make a brief summary of what it is and how it is used?
I looked at the code for the logging, and it seems very useful, but how is that code used in the different vehicle_*.c files? And what is the best way to access the logged data?

On Tuesday, June 3, 2014 10:40 PM, Gianluca notifications@github.com wrote:

Ok. Now I've added a full featured configuration for twizy.

Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:

The logging module is not used by the Twizy firmware.

Don't confuse logging with the server/history
record functionality, that will work without the
logging module.

The logging module provides a charge log, a more
simple version of that feature also is available
in the Twizy firmware by means of history records.

Regards,
Michael

Am 03.06.2014 11:04, schrieb Gianluca:

Ok,
in the configuration I've excluded logging.c
from build and now it works.
Now I've enabled OVMS_DIAGMODULE too and it works.

This means if battery monitor is needed no
logging available, right?

Is there any way to avoid this?

Il giorno 03/giu/2014, alle ore 10:38, Michael
Balzer notifications@github.com ha scritto:

Gianluca,

check if the actual acc and logging modules also
are excluded from the build (.o files context
menu).

Regards,
Michael

Am 03.06.2014 08:03, schrieb Gianluca:

Ok,
some other info. I've tried using BATTMON and
removing CFG. Now it states:
Error - section 'MD5_DATASTORE' can not fit the
section. Section 'MD5_DATASTORE'
length=0x00000040

Compiling RT_Ptoduction or RT_Production with
OVMS_TWIZY_CFG works well.

Gianluca Magalotti

Il giorno 03/giu/2014, alle ore 06:58, Mark
Webb-Johnson notifications@github.com ha
scritto:

Can you try without OVMS_LOGGINGMODULE?

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub

#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal

Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub
#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

Answer 11 · 2014-06-04T00:02:37.000Z

The logging subsystem is entirely separate from the vehicle code. It looks at vehicle state to determine what the car is doing (parked idle, charging, driving, etc). If the user opts-in, it will output a single summary log record to the server whenever a drive and/or charge completes.

The user can retrieve the log records either via the raw or http apis.

Regards, Mark.

On 4 Jun, 2014, at 4:48 am, bobbo3 notifications@github.com wrote:

I am trying to understand the logging vs. history records, but can not put this in context.
Can someone please make a brief summary of what it is and how it is used?
I looked at the code for the logging, and it seems very useful, but how is that code used in the different vehicle_*.c files? And what is the best way to access the logged data?

On Tuesday, June 3, 2014 10:40 PM, Gianluca notifications@github.com wrote:

Ok. Now I've added a full featured configuration for twizy.

Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:

The logging module is not used by the Twizy firmware.

Don't confuse logging with the server/history
record functionality, that will work without the
logging module.

The logging module provides a charge log, a more
simple version of that feature also is available
in the Twizy firmware by means of history records.

Regards,
Michael

Am 03.06.2014 11:04, schrieb Gianluca:

Ok,
in the configuration I've excluded logging.c
from build and now it works.
Now I've enabled OVMS_DIAGMODULE too and it works.

This means if battery monitor is needed no
logging available, right?

Is there any way to avoid this?

Il giorno 03/giu/2014, alle ore 10:38, Michael
Balzer notifications@github.com ha scritto:

Gianluca,

check if the actual acc and logging modules also
are excluded from the build (.o files context
menu).

Regards,
Michael

Am 03.06.2014 08:03, schrieb Gianluca:

Ok,
some other info. I've tried using BATTMON and
removing CFG. Now it states:
Error - section 'MD5_DATASTORE' can not fit the
section. Section 'MD5_DATASTORE'
length=0x00000040

Compiling RT_Ptoduction or RT_Production with
OVMS_TWIZY_CFG works well.

Gianluca Magalotti

Il giorno 03/giu/2014, alle ore 06:58, Mark
Webb-Johnson notifications@github.com ha
scritto:

Can you try without OVMS_LOGGINGMODULE?

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub

#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal

Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub
#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

Answer 12 · 2014-06-04T06:17:10.000Z

Thanks Mark,

How does the user opt-in? Is this a feature? If yes, what id?

On Wednesday, June 4, 2014 2:02 AM, Mark Webb-Johnson notifications@github.com wrote:

The logging subsystem is entirely separate from the vehicle code. It looks at vehicle state to determine what the car is doing (parked idle, charging, driving, etc). If the user opts-in, it will output a single summary log record to the server whenever a drive and/or charge completes.

The user can retrieve the log records either via the raw or http apis.

Regards, Mark.

On 4 Jun, 2014, at 4:48 am, bobbo3 notifications@github.com wrote:

I am trying to understand the logging vs. history records, but can not put this in context.
Can someone please make a brief summary of what it is and how it is used?
I looked at the code for the logging, and it seems very useful, but how is that code used in the different vehicle_*.c files? And what is the best way to access the logged data?

On Tuesday, June 3, 2014 10:40 PM, Gianluca notifications@github.com wrote:

Ok. Now I've added a full featured configuration for twizy.

Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:

The logging module is not used by the Twizy firmware.

Don't confuse logging with the server/history
record functionality, that will work without the
logging module.

The logging module provides a charge log, a more
simple version of that feature also is available
in the Twizy firmware by means of history records.

Regards,
Michael

Am 03.06.2014 11:04, schrieb Gianluca:

Ok,
in the configuration I've excluded logging.c
from build and now it works.
Now I've enabled OVMS_DIAGMODULE too and it works.

This means if battery monitor is needed no
logging available, right?

Is there any way to avoid this?

Il giorno 03/giu/2014, alle ore 10:38, Michael
Balzer notifications@github.com ha scritto:

Gianluca,

check if the actual acc and logging modules also
are excluded from the build (.o files context
menu).

Regards,
Michael

Am 03.06.2014 08:03, schrieb Gianluca:

Ok,
some other info. I've tried using BATTMON and
removing CFG. Now it states:
Error - section 'MD5_DATASTORE' can not fit the
section. Section 'MD5_DATASTORE'
length=0x00000040

Compiling RT_Ptoduction or RT_Production with
OVMS_TWIZY_CFG works well.

Gianluca Magalotti

Il giorno 03/giu/2014, alle ore 06:58, Mark
Webb-Johnson notifications@github.com ha
scritto:

Can you try without OVMS_LOGGINGMODULE?

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub

#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal

Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub
#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

Answer 13 · 2014-06-04T06:20:57.000Z

In ovms.h:

#define FEATURE_OPTIN 0x0D // Features to opt-in to

#define FEATURE_OI_SPEEDO 0x01 // Set to 1 to enable digital speedo
#define FEATURE_OI_LOGDRIVES 0x02 // Set to 1 to enable logging of drives
#define FEATURE_OI_LOGCHARGE 0x04 // Set to 1 to enable logging of charges

So, setting feature 13 to 6 should log both drives and charges.

Regards, Mark.

On 4 Jun, 2014, at 2:17 pm, bobbo3 notifications@github.com wrote:

Thanks Mark,

How does the user opt-in? Is this a feature? If yes, what id?

On Wednesday, June 4, 2014 2:02 AM, Mark Webb-Johnson notifications@github.com wrote:

The logging subsystem is entirely separate from the vehicle code. It looks at vehicle state to determine what the car is doing (parked idle, charging, driving, etc). If the user opts-in, it will output a single summary log record to the server whenever a drive and/or charge completes.

The user can retrieve the log records either via the raw or http apis.

Regards, Mark.

On 4 Jun, 2014, at 4:48 am, bobbo3 notifications@github.com wrote:

I am trying to understand the logging vs. history records, but can not put this in context.
Can someone please make a brief summary of what it is and how it is used?
I looked at the code for the logging, and it seems very useful, but how is that code used in the different vehicle_*.c files? And what is the best way to access the logged data?

On Tuesday, June 3, 2014 10:40 PM, Gianluca notifications@github.com wrote:

Ok. Now I've added a full featured configuration for twizy.

Il giorno 03/giu/2014, alle ore 13:51, Michael Balzer notifications@github.com ha scritto:

The logging module is not used by the Twizy firmware.

Don't confuse logging with the server/history
record functionality, that will work without the
logging module.

The logging module provides a charge log, a more
simple version of that feature also is available
in the Twizy firmware by means of history records.

Regards,
Michael

Am 03.06.2014 11:04, schrieb Gianluca:

Ok,
in the configuration I've excluded logging.c
from build and now it works.
Now I've enabled OVMS_DIAGMODULE too and it works.

This means if battery monitor is needed no
logging available, right?

Is there any way to avoid this?

Il giorno 03/giu/2014, alle ore 10:38, Michael
Balzer notifications@github.com ha scritto:

Gianluca,

check if the actual acc and logging modules also
are excluded from the build (.o files context
menu).

Regards,
Michael

Am 03.06.2014 08:03, schrieb Gianluca:

Ok,
some other info. I've tried using BATTMON and
removing CFG. Now it states:
Error - section 'MD5_DATASTORE' can not fit the
section. Section 'MD5_DATASTORE'
length=0x00000040

Compiling RT_Ptoduction or RT_Production with
OVMS_TWIZY_CFG works well.

Gianluca Magalotti

Il giorno 03/giu/2014, alle ore 06:58, Mark
Webb-Johnson notifications@github.com ha
scritto:

Can you try without OVMS_LOGGINGMODULE?

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub

#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal

Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

Reply to this email directly or view it on
GitHub.

Reply to this email directly or view it on
GitHub
#132 (comment).

Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.