This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM35x_FlashAndBootUtils_1_50, ubl, u-boot and Linux Flash Blocks Help

Hello All

Can somebody please confirm if the following is correct or incorrect. I need a sanity check on this before I can continue..

First, I am using my custom designed DM355 board for this work with the linux kernel Linux-2.6.10_mvl401 this board has the 29F4G08AAC on it which is page and block size compatible with the flash on the EVM)

1.  DM35x_FlashAndBootUtils_1_50 will try and place the specified u-boot binary in the blocks 25-50 (final place depends on any bad blocks encountered)

2. ubl supplied with EVM for emulator flashing places u-boot at block 10 thus all documentation relating to EVM details updating u-boot (via u-boot) at address 0x140000

3.  Linux NAND driver configured with NAND sectioned as follows (from arch/arm/mach-davinci/board-dm355-evm.c)

       bootloader = blocks 0..14

       params = block 15

       kernel = blocks 16 .. 48 (4M reserved for kernel=32 blocks)

        filesys1 = 49 ...

        filesys2 = .....

Does this mean that if I use the DM35x_FlashAndBootUtils_1_50 serial flasher tools that u-boot will be dropped into either the kernel space or the filesys space depending on the bad blocks.

So, is it the case that for a platform to be compatible with multiple methods of installing ubl and u-boot, it is necessary to ensure linux extends the size of the bootloader section to 50 blocks (all eventualities covered) ?

Many thanks

  Garry Jackson