Loader Action Log - APP

[mobytes]

I presume that APP is a linked filesystem. Can anyone confirm or deny?

--> Dumping the Loader Action Log:
--> Wed Jun 12 19:19:40 2009:3.9.0.65:LI
--> Wed Jun 12 19:15:29 2009:3.9.0.65:E
--> Wed Apr 29 18:40:47 2009:3.9.0.63:LI:SWC L APP-20341-012
--> Wed Apr 29 18:40:34 2009:3.9.0.63:HIS:SWC HIS 0
--> Wed Apr 29 18:38:06 2009:3.9.0.63:LI:SWC L SFI-18379-011
--> Wed Apr 29 18:38:05 2009:3.9.0.63:HBR
--> Wed May 29 18:35:45 2009:3.9.0.63:EAS:SWC EraseAppstore
--> Wed May 29 18:34:29 2009:3.9.0.63:E:SWC Erase
--> Wed May 29 11:54:47 2009:3.9.0.63:LI:MML L MFI-14678-020
--> Wed May 29 11:53:27 2009:3.9.0.63:E:MML Erase
--> Tue Oct 28 20:57:36 2007:3.9.0.1:LI:SWC L APP-14859-019
--> Tue Oct 28 20:57:23 2007:3.9.0.1:HIS:SWC HIS 0
--> Tue Oct 28 20:54:57 2007:3.9.0.1:LI:SWC L SFI-14562-024

-mobytes

[_free]

cfp get the logs from bb.

[mobytes]

Originally Posted by _free

cfp get the logs from bb.

_free,

I have never been able to pull a bugdisp log using CFP. If you have been successful, let me know what works for you.

-mobytes

[_free]

mobytes,

cfp -v5 -u getlog bug.log

But, only in Factory OS Mode.

Has you find the RIM Channel to get the logs?

[mobytes]

Originally Posted by _free

mobytes,

cfp -v5 -u getlog bug.log

But, only in Factory OS Mode.

That's strange. It doesn't work on my 8830 when running an MFI load in developer mode.

Has you find the RIM Channel to get the logs?

I haven't found a way yet...

However, the simulators create a session_name.bug file (for example - 8830.bug) in the simulator directory. There may also be a way to dump the bugdisp log from the engineering screens.

[_free]

mobytes,

I have a 8703e.
I do a test. in MML, Use NUKE in HideMneu. all of SWPart List lost.
I try to load VSM.
use -v5 command, i get a output txt, such as:

--> Dumping the Loader Action Log:

--> S:00010005

--> Fri Jan 23 21:58:24 2009:3.9.0.49:LI:CFP -v5 -u load file

--> S:00010005

--> Fri Jan 23 16:29:41 2009:3.9.0.49:LI:CFP -v5 -u load file

--> S:00010005

--> Fri Jan 23 16:26:33 2009:3.9.0.49:LI:CFP -v5 -u load file

--> S:00010005

--> Fri Jan 23 12:19:53 2009:3.9.0.49:LI:CFP -u load file

--> S:00010005

--> Fri Jan 23 11:27:55 2009:3.9.0.49:LI:CFP -u load file

No the full text as yours.

ps, I use CDMA Universal 3.1.4.exe to dump the memory from 0x10000000, I think some codes in the BIN, such as BOOTLOADER.

[mobytes]

Originally Posted by _free

mobytes,

No the full text as yours.

The level of detail in the LAL is determined by the application (loader, cfp, mml, brl, swc, bmt, irt, stp, lsd, etc.)

ps, I use CDMA Universal 3.1.4.exe to dump the memory from 0x10000000, I think some codes in the BIN, such as BOOTLOADER.

I suppose you could get bits and pieces of bootRom code from RAM dumps, but if you want it all, you should dump the entire flash. And then tell us how you did it.

-mobytes

[dreamolight]

Originally Posted by mobytes

The level of detail in the LAL is determined by the application (loader, cfp, mml, brl, swc, bmt, irt, stp, lsd, etc.)



-mobytes

do you have these application?

[_free]

Yeah,
9630 reset the SW Parts list., can't find the MFI files.

mobytes, will you find some command about it?