Okay, in the meantime I got two further efusA9X boards. Even after resetting the bootloader via the 'C' command Eboot showed that the boards have 1 GByte of flash. Nboot shows the expected 512 MBytes, see the following logging:
F&S Nand Loader VN37 built Jan 31 2019 09:46:00
efusA9X Rev. 1.30
iMX 6SoloX Extended Commercial 1000MHz Rev 1.3 running at 792MHz
RAM: 512MB (2*2GBit)
FLASH: 512MB (MICRON MT29F4G08ABADAH4)
Config jumpers: 1101_0011_1101
Board features: LAN1 WLAN
Serial number: not set
Current boot mode: Boot From Fuses
Configured boot device: NAND Flash
Booted from NAND page 0
Unfortunately it is not possible to enter the size of the last partition "SECOND" manually, Eboot assigns automatically the not used space to it. This means that I have two options:
- Kernel: 128 MByte
- FFSDISK: 1024-128 = 896 MByte
- SECOND: 0 MByte (automatically assigned by Eboot).
- Kernel: 128 MByte
- FFSDISK: 512-128 = 384 MByte
- SECOND: 512 MByte (automatically assigned by Eboot).
In both cases Eboot tries to access not existing memory to make the partitioning and to format the partitions. Which one is less worse, a) or b)?
I tried both. When doing b) the installed kernel did not start (kernel stopped at the second BE2....), after resetting the device Eboot was lost. When doing a) the kernel started, also after powering on/off. So option b) seems to destroy at least less than a).
But independent weather a) or b) is done, I always have to install Eboot after doing the partitioning with the parameters shown in a) and b). Is this normal? If I partition the flash and power the device off/on, Eboot is lost (Nboot shows the command line automatically with the hint that there is no Eboot). After flashing Eboot in Nboot via the serial interface. I can use Eboot to install the OS-image.
Is this a normal behavior or can this be caused by the problem that Eboot works with the wrong size of the flash?
Eboot: Version 1.4