[uboot] mpc8360 increase flash memory

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

[uboot] mpc8360 increase flash memory

Jump to solution
1,107 Views
fguihot
Contributor I
Hi everybody

I'm a beginner in embedded linux, and I've got a problem.
I'm with a board with a MPC8360, 16Mb of flash memory, and 256Mb of DDR2.
I boot the board from flash, with uboot 1.3.0-rc2.
Everything works great, and I can erase and copy some stuff in the flash memory, with the uboot shell, and erase and cp command.
The flash memory map was from 0xFC00_0000 to 0xFCFF_FFFF, and was managed with LBC0.
the register were
LBLAWAR0 = 0x80000017 ;16Mb flash
LBLAWBAR0 = 0xfc000000 ;flash base address
OR0 = 0xff000ca1 ;address mask 0xFF
BR0 = 0xfc001001 ; address 0xFC

I decided to increase the flash size from 16Mb to 32Mb.
The new memory map is from 0xFC00_0000 to 0xFDFF_FFFF.I have made some few changes in the uboot :
LBLAWAR0 = 0x80000018 ;32Mb flash
LBLAWBAR0 = 0xfc000000 ;flash base address
OR0 = 0xfe000ca1 ;address mask 0xFE
BR0 = 0xfc001001 ; address 0xFC

It go to the shell from the uboot, but when I try to acess to the 16MLb-32Mb of the flash, the uboot hang with the message :

Bad trap at PC: ffd5c34, SR: b032, vector=300

**bleep**: 0FFD5C34 XER: 20000000 LR: 0FFD5C34 REGS: 0ffaabc8 TRAP: 0300 DAR: FD000000

MSR: 0000b032 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11

DSIR: 0ffeded8



GPR00: 0FFD5C34 0FFAACB8 00000080 00000000 00000030 00000010 FFFFFFF8 00000007

GPR08: 00000041 00000020 FFFFFFFF 00000004 00000000 E0110000 0FFFE000 13FCB000

GPR16: 00000000 00000000 00000000 0000000B 00000000 00000000 00000001 FC000002

GPR24: FD000000 0FFFDD80 FD000000 04040000 0FFAAF4C 0FFAAF4C 0FFFE4F4 0FFFE7B0

Call backtrace:

0FFD5C34 0FFD4938 0FFE2CC4 0FFDE11C 0FFE36FC 0FFE3A1C 0FFE3CA8

0FFE4D18 0FFE4EF4 0FFD7014 0FFCFEE8 0FFCE73C

Exception in kernel pc ffd5c34 signal 0

Resetting the board.


There seem to be a problem with the configuration register, but I couldn't spot it.
Does anyone have an idea ?
Tags (2)
0 Kudos
1 Solution
551 Views
fguihot
Contributor I

A colleague spotted the problem : It didn't come from the flash memory or local bus configuration, but from the MMU configuration.

The flash memory is accessed througth the MMU and cached. I didn't increase the cache size.... 

View solution in original post

0 Kudos
1 Reply
552 Views
fguihot
Contributor I

A colleague spotted the problem : It didn't come from the flash memory or local bus configuration, but from the MMU configuration.

The flash memory is accessed througth the MMU and cached. I didn't increase the cache size.... 

0 Kudos