[Ovmsdev] SPI RAM

[Mark Webb-Johnson]

I’m doing some work on optimising RAM usage in OVMS v3.1. This is to try to make space for bluetooth, etc.

First step is fixing the (broken) SPIMEM_AGGRESSIVE option to work better. Saving is worthwhile:

Without aggressive:
Free 8-bit 113116/281672, 32-bit 8020/24276, SPIRAM 4140964/4194252

With aggressive:
Free 8-bit 137380/281640, 32-bit 8020/24276, SPIRAM 4108616/4194252

That is the first step only. We are still using far too much internal RAM, and almost the whole 4MB of external RAM is sitting idle.

The reason for this eMail: Hopefully I didn’t break anything. If I did, let me know.

Regards, Mark.

> Begin forwarded message:
> 
> From: GitHub <noreply at github.com>
> Subject: [openvehicles/Open-Vehicle-Monitoring-System-3] 2816b9: Support minimal build (all components disabled) - ...
> Date: 16 May 2018 at 10:13:49 AM HKT
> To: mark at webb-johnson.net
> Reply-To: GitHub <noreply at github.com>
> 
> Commit: 23f307757abb6411f77500182b72b11417019317
>      https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/23f307757abb6411f77500182b72b11417019317 <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/23f307757abb6411f77500182b72b11417019317>
>  Author: Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>>
>  Date:   2018-05-16 (Wed, 16 May 2018)
> 
>  Changed paths:
>    M vehicle/OVMS.V3/main/ovms.cpp
>    M vehicle/OVMS.V3/main/ovms.h
> 
>  Log Message:
>  -----------
>  Correct implementation of CONFIG_OVMS_HW_SPIMEM_AGGRESSIVE.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180516/e1ef567a/attachment.html>