Sync 3 Technical Discussion
11-15-2017, 12:52 PM
#21
So, for MY16 W/O NAV it looks like:
-TBB is still the NAV check
-AHH contains the base image & normalizes between '16, '17, and '18 vehicles/APIMs
>included in the img.tar.gz tarball are all of the HB5T-14G386-A*.img files I'd been looking for
-SC deletes old stuff (gracenotes, &c.)
-BB nothing more than the voice_new recognition software (1.5 GB)
-AAB it appears undoes the normalizing that was done in -AHH
-BA nothing more than the gracenotes_new image
-AJ is all of the apps and some finishing bits
-AA generates the .xml file that is sent back to Ford.
So, If I'm trying to piecemeal this thing together to install... It looks like part 1 (base image) should have -TBB, -AHH, -AAB, -AA and Part 2 (everything else) should be -TBB, -SC, -BB, -BA, -AJ, -AA
-TBB is still the NAV check
-AHH contains the base image & normalizes between '16, '17, and '18 vehicles/APIMs
>included in the img.tar.gz tarball are all of the HB5T-14G386-A*.img files I'd been looking for
-SC deletes old stuff (gracenotes, &c.)
-BB nothing more than the voice_new recognition software (1.5 GB)
-AAB it appears undoes the normalizing that was done in -AHH
-BA nothing more than the gracenotes_new image
-AJ is all of the apps and some finishing bits
-AA generates the .xml file that is sent back to Ford.
So, If I'm trying to piecemeal this thing together to install... It looks like part 1 (base image) should have -TBB, -AHH, -AAB, -AA and Part 2 (everything else) should be -TBB, -SC, -BB, -BA, -AJ, -AA
The following users liked this post:
Acool (11-15-2017)
11-15-2017, 12:54 PM
#22
Same thing happened to me; I had to create a special `autoinstall.lst` install file for GN. Here you go:
Code:
; SYNC3 Consumer Assembly Upgrade - Release 2.3.10 - Only for MY 16 NonNav/NonEU assemblies. ; GN DB installation [SYNCGen3.0_2.3.17109_PRODUCT] ; system prep Item1 = HB5T-14G386-TBB Open1 = SyncMyRide\HB5T-14G386-TBB.tar.gz ; remove Gracenotes DB to make room Item2 = GB5T-14G386-SC Open2 = SyncMyRide\GB5T-14G386-SC.tar.gz Options = AutoInstall ; 2nd half [SYNCGen3.0_ALL] ; gracenotes DB installation Item1 = JL7T-14G423-BA Open1 = SyncMyRide\JL7T-14G423-BA.tar.gz Options = AutoInstall,Delay,Include,Transaction
11-15-2017, 01:17 PM
#23
11-15-2017, 01:19 PM
#24
Just a thought: Could it be a RAM error instead of storage error? These modules have I believe 2GB DDR3 SDRAM inside. I don't recall if a Master reset wipes out everything non-stock that would be loaded into RAM upon restart?
Have you tried an actual Power Cycle (disconnect battery)? While the module goes to sleep after shutting down, the CPU is still powered. It may need to be actually power cycled to lose whatever it's holding in RAM.
Any steps you can take to reduce any RAM usage (i.e., true power cycle by removing battery, remove apps, turn off wifi, master reset, don't touch anything upon master reset other than to say no to auto updates - then insert USB)?
Have you tried an actual Power Cycle (disconnect battery)? While the module goes to sleep after shutting down, the CPU is still powered. It may need to be actually power cycled to lose whatever it's holding in RAM.
Any steps you can take to reduce any RAM usage (i.e., true power cycle by removing battery, remove apps, turn off wifi, master reset, don't touch anything upon master reset other than to say no to auto updates - then insert USB)?
11-15-2017, 01:25 PM
#25
Just a thought: Could it be a RAM error instead of storage error? These modules have I believe 2GB DDR3 SDRAM inside. I don't recall if a Master reset wipes out everything non-stock that would be loaded into RAM upon restart?
Have you tried an actual Power Cycle (disconnect battery)? While the module goes to sleep after shutting down, the CPU is still powered. It may need to be actually power cycled to lose whatever it's holding in RAM.
Any steps you can take to reduce any RAM usage (i.e., true power cycle by removing battery, remove apps, turn off wifi, master reset, don't touch anything upon master reset other than to say no to auto updates - then insert USB)?
Have you tried an actual Power Cycle (disconnect battery)? While the module goes to sleep after shutting down, the CPU is still powered. It may need to be actually power cycled to lose whatever it's holding in RAM.
Any steps you can take to reduce any RAM usage (i.e., true power cycle by removing battery, remove apps, turn off wifi, master reset, don't touch anything upon master reset other than to say no to auto updates - then insert USB)?
11-15-2017, 01:27 PM
#26
Just a thought: Could it be a RAM error instead of storage error? These modules have I believe 2GB DDR3 SDRAM inside. I don't recall if a Master reset wipes out everything non-stock that would be loaded into RAM upon restart?
Have you tried an actual Power Cycle (disconnect battery)? While the module goes to sleep after shutting down, the CPU is still powered. It may need to be actually power cycled to lose whatever it's holding in RAM.
Any steps you can take to reduce any RAM usage (i.e., true power cycle by removing battery, remove apps, turn off wifi, master reset, don't touch anything upon master reset other than to say no to auto updates - then insert USB)?
Have you tried an actual Power Cycle (disconnect battery)? While the module goes to sleep after shutting down, the CPU is still powered. It may need to be actually power cycled to lose whatever it's holding in RAM.
Any steps you can take to reduce any RAM usage (i.e., true power cycle by removing battery, remove apps, turn off wifi, master reset, don't touch anything upon master reset other than to say no to auto updates - then insert USB)?
I know power was disconnected two weeks ago when they were servicing my valve cover gasket.
11-15-2017, 03:35 PM
#27
As an aside, the module stores the main file system on two partitions. For the module I updated from 1.0 to 2.3, it has 1.0 on one partition, and 2.3 on the other. This doesn't include mountable images (like GN) which are stored on a third partition and likely overwritten during upgrade since their existence isn't vital. Install cache is stored along with GN and Voice on the third partition, so I'm guessing if the MEM error is due to disk space and not RAM, then perhaps the install cache is not being cleared. In the install scripts, are there any references to ivsu_cache or ivsu_installcache ?
11-15-2017, 03:50 PM
#28
As an aside, the module stores the main file system on two partitions. For the module I updated from 1.0 to 2.3, it has 1.0 on one partition, and 2.3 on the other. This doesn't include mountable images (like GN) which are stored on a third partition and likely overwritten during upgrade since their existence isn't vital. Install cache is stored along with GN and Voice on the third partition, so I'm guessing if the MEM error is due to disk space and not RAM, then perhaps the install cache is not being cleared. In the install scripts, are there any references to ivsu_cache or ivsu_installcache ?
i’ll take a look at the various script and see if there’s any references to those cache items
11-15-2017, 03:54 PM
#29
Code:
$ grep cache `find . -name *.sh` ./GB5T-14G386-AA/post_script.sh: diff -q $f /fs/images/ivsu_cache/Interrogator_Log.xml > /dev/null ./GB5T-14G386-AA/post_script.sh: rm /fs/images/ivsu_cache/*Interrogator_Log.xml ./GB5T-14G386-AA/post_script.sh: if [ ! -e /fs/images/ivsu_cache/Decoded_ODL.xml ]; then ./GB5T-14G386-AA/post_script.sh: cp /tmp/Decoded_ODL.xml /fs/images/ivsu_cache ./JL1T-14G381-AJ/post_script.sh:SRC_LOCATION=/fs/images/ivsu_installcache/.extract_apps ./JL1T-14G381-AJ/post_script.sh:SRC1_LOCATION=/fs/images/ivsu_cache/.extract_apps
11-15-2017, 04:05 PM
#30
2.3 MY16 non-nav pristine install attempt after clearing everything and leaving battery disco'd for 3 hours: no go. MEM_ERR03.
I want an APIM with m0ar RAMdisk dammit.
I want an APIM with m0ar RAMdisk dammit.