BB Logging beta update: April 14, 2008

Quote:

---

Originally Posted by tunedbyGM

"Error Code $0194 ( Write , file system error 20)

---

That usually means "File system full". And that usually happens because you're trying to copy too many files or the wrong files to the [Config] section.
As some of the other replies suggested, delete ALL *.pmm files from the Config folder on your PC, then re-extract them from the zip file. That will leave you with only the files that should be there and not files from previous releases.

P.S. You only need to copy the *.pmm files to FlahScan that you expect to use. You don't have to copy them all.
i.e. if you are only intending to log LS1 98, LS1 99+, E40 and E38, then all you need to copy to FlashScan are the files:

LS1A_A.pmm (LS1 98 auto)
LS1A_M.pmm (LS1 98 manual)
LS1B_A.pmm (LS1 99+ auto)
LS1B_M.pmm (LS1 99+ manual)
E40.pmm (E40 ECM)
T42.pmm (4/5 speed TCM)
E38.pmm (E38 engine)
T43.pmm (6 speed TCM)

You can even delete unwanted entries from Options.ini to make the PID selection menu on FlashScan more compact.

Regards
Paul

Quote:

---

Originally Posted by Happy Jim

Paul,

I'm doing a catch up having missed a couple of patches.

I'm on 2.5.04 Boot (Oct 16th) (firmware 2.5.15 Mar 18th)

The readme PDS says I should...
1. Program Firmware V2.05.16(0326)
2. Program Boot Block V2.05.07(0412)
3. Program firmware V2.05.16 (0412)

I can't find the file for step 1?? I guess it's on the download you've removed.
Steps 2 & 3, should the filenames be xxx(0414).??

Can I ignore step 1 and jump to step 2 or will I toast my FS that way?

If I need the first file could you post on here (or mail me?)

Tks

Jim

---

If you're starting out at boot block V2.05.04 (and firmware 2.05.15), then you can jump straight to step 2.
Step one could have said "flash in V2.05.15 or 2.05.16". You have already got 2.05.15 so you're good to go from step 2.

The file names should end with (0414), that's a typing mistake on my part.

Regards
Paul

Quote:

---

Originally Posted by tunedbyGM

Got to looking in the HAPI folder and found several .pmm files along with the Config Folder which contains both .pmm and -.pmm files , can I just delete the Config folder and re-run the zip to replace it ?
And what are the .pmm files doing in the HAPI folder and not in the Config folder ?
I also have a EFLIve Hapi folder in the EFILive Hapi folder , does it need to be there ?

---

*.pmm files can be anywhere, there's no restriction. They are not used (yet) by the PC, only by FlashScan.
However, to keep everything neat and tidy, I recommend keeping them in the Config folder - which matches the [Config] tab page in EFILive_Explorer.
You can delete all *.pmm files from the PC and re-extract them from the zip file to make sure you have the latest/correct set of pmm files.
No, you don't need an EFILive_Hapi folder in the EFILive_Hapi folder.

See image of my setup here.

Regards
Paul

Quote:

---

Originally Posted by Blacky

If you're starting out at boot block V2.05.04 (and firmware 2.05.15), then you can jump straight to step 2.
Step one could have said "flash in V2.05.15 or 2.05.16". You have already got 2.05.15 so you're good to go from step 2.

The file names should end with (0414), that's a typing mistake on my part.

Regards
Paul

---

All working,

Many thanks

Jim

Hi Paul,

I tried some more BBL-ing this morning and while the recording works well, I still can't read any of the DMA PID's in the log file, when loading into scan tool.

Simon

Same problem here with VISTA. If you click on explorer before running HAPI it will give an infinite error. Same issue I posted in another thread.

Quote:

---

Originally Posted by swingtan

Hi Paul,

I tried some more BBL-ing this morning and while the recording works well, I still can't read any of the DMA PID's in the log file, when loading into scan tool.

Simon

---

I'll look into it.
Paul

Quote:

---

Originally Posted by Black02SS

Same problem here with VISTA. If you click on explorer before running HAPI it will give an infinite error. Same issue I posted in another thread.

---

Its most likely a Vista security issue. EFILive_Explorer (or the user logged in running EFILive_Explorer) probably does not have permission to run EFILive_Hapi.

I don't know how to fix that, I'm not a Vista expert.
You may need to go into the properties of the exe file and change the permissions to allow them to play nicely in Vista.
Or, there may just be a security setting in your Vista setup that is just a little too paranoid.

Regards
Paul

Do we need to keep all the .efw files that are acquired during all the updates ?
Just trying to trim some unused stuff from the folder .

Quote:

---

Originally Posted by tunedbyGM

Do we need to keep all the .efw files that are acquired during all the updates ?
Just trying to trim some unused stuff from the folder .

---

No, you don't need any of them once a *.efw file is programmed into FlashScan you can delete it. The only reason folks keep them is sometimes during the beta test, I will release a firmware upgrade and it will break some feature. The feature can be restored by going back to the previous *.efw file until a fix is available.

That is only possible during the beta test because I am trying to keep the version number the same and only change the temporary date extension. Because *.efw files during the beta test have the same internal date you can put an old file back into FlashScan because the version checking algorithm sees the the same version number not an earlier one.

(Except when a boot block upgrade is needed, the I have to increase the version number of the firmware file.)

Once the official BB Logging firmware is released, each firmware upgrade will be a new version number (with no date extensions). Then there is no going back to an older version.

Regards
Paul