U-Boot: build with nand command

396 views
Skip to first unread message

Sergei Antonov

unread,
Aug 11, 2015, 7:33:52 PM8/11/15
to linux...@googlegroups.com
Hello!
I have a bricked device which can only boot into FEL mode.

Here are some strings identifying the device:
model=T9701
brand=iNet
name=crane_evb
See more in attached files:
bootinfo.txt
script.fex
build.prop
They all come from the device.

I have set up UART, compiled sunxi-tools, and compiled u-boot-sunxi
with iNet_3F_defconfig. This iNet_3F_defconfig seems to be the closest
to my device, my .fex and inet_3F.fex from sunxi-boards are almost
identical. So now after device reset and running "fel uboot
u-boot-sunxi-with-spl.bin" I get into an u-boot command interpreter.
So far so good. Running 'help' gives me a number of available commands
and there is no 'nand' command among them (expectedly so: it is turned
off in the configuration). I have reasons to believe that the device
was bricked because of fiddling with nand partitions. The device
originally had 9 partitions: nanda,...,nandi. So I want to enable nand
command to see the current state and fix if something is broken. I did
"make menuconfig", found this option:

CONFIG_CMD_NAND:
NAND support.
Symbol: CMD_NAND [=n]
Type : boolean
Prompt: nand
Location:
-> Command line interface
-> Device access commands

, turned it on, and got compilation errors:

CC common/main.o
CC common/board_f.o
CC common/board_r.o
CC common/cmd_version.o
CC common/cmd_nand.o
common/cmd_nand.c: In function 'set_dev':
common/cmd_nand.c:116:24: error: 'CONFIG_SYS_MAX_NAND_DEVICE'
undeclared (first use in this function)
if (dev < 0 || dev >= CONFIG_SYS_MAX_NAND_DEVICE ||
^
common/cmd_nand.c:116:24: note: each undeclared identifier is reported
only once for each function it appears in
common/cmd_nand.c: In function 'do_nand':
common/cmd_nand.c:399:19: error: 'CONFIG_SYS_MAX_NAND_DEVICE'
undeclared (first use in this function)
for (i = 0; i < CONFIG_SYS_MAX_NAND_DEVICE; i++) {
^
common/cmd_nand.c: In function 'do_nandboot':
common/cmd_nand.c:959:24: error: 'CONFIG_SYS_MAX_NAND_DEVICE'
undeclared (first use in this function)
if (idx < 0 || idx >= CONFIG_SYS_MAX_NAND_DEVICE || !nand_info[idx].name) {
^
scripts/Makefile.build:277: recipe for target 'common/cmd_nand.o' failed
make[1]: *** [common/cmd_nand.o] Error 1
Makefile:1196: recipe for target 'common' failed
make: *** [common] Error 2

I tried hardcoding CONFIG_SYS_MAX_NAND_DEVICE constant, but it still
wasn't enough to compile. I think I need more elaborate changes to the
configuration or just another configuration with more features
enabled.

Can anyone help me?
bootinfo.txt
build.prop
script.fex

Siarhei Siamashka

unread,
Aug 13, 2015, 3:56:02 AM8/13/15
to sap...@gmail.com, linux...@googlegroups.com
On Wed, 12 Aug 2015 01:33:49 +0200
Sergei Antonov <sap...@gmail.com> wrote:

> Hello!
> I have a bricked device which can only boot into FEL mode.

You can probably also boot from the SD card, unless the SD card slot
is damaged.
Based on what you say, it looks like you want to restore Android on
your tablet. This is usually done via http://linux-sunxi.org/LiveSuit
Naturally, you need the right firmware image for your tablet. Good
responsible vendors are providing such recovery images from their
websites. Maybe people from various Android forums can help better?
This mailing list is primarily dedicated to running GNU/Linux on
Allwinner hardware.

--
Best regards,
Siarhei Siamashka

Sergei Antonov

unread,
Aug 13, 2015, 8:44:23 AM8/13/15
to Siarhei Siamashka, linux...@googlegroups.com
On 13 August 2015 at 09:55, Siarhei Siamashka
<siarhei....@gmail.com> wrote:
> On Wed, 12 Aug 2015 01:33:49 +0200
> Sergei Antonov <sap...@gmail.com> wrote:
>
>> Hello!
>> I have a bricked device which can only boot into FEL mode.
>
> You can probably also boot from the SD card, unless the SD card slot
> is damaged.

Booting from SD, did not work. But I managed to restore the device
already. I did it by loading and running through FEL the original
u-boot.bin binary (luckily I had it) in a command interpreter mode,
then I ran fastboot and recovered nand partitions.

I'm still interested though: how could I have built a suitable
u-boot.bin from source? I mean with "nand" command support and
possibly some more useful commands.
This mailing list is referred to in http://linux-sunxi.org/U-Boot
Then what is the right list to ask about u-boot-sunxi?
Reply all
Reply to author
Forward
0 new messages