No, you didn't. U-boot does.fvdw wrote:I did not disable the clock interrupt
? The uImage is loaded @0x0400000 and up. So when nothing is in it's way, you have 124MiB of space.But in case the kernel is loaded ad address 0x400000 it means at byte 4194304 of the ram.
So we have max 4.2 MB of space there
uImage minus the header, which is 64 bytes.the data (how big is this ?)
The kernel overwriting itself is no problem, I think. When the tail of the copy overwrites the head of the 'original', that head has already been copied.But the data is copied to 0x8000 so effecitvely we have about 4.1 MB space for that before it overwrite itself
At this stage we have u-boot, the u-boot environment, and some u-boot stack/heap. I guess it's SPI flash, so u-boot can't run from flash.then loading it at 800000 shuld give more space...unless there is stored more in between 0 en the first 4.1 MB of the RAM
How big is the 'normal' kernel? If you add 0x08000 and round that up to a nice value (binary of course), that might be the maximal size (after subtrackting that 0x08000 again).So what size may the kernel be then to fit
? The uImage is loaded @0x0400000 and up. So when nothing is in it's way, you have 124MiB of space.But in case the kernel is loaded ad address 0x400000 it means at byte 4194304 of the ram.
So we have max 4.2 MB of space there
I thought the a part of u-boot was around 0x0800000, but it seems not to be there
...
So *if* u-boot (or it's stack) is overwritten, it is somewhere in 0x08000 + kernel size.
that has a size of 1.8 MBHow big is the 'normal' kernel?
Mijzelf wrote:You know that it's possible to put the initramfs in a separate uImage? That is generally called a uInitrd. In that case you can upload it somewhere 'in the ocean' above 16M, and put only the bare kernel at 0x08000.
Marvell>> bootm 0x400000
bootm 0x400000
## Booting image at 00400000 ...
Image Name: Linux-2.6.39.4
Created: 2013-10-24 20:50:11 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1815908 Bytes = 1.7 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
Starting kernel ...
Linux version 2.6.39.4 (root@fvdwsl-5big2.local) (gcc version 4.5.4 (GCC) ) #27
PREEMPT Thu Oct 24 21:49:48 GMT+1 2013
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: LaCie 5Big1 Network
Clearing invalid memory bank 0KB@0x00000000
Clearing invalid memory bank 0KB@0x00000000
Clearing invalid memory bank 0KB@0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Kernel command line: console=ttyS0,115200 netconsole=6666@192.168.0.252/,6666@19
2.168.0.12/
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 126388k/126388k available, 4684k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xc8800000 - 0xfd800000 ( 848 MB)
lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0063000 ( 364 kB)
.text : 0xc0063000 - 0xc034b000 (2976 kB)
.data : 0xc034c000 - 0xc035f6e0 ( 78 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptable hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
Return to Lacie 5Big Network vs1
Users browsing this forum: No registered users and 5 guests