Undocumented SYSCFG0 register

No, this is a reserved register that is not documented. Can you describe what you are trying to accomplish? Thanks

Jeff

Jeff,

I am debugging the boot... So I am digging into the RBL by reverse-engineer it.

I am able to check that the ais file is written correctly in NAND... But I am wondering if there is any compatibility between the RBL and the NAND.

The ONFI NAND spec I have is as follows:

- Base Address: 0x62000000 (CS3)

- Bus width: 8

- ManfID: 0x2C

- devID: 0x48

- numBlocks: 4096

- pagesPerBlock: 128

- dataBytesPerPage: 4096

- spareBytesPerPage: 224

- dataBytesPerOp: 512

- spareBytesPerOp: 16

- numOpsPerPage: 8

- numColAddrBytes: 2

- numRawAddrBytes: 3

- CSOffset: 0

Is this NAND flash compatible with OMAP-L138 RBL?

Thx

KB2603

Hi KB2603,

I have referred OMAP-L138 resources in two places.

First one is SPRAB41C–September 2010Using the OMAP-L1x8 Boot Loader PDF. In that PDF, NAND Device ID is not lsited (0x48).

Similarly I ahve also referred OMAP-L138 Boot Utils package 2.30 version. In that folder device_nand.c also doesn't include this Device Id.

Thank You & Regards,

GSR

Thx for your response.

Do I need to add this device in the list?

With what I have read in the source code of the NAND writer, the device list used only if the NAND is not ONFI compliant.

The NAND I am using is ONFI compliant. the NAND writer from Boot Utils detects automatically the NAND parameters. I have debugged the NAND writer code and confirmed the NAND parameters were read correctly from the device.

Can the OMAP-L138 boot with this NAND device?

I am going to check whether the device Id is used for other purpose in the source code.

Rgds

KB

Jeff,

This register is equal to 0x32.

Does it mean?

KB

Jeff,

I have tried the LED blink example for our custom board.

In Debug ( and without GEL) I am able to run the code. I start first the boot Arm  then I can connect to the DSP side and load  and executes the DSP code with no problem.

In release, I generate the .bin as describe in bootloade document SPRAB41C.

There is something weird in the example configuration file (.cfg). It seems that dsp.out is placed with @0x00000000. Do you know why @0x00000000 is used?

dsp.out has already the right address

I flash the .bin into block1 of NAND using the NAND writer and check that it is there. But board does not boot.

After boot, I connect to the board with the debug GEL, then read the ROM status and see "Peripheral Open Failed".

Any idea what's wrong?

KB

Jeff,

After booting the LED blink example, the ARM vectors are as follow:

0xFFFF0000 EAFF7FFE

0xFFFF0004 EAFFFFFD

0xFFFF0008 EAFFFFFC

0xFFFF000C EAFFFFFB

0xFFFF0010 EAFFFFFA

0xFFFF0014 EAFFFFF9

0xFFFF0018 EAFFFFF8

0xFFFF001C EAFFFFF7

0xFFFF0020 FFFF0700

The vector has not been update after boot!

Any idea why?

KB

Jeff,

I have checked all the pins of the OMAP-L138 (clock, reset, power,...)... Power sequence follows spec. reset is release 400ms after all voltages have be set.

I can run any code with no problem in debug, but nothing is happening in release.

Maybe I am missing something.

Is there any pins that can affect the boot process other than the boot mode pins.

Thx

KB

Can you try flashing the pre-built AIS binary that comes with the LED flash example? Does that one work?

Jeff

Jeff,

I flash the binary example (OMAP-L138-DSP-LED-NAND-SPI-UART.bin) and board did not start successfully.

In debug, I read ROM status: Peripheral Open Failed.

PC=0xFFFD397C

Rgds

KB

Can you print out the entire contents of the debug GEL and post it here?

Jeff

Jeff,

Please find attached s simlpe project with an ARM application that does only while(1);

Let me know if you see anything wrong with it.

Thx2376.BootL138Test.zip

KB

I'm sorry I misspoke. I meant paste the entire output of the debug GEL file :)

Jeff