[Isl3893-devel] development boot

[Arco]

Hi list,

In the readme of the firmware is the development mode mentioned.

In development mode an additional image file is generated. This imagefile ( apfirmware.tfs ) is used by the bootstrap
functionality of the bootrom. To have this file downloaded by the bootrom in case it can not find an
valid image in flash perform the following manual steps. mv apfirmware.tfs to 3893-<MAC address>.bin where MAC address equals
the MAC address of the AP. Copy the resulting file to the /tfs directory of a machine in the same subnet as the AP.
e.g. MAC address is 00:10:91:01:02:03 use mv apfirmware.tfs 3893-001091010203.bin
cp 3893-001091010203.bin /tfs

I have tried it several times and I think I'm missing some small step.
So here are my questions:

1. did anyone succeed on using this?
2. how do I force an invalid flash?

Arco

[Roland Mieslinger]

Post by Arco
Hi list,
In the readme of the firmware is the development mode mentioned.
In development mode an additional image file is generated. This imagefile ( apfirmware.tfs ) is used by the bootstrap
functionality of the bootrom. To have this file downloaded by the bootrom in case it can not find an
valid image in flash perform the following manual steps. mv apfirmware.tfs to 3893-<MAC address>.bin where MAC address equals
the MAC address of the AP. Copy the resulting file to the /tfs directory of a machine in the same subnet as the AP.
e.g. MAC address is 00:10:91:01:02:03 use mv apfirmware.tfs 3893-001091010203.bin
cp 3893-001091010203.bin /tfs
I have tried it several times and I think I'm missing some small step.
1. did anyone succeed on using this?
2. how do I force an invalid flash?
Arco

Hi Arco,

i'm not sure but maybe the key is "used by the bootstrap functionality
of the bootrom".

cat /proc/mtd gives you:
dev: size erasesize name
mtd0: 00010000 00002000 "Bootloader"
mtd1: 00350000 00010000 "Access Point Firmware"
mtd2: 000a0000 00010000 "Flash Filesystem"

When flashing new firmware only mtd1 and mtd2 are modified, but mtd0 is
always unmodified. I'd not recommend erasing mtd0, but I think only this
will give you the above mentioned boot sequence. Don't brick your AP.

Roland

[Wojtek A.]

Post by Roland Mieslinger

Post by Arco
I have tried it several times and I think I'm missing some small step.
1. did anyone succeed on using this?
2. how do I force an invalid flash?
Arco

Hi Arco,
i'm not sure but maybe the key is "used by the bootstrap functionality
of the bootrom".
dev: size erasesize name
mtd0: 00010000 00002000 "Bootloader"
mtd1: 00350000 00010000 "Access Point Firmware"
mtd2: 000a0000 00010000 "Flash Filesystem"
When flashing new firmware only mtd1 and mtd2 are modified, but mtd0 is
always unmodified. I'd not recommend erasing mtd0, but I think only this
will give you the above mentioned boot sequence. Don't brick your AP.
Roland

DON'T erase mtd0!,
as I remeber it is enought to erase mtd1.
I tried to boot from network, I used dhcpd from linux as a bootp server
but i wasn't able to force it to offer file to AP.
Please look throught archive.

I tried to boot AP this way, because I got Flash verification error.

Best wishes

Ericandor



----------------------------------------------------
Załóż konto. Przelewy - 0zł. Darmowe konto oszczędnościowe - 3,25%!
Sprawdź i wygraj Toyotę Aygo! >> Kliknij:
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fing22.html&sid=854

[Wojtek A.]

Post by Roland Mieslinger

Post by Arco
I have tried it several times and I think I'm missing some small step.
1. did anyone succeed on using this?
2. how do I force an invalid flash?
Arco

Hi Arco,
i'm not sure but maybe the key is "used by the bootstrap functionality
of the bootrom".
dev: size erasesize name
mtd0: 00010000 00002000 "Bootloader"
mtd1: 00350000 00010000 "Access Point Firmware"
mtd2: 000a0000 00010000 "Flash Filesystem"
When flashing new firmware only mtd1 and mtd2 are modified, but mtd0 is
always unmodified. I'd not recommend erasing mtd0, but I think only this
will give you the above mentioned boot sequence. Don't brick your AP.
Roland

DON'T erase mtd0!,
as I remeber it is enought to erase mtd1.
I tried to boot from network, I used dhcpd from linux as a bootp server
but i wasn't able to force it to offer file to AP.
Please look throught archive.

I tried to boot AP this way, because I got Flash verification error.

Best wishes

Ericandor



----------------------------------------------------
Załóż konto. Przelewy - 0zł. Darmowe konto oszczędnościowe - 3,25%!
Sprawdź i wygraj Toyotę Aygo! >> Kliknij:
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fing22.html&sid=854

[Roland Mieslinger]

Post by Wojtek A.

Post by Roland Mieslinger

Post by Arco
I have tried it several times and I think I'm missing some small step.
1. did anyone succeed on using this?
2. how do I force an invalid flash?
Arco

Hi Arco,
i'm not sure but maybe the key is "used by the bootstrap functionality
of the bootrom".
dev: size erasesize name
mtd0: 00010000 00002000 "Bootloader"
mtd1: 00350000 00010000 "Access Point Firmware"
mtd2: 000a0000 00010000 "Flash Filesystem"
When flashing new firmware only mtd1 and mtd2 are modified, but mtd0 is
always unmodified. I'd not recommend erasing mtd0, but I think only this
will give you the above mentioned boot sequence. Don't brick your AP.
Roland

DON'T erase mtd0!,
as I remeber it is enought to erase mtd1.
I tried to boot from network, I used dhcpd from linux as a bootp server
but i wasn't able to force it to offer file to AP.
Please look throught archive.
I tried to boot AP this way, because I got Flash verification error.
Best wishes
Ericandor

I agree not erase mtd0. But erasing mtd1 will start the normal "rescue
boot", this is different from the above mentioned boot method.

Roland