I have a question about catalog in PB4.2

Similar Threads:

1.Bootloader placed correctly in the PB4.1 Catalog?

It needs to be a required child, which is defined by the BSP where the
DefaultDrivers are defined not the bootloader.

Children( <Bootloader GUID>)

Or make it an optional child, so that it can be removed:

OptionalChildren ( "{27000D58-4018-4D39-9E4A-E39F60299305}" )

2.UPDATING PB4.1 TO PB4.2 WITH PROBLEMS

     My system : PXA250, 32 MB RAM, 32 MB FLASH, PB4.2.

     When I was working with PB4.1, I had a lot of problems to make my
system work. I had a lot of fight with assembler code, MMU, JTAG, etc, but
after several months of work everything was working. I used a Lubbock BSP
clone, removing all the BLR, BCR, ASSABBET, etc, code.

     Now seems that the nightmare starts again. I received my copy of PB4.2,
and the first surprise is that I have to implement all my changes in a new
BSP manually. No way to make it with any wizard.

So I implemented again all my changes to a new Lubbock BSP clone. I load the
OS image in my board and launch the system, it doesn't works! Using MajicMx
hardware probe I have seen the code where the system hangs:


        mfc15   r1, c1
        orr     r1, r1, #0x007F                 ; changed to read-mod-write
for ARM920 Enable: MMU, Align, DCache, WriteBuffer
        orr     r1, r1, #0x3200                 ; vector adjust, ICache, ROM
protection
        ldr     r0, VirtualStart
        cmp     r0, #0                          ; make sure no stall on "mov
pc,r0" below
        mtc15   r1, c1                          ; enable the MMU & Caches
        mov     pc, r0                          ;  & jump to new virtual
address
        nop


  The system hangs in mtc15 instruction. I had the same problem in the very
beginning of my previous system, and it was due to bad configuration in
config.bib file. But now I can swear that OemAddressTable and config.bib are
perfect.

  I was wondering if the cause of the problem is that I have not implement
the function "OEMCacheRangeFlush". After reading the PB help, I don't know
if it's optional to implement that function. I have not implemented it, but
Building the image doesn't report any linker errors.

   So, I would like to know if the problem could be related to cache issues.
I have seen that one of the functions that are called before the "mtc15
macro" is OEMArmCacheMode. Do I have to make any change to this function?

 Any help would be appreciated.

 Best Regards.

3.ActiveSync question with repllog PB4.0

4.err " The catalog file is damaged or an invalid catalog "

Hi,

I got the err " The catalog file is damaged or an invalid catalog " whenever
I run the MS Baseline security analyser ( MBSA ).

Can anyone help?

Thanks
Jim

5.Catalog Item not appearing in Workspace Catalog Tree...

...despite no error report from Platform Builder, when I add a keyboard 
driver from my custom BSP (based on Samsung SMDK2410), nothing appears in the 
"left-hand" catalog tree. i.e. it seems as though the Catalog Item has not 
been added to the OS design. 

I don't think it's just a UI glitch, because a build made after this 
non-addition still has no keyboard support.

Has anyone seen this phenomenon before (not necessarily keyboard related)?

PS The keyboard driver is a slightly modified version of the Samsung driver.
PPS I can add some but not all of the other items from my custom BSP.

6. The catalog file is damaged or an invalid catalog

7. Question about Global Catalog

8. Global Catalog question