[Ovmsdev] V3 progress

[Mark Webb-Johnson]

Tom,

I think your problem is sdkconfig. That has settings for partition table, fat filesystem, and timer task stack size; all three of your issues.

Can you try to diff your sdkconfig against sdkconfig.default (which contains all the custom settings)? Or just copy sdkconfig.default over your sdkconfig, and then adjust appropriately for what you need custom? You’ll need to ‘make menuconfig’ to confirm things, then I suggest ‘make clean’ and ‘make flash’ to flash everything (partition table, bootloader, etc).

Regards, Mark.

P.S. The store has ‘m_store_fat.format_if_mount_failed = true’, so should format as necessary.

> On 11 Oct 2017, at 3:17 AM, Tom Parker <tom at carrott.org> wrote:
> 
> On 10/10/17 23:39, Tom Parker wrote:
>> I'll test the vfs append tomorrow too
> 
> I think there is a problem with the simcom support. The following trace at the bottom of this mail happens on startup and it reboots before doing it again in a loop. I haven't  startup tasks. I've got the hologram simcard in it but haven't registered it or anything like that, so maybe an error is being reported that isn't being handled. I turned off the simcom support in make menuconfig and it's stable.
> 
> The vfs things don't work:
> 
> OVMS > vfs mkdir /store/scripts
> Error: Could not create VFS directory
> 
> It also used to store my config across power cycles but it doesn't do that anymore.
> 
> Is this relevant:
> 
> I (1132) ovms_main: Mounting CONFIG...
> E (1132) vfs_fat_spiflash: Failed to find FATFS partition (type='data', subtype='fat', partition_label='store'). Check the partition table.
> Initialising OVMS CONFIG within STORE
> 
> I appear to be using the ./vehicle/OVMS.V3/partitions.csv partition table, does /store need formatting? I see there is autoformat code in the sdcard paths, but not in the internal storage?
> 
> Simcom reboot loop referred to above:
> 
> Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console
> I (2280) simcom: State: Enter CheckPowerOff state
> SIMCOM tx 41 54 0d 0a AT..            ***ERROR*** A stack overflow in task Tmr Svc has been detected.
> abort() was called at PC 0x400887b8 on core 0
> 0x400887b8: vApplicationStackOverflowHook at /home/ubuntu/esp/esp-idf/components/esp32/./panic.c:519
> 
> 
> Backtrace: 0x400886a0:0x3ffc7670 0x4008879f:0x3ffc7690 0x400887b8:0x3ffc76b0 0x400864e9:0x3ffc76d0 0x40087a9c:0x3ffc76f0 0x40087a56:0xa5a5a5a5
> 0x400886a0: invoke_abort at /home/ubuntu/esp/esp-idf/components/esp32/./panic.c:519
> 
> 0x4008879f: abort at /home/ubuntu/esp/esp-idf/components/esp32/./panic.c:519
> 
> 0x400887b8: vApplicationStackOverflowHook at /home/ubuntu/esp/esp-idf/components/esp32/./panic.c:519
> 
> 0x400864e9: vTaskSwitchContext at /home/ubuntu/esp/esp-idf/components/freertos/./tasks.c:4446
> 
> 0x40087a9c: _frxt_dispatch at ??:?
> 
> 0x40087a56: _frxt_int_exit at ??:?
> 
> 
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev