Dies ist eine mobil optimierte Seite, die schnell lädt. Wenn Sie die Seite ohne Optimierung laden möchten, dann klicken Sie auf diesen Text.

Evolux for Pingulux ext. yaffs2

    Nobody is reading this thread right now.
AW: Evolux for Pingulux ext. yaffs2

kann mal jemand mit toshiba chipset bitte orig booten
dann telnet:
./unspare2/dev/mtd1 /tmp/oob.img

Sie müssen registriert sein, um Links zu sehen.
enptacken und nach /tmp vorab schieben und chmod 755 drauf. dann o.g. ausführen.
des erzeugt ein oob.img mit 328bytes.
des bitt ma raren/taren und hier anhängen.

edit: das wird aber auc nix bringen denke ich.
 
AW: Evolux for Pingulux ext. yaffs2

unspare2? Wo finde ich das?
: not found
 
AW: Evolux for Pingulux ext. yaffs2

unspare2 ist in tmp chmod auf 755
Dann o.g. Befehl
=> not found
 
AW: Evolux for Pingulux ext. yaffs2

cd /tmp
./unspare2 /dev/mtd1 /tmp/oob.img


next try:
 
Zuletzt bearbeitet:
AW: Evolux for Pingulux ext. yaffs2

[root@stlinux]#./unspare2 /dev/mtd1 /tmp/oo.img
unspare2-0.2.3: OOB extracting tool for yaffs2utils
cannot open the device /dev/mtd1
ioctl failed
failed[root@stlinux]#

V4: Auch nicht:
stm-nand-emi: Configuring EMI Bank 1 for NAND access
[MTD][NAND]: nand_decode_id: failed to decode NAND device ID
Failed to decode NAND READID [98 dc 90 15]
No NAND device found!!!

Wenn 0x98 und 0xdc klar sind, was ist dann noch mit 90 15. Die müssen wohl auch noch vom kernel verstanden werden, oder?
Ich meine die komplette READ ID vom Chip muss verstanden und entsprechend gesetzt werden.
Code: 
A NAND-based Flash memory chip returns in response to the Read ID command several data bytes (identifier).
 The most frequent identifier type is 4 bytes long, but it can be longer as well. 
 Identifier structure:
 Byte 1 describes the chip manufacturer (Vendor ID).
 Byte 2 describes the memory chip itself as a device (Device ID).
 [COLOR=#ff0000]Bytes 3–n[/COLOR] describe in vendor-specific format the settings of the  internal memory chip structure including memory page size, memory cells  type, presence of several segments, etc.
 
Zuletzt bearbeitet:
Re: AW: Evolux for Pingulux ext. yaffs2

Sorry, ich würde ja gern mithelfen. Aber ich komme erst am Wochenende wieder an die Box ran
 
AW: Evolux for Pingulux ext. yaffs2

So, hier mal die erste Info (Spark gebootet, Ausgabe mittels dmesg, kein Comcable Logging):

NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Zum Vergrößern anklicken....

Bild kommt gleich.

Edit: Hier das Bild:
Sie müssen registriert sein, um Links zu sehen.
 
Zuletzt bearbeitet:
AW: Evolux for Pingulux ext. yaffs2

en comlog wäre nützlich von evo boot ob da auch 90 15 kommt.

@neuss,
2 seiten vorher schreibst du du hättest auch toshiba ram?
und da bootet evo am pinguplus bei dir?



falls dem so is kann ich nämlich hier aufhören zu suchen denn dann haben die user wos nich geht schlicht defekte hw-chipse was bei edision ja eigentlich standard is!
 
Zuletzt bearbeitet:
AW: Evolux for Pingulux ext. yaffs2

Ja, ich habe Toshiba-NAND und nein: Evolux und ProtoluxV3 booten nicht bei mir.
Das oben ist das dmesg von Sparks.

Das "[98 dc 90 15]" ist aus dem BootLOG vom Evo mit anschliessender Kernel-Panic.

Was sagt denn ein Bootlog vom Evo, das auch fertig bootet?

So weit ich noch weiss:
Viprex Plus Kiste hat Hynix und läuft mit EVO
DIVIDIS Plus neue Kiste hat auch Toshiba und bootet EVO auch nicht zuende.
 
Zuletzt bearbeitet:
AW: Evolux for Pingulux ext. yaffs2

ok.
hab ma in mei heimatboard angefragt ob da jemand noch was weiss.
wenn des nix wird bliebe nur noch en evolux als jffs2 bauen und für die "geschädigten" zur verfügung stellen was dann natürlich einiges langsamer booten wird.
 
AW: Evolux for Pingulux ext. yaffs2

Und ich werd mich mal noch ein wenig weiter in die Materie einlesen. Vielleicht finde ich ja noch einen Hinweis.
 
AW: Evolux for Pingulux ext. yaffs2

pinky1981 schrieb:
en comlog wäre nützlich von evo boot ob da auch 90 15 kommt.
Zum Vergrößern anklicken....

Bitte:

NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Zum Vergrößern anklicken....

weiteres Comlog:
ªªýû

Board: STx7111-Mboard (MB618) [32-bit mode]
info: Disregarding any EPLD


U-Boot 1.3.1-g057e7c28 (Oct 21 2011 - 09:58:11) - stm23_0043 - YW 1.0.021 Rel

DRAM: 128 MiB
NOR: 8 MiB
NAND: 512 MiB
In: serial
Out: serial
Err: serial
IdentID : 09 00 08 00 00 3c 1a
Hit ESC to stop autoboot: 0

Loading from NAND 512MiB 3,3V 8-bit, offset 0x18000000
Image Name: Linux-2.6.32.57_stm24_0210
Image Type: SuperH Linux Kernel Image (gzip compressed)
Data Size: 2414524 Bytes = 2.3 MiB
Load Address: 80801000
Entry Point: 80802000
## Booting image at 80000000 ...
Image Name: Linux-2.6.32.57_stm24_0210
Image Type: SuperH Linux Kernel Image (gzip compressed)
Data Size: 2414524 Bytes = 2.3 MiB
Load Address: 80801000
Entry Point: 80802000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
found phy at addres = 1
stmac_phy_get_addr(): id1 = 0x7, id2 = 0xc0f1
stb_id = 908003c1a

Starting kernel console=ttyAS0,115200 root=/dev/mtdblock6 rootfstype=jffs2 rw in it=/bin/devinit coprocessor_mem=4m@0x40000000,4m@0x40400000 printk=1 rw ip=${ipa ddr}:${serverip}:${gatewayip}:${netmask}:LINUX7109:eth0ff bigphysarea=6000 stm maceth=msglvl:0,phyaddr:1,watchdog:5000 nwhwconf=device:eth0,hwaddr:24:00:08:00: 3C:1A Manufacture=Spark-Project STB_ID=09:00:08:00:00:3C:1A - 0x00000000 - 0 ...

Linux version 2.6.32.57_stm24_0210 (pinky@asuslappy) (gcc version 4.5.2 20110124 (STMicroelectronics/Linux Base 4.5.2-78) (GCC) ) #1 PREEMPT Mon Jul 23 11:51:53 CEST 2012
Boot params:
... MOUNT_ROOT_RDONLY - 00000001
... RAMDISK_FLAGS - 00000000
... ORIG_ROOT_DEV - 00000200
... LOADER_TYPE - 00000000
... INITRD_START - 00000000
... INITRD_SIZE - 00000000
Booting machvec: sat7111
Node 0: start_pfn = 0x40000, low = 0x50000
Zone PFN ranges:
Normal 0x00040000 -> 0x00050000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00040000 -> 0x00050000
Spark-7111 board initialization
STx7111 version 3.x
bpa2: partition 'bigphysarea' created at 0x48000000, size 32768 kB (0x02000000 B )
bpa2: partition 'LMI_IO' created at 0x4a000000, size 98304 kB (0x06000000 B)
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: console=ttyAS0,115200 root=/dev/mtdblock6 rw init=/bin/devi nit coprocessor_mem=4m@0x40000000,4m@0x40400000 printk=1 rw ip=${ipaddr}:${serve rip}:${gatewayip}:${netmask}:LINUX7109:eth0ff stmmaceth=msglvl:0,phyaddr:1,wat chdog:5000 nwhwconf=device:eth0,hwaddr:24:00:08:00:3C:1A Manufacture=Spark-Proje ct STB_ID=09:00:08:00:00:3C:1A
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
PVR=04909200 CVR=60880000 PRR=00009a10
I-cache : n_ways=2 n_sets=512 way_incr=16384
I-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
D-cache : n_ways=2 n_sets=512 way_incr=16384
D-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
Memory: 116224k/262144k available (3013k kernel code, 1021k data, 116k init)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:600
Failed to enable clk CLKA_REF, ignoring
Failed to enable clk CLKA_PLL0LS, ignoring
console [ttyAS0] enabled
sh_tmu: TMU0 used for clock events
sh_tmu: TMU0 used for periodic clock events
sh_tmu: TMU1 used as clock source
Calibrating delay loop... 448.51 BogoMIPS (lpj=897024)
Mount-cache hash table entries: 512
CPU: STx7111
[STM][PM-Sys]: ilc3 @ 4096
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
DMA: Registering DMA API.
Switching to clocksource TMU1
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
[STM]: [PM]: Suspend support registered
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Slow work thread pool: Starting up
Slow work thread pool: Ready
NTFS driver 2.1.29 [Flags: R/W].
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.13)
JFS: nTxBlock = 909, nTxLock = 7272
msgmni has been set to 227
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered (default)
lirc_dev: IR Remote Control driver registered, major 61
lirc-stm: probe found data for platform device lirc-stm
lirc-stm: STM LIRC plugin using IRQ 125 in IR mode
lirc_dev: lirc_register_driver: sample_rate: 0
STMicroelectronics LIRC driver initialized.
STMicroelectronics ASC driver initialized
stm-asc.0: ttyAS0 at MMIO 0xfd032000 (irq = 121) is a stm-asc
stm-asc.1: ttyAS1 at MMIO 0xfd033000 (irq = 120) is a stm-asc
loop: module loaded
physmap platform flash device: 00800000 at 00000000
physmap-flash: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition information
Creating 3 MTD partitions on "physmap-flash":
0x000000000000-0x000000080000 : "Boot firmware"
0x000000080000-0x000000780000 : "Kernel"
0x000000780000-0x000000800000 : "Reserve"
stm-nand-emi: Configuring EMI Bank 1 for NAND access
ONFI flash detected
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
cmdlinepart partition parsing not available
Creating 4 MTD partitions on "stm-nand-emi.0":
0x000000000000-0x000000800000 : "Spark Kernel"
0x000000800000-0x000018000000 : "Spark Rootfs"
0x000018000000-0x000018800000 : "E2 Kernel"
0x000018800000-0x00001ff00000 : "E2 RootFs"
stmmac - user ID: 0x10, Synopsys ID: 0x33
No HW DMA feature register supported
Enhanced/Alternate descriptors
RX Checksum Offload Engine supported
TX Checksum insertion supported
Wake-Up On Lan supported
hso: drivers/net/usb/hso.c: 1.2 Option Wireless
usbcore: registered new interface driver hso
nwhw_config: (eth0) setting mac address: 24:00:08:00:3c:1a
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
stm-ehci stm-ehci.0: st-ehci
stm-ehci stm-ehci.0: new USB bus registered, assigned bus number 1
stm-ehci stm-ehci.0: irq 169, io mem 0xfe1ffe00
stm-ehci stm-ehci.0: USB 0.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
stm-ohci stm-ohci.0: stm-ohci
stm-ohci stm-ohci.0: new USB bus registered, assigned bus number 2
stm-ohci stm-ohci.0: irq 168, io mem 0xfe1ffc00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
i2c /dev entries driver
Linux video capture interface: v2.00
sh_tmu: TMU0 kept as earlytimer
sh_tmu: TMU1 kept as earlytimer
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
[STM][PM-Sys]: emi @ 40
[STM][PM-Sys]: gpio @ 20
STMicroelectronics - Coprocessors st231 Init
st231.0 Coprocessor -------------------------------------------
flags 0001 RAM start at 0xbf000000 size 0x00400000
cop. addr 0x40000000
Channels : Not defined
IRQ : not used
---------------------------------------------------------------
st231.1 Coprocessor -------------------------------------------
flags 0001 RAM start at 0xbf400000 size 0x00400000
cop. addr 0x40400000
Channels : Not defined
IRQ : not used
---------------------------------------------------------------
DMA: Registering fdma_dmac.0 handler (16 channels).
IRQ 140/fdma_dmac.0: IRQF_DISABLED is not guaranteed on shared IRQs
stm-fdma stm-fdma.0: firmware: using built-in firmware fdma_STx7111_0.elf
DMA: Registering fdma_dmac.1 handler (16 channels).
platform fdma_dmac.0: SLIM hw 0.0, FDMA fw 2.1
IRQ 141/fdma_dmac.1: IRQF_DISABLED is not guaranteed on shared IRQs
stm-fdma stm-fdma.1: firmware: using built-in firmware fdma_STx7111_1.elf
platform fdma_dmac.1: SLIM hw 0.0, FDMA fw 2.5
Advanced Linux Sound Architecture Driver Version 1.0.21.
ALSA device list:
#0: STMicroelectronics STx7111 cut 3.x SOC audio subsystem
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers


Edit: Eine blöde Frage habe ich noch: Wo soll denn das hier eigentlich stehen im Comlog:
neuss67 schrieb:
Das "[98 dc 90 15]" ist aus dem BootLOG vom Evo....
Zum Vergrößern anklicken....

Also die Zahlenfolge?
 
AW: Evolux for Pingulux ext. yaffs2

Bei Dir steht:
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Also (0x)ad (0x)dc und nix weiter
Manufacturer ID = ad für Hynix
Device ID= dc

Das [98 dc 90 15] kommt vom Toshiba-Nand, womit der Kernel aber nichts anfangen kann und daher ausgibt; Failed to decode.

Falls sich jemand da einlesen möchte, der aber bessere Linux-Kenntnisse als ich hat:
Code: 
I am able to successfully flash and boot using a Micron  MT29F4G08ABADA NAND WP Flash chip, which seems to have the same specs  and technology as your target chip.  I am able to program the device  installed in the i.MX28 EVK NAND flash socket over the micro USB  connector link from a Windows PC running the Freescale Manufacturing  Tool.  I am then able to boot the EVK from NAND flash to load a custom  Linux kernel and UBIFS root filesystem.
Getting the NAND chip to  be recognized during the kernel boot scan and programming the chip via  the Mfg Tool are independent operations, and both must be successful.   Since the output you sent is generated from running the Mfg Tool,  perhaps you should start there and continue until the programming is  successful.  Then, you can move on to getting the EVK to boot from NAND.
I  have compared a capture file of output from the debug terminal during a  successful Mfg Tool programing run with yours  I have not looked  exhaustively, but our outputs track very closely except for the NAND  chip-related items.  The critical difference begins at line 106 in my  file:  "Scanning for NAND Flash chips...".  Interestingly, during your  run, the next line ("NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda  (Micron NAND 256MiB 3,3V 8-bit") shows that your NAND chip was detected  and the ID's were read correctly.
I believe the Mfg Tool  "updater_ivt.sb" kernel uses the same technique to recognize NAND flash  types as works in the "normal" kernel.  The first step is to locate the  device in the following array of structures:
    struct nand_flash_dev nand_flash_ids[ ],
which is initialized in the following kernel source file:
    [ drivers/mtd/nand/nand_ids.c ]
Your chip ID (0xDA) matches the following entry:
[COLOR=#008000]    /* 2 Gigabit */[/COLOR]
    {[COLOR=#A31515]"NAND 256MiB 3,3V 8-bit"[/COLOR], 0xDA, 0, 256, 0, LP_OPTIONS},
whereas my chip ID (0xDC) matches the entry in the next size block:
[COLOR=#008000]    /* 4 Gigabit */[/COLOR]
    {[COLOR=#A31515]"NAND 512MiB 3,3V 8-bit"[/COLOR], 0xDC, 0, 512, 0, LP_OPTIONS},
This matching is how you received single "NAND device:..." output line in your file.
The second step is to locate the device in one of the arrays of structures of the following type:
    struct nand_device_info[ ],
which are initialized in the following kernel source file:
    [ drivers/mtd/nand/nand_device_info.c ]
There  are a number of these arrays of structures, corresponding to different  "Types", as shown in the following "directory" from the same file:
/*
* A table that maps manufacturer IDs to device information tables.
*/
    static [COLOR=#0000FF]struct[/COLOR]nand_device_type_info nand_device_type_directory[] __initdata = {
        {nand_device_info_table_type_2, [COLOR=#A31515]"Type 2"[/COLOR]},
        {nand_device_info_table_large_mlc, [COLOR=#A31515]"Large MLC"[/COLOR]},
        {nand_device_info_table_type_7, [COLOR=#A31515]"Type 7"[/COLOR]},
        {nand_device_info_table_type_8, [COLOR=#A31515]"Type 8"[/COLOR]},
        {nand_device_info_table_type_9, [COLOR=#A31515]"Type 9"[/COLOR]},
        {nand_device_info_table_type_10, [COLOR=#A31515]"Type 10"[/COLOR]},
        {nand_device_info_table_type_11, [COLOR=#A31515]"Type 11"[/COLOR]},
        {nand_device_info_table_type_15, [COLOR=#A31515]"Type 15"[/COLOR]},
        {nand_device_info_table_type_16, [COLOR=#A31515]"Type 16"[/COLOR]},
        {nand_device_info_table_bch_ecc12, [COLOR=#A31515]"BCH ECC12"[/COLOR]},
        {nand_device_info_table_bch_ecc24, [COLOR=#A31515]"BCH ECC24"[/COLOR]},
        {0, 0},
    };
In  the same file there are functions and logic that locate a particular  entry for a specific NAND flash chip.  In my case, my chip is matched to  the following entry:
/*
* Type 7
*/
static [COLOR=#0000FF]struct[/COLOR]nand_device_info nand_device_info_table_type_7[] __initdata = {
< snip >
    {
        .end_of_table = [COLOR=#0000FF]false[/COLOR],
        .manufacturer_code = 0x2c,
        .device_code = 0xdc,
        .cell_technology = NAND_DEVICE_CELL_TECH_SLC,
        .chip_size_in_bytes = 512LL*SZ_1M,
        .block_size_in_pages = 64,
        .page_total_size_in_bytes = 2*SZ_1K + 64,
        .ecc_strength_in_bits = 4,
        .ecc_size_in_bytes = 512,
        .data_setup_in_ns = 20,
        .data_hold_in_ns = 10,
        .address_setup_in_ns = 10,
        .gpmi_sample_delay_in_ns = 6,
        .tREA_in_ns = -1,
        .tRLOH_in_ns = -1,
        .tRHOH_in_ns = -1,
[COLOR=#A31515]        "MT29F4G08AAA"[/COLOR],
    },
< snip >
};
This  table is the source of critical information regarding the NAND  geometry, timing, etc. that appears in the debug terminal listing when  the chip is successfully recognized during the kernel scan.
The matching function for Micron devices in the same file begins with the following:
static [COLOR=#0000FF]struct[/COLOR] nand_device_info * __init nand_device_info_fn_micron([COLOR=#0000FF]const[/COLOR]uint8_t id[])
{
[COLOR=#0000FF]    struct[/COLOR]nand_device_info *table;
 
[COLOR=#008000]    /* Check for an SLC device. */[/COLOR]
[COLOR=#0000FF]    if[/COLOR](ID_GET_CELL_TYPE_CODE(id) == ID_CELL_TYPE_CODE_SLC) {
[COLOR=#008000]        /* Check number of simultaneously programmed pages. */[/COLOR]
[COLOR=#0000FF]        if[/COLOR](ID_GET_MICRON_SIMUL_PROG(id)) {
[COLOR=#008000]            /* Type 7 */[/COLOR]
            table = nand_device_info_table_type_7;
        }
[COLOR=#0000FF]        else[/COLOR]{
[COLOR=#008000]            /* Zero simultaneously programmed pages means Type 2. */[/COLOR]
            table = nand_device_info_table_type_2;
        }
[COLOR=#0000FF]        return[/COLOR]nand_device_info_search(table, ID_GET_MFR_CODE(id),
        ID_GET_DEVICE_CODE(id));
    }
< snip >
 For  my chip, there is an entry in both the "Type 2" and "Type 7" arrays  that would seem to match, but the matching function returns the "Type 7"  entry.  Your chip seems to appear in the "Type 2" array, but is missing  from the "Type 7" array.  Since our chips are very similar and seem to  use the same technology, I would expect that the would be of the same  "Type".
So, your chip appears to fail to match a  "nand_device_info" structure.  I believe that the table used in the  "updater" code that runs as part of the Mfg Tool uses the same tables,  which would explain the failure to recognize your chip.  It appears that  your next step must be to add support for your chip within the context  of the Mfg Tool.
Once your chip is recognized, the other major  issue you will face is deciding what type of flash filesystem to use.  I  am successfully using UBIFS, but JFFS2 is also a widely-used choice.   You will have to make that decision following your own requirements and  criteria.

Nachtrag:
Der Hynix NAND ist ONFI-Nand und scheint damit keine Extended Parameters zu brauchen, dem reichen Hersteller- und Device-ID.
Das ist beim Toshiba nicht so einfach, der muss dem System klar seine Parameter mitteilen, also 0x90 und 0x15.
 
Zuletzt bearbeitet:
AW: Evolux for Pingulux ext. yaffs2

nand_device_info.c gibt es nicht und auch im gesamten kernelsource is kein nand_device_info zu finden
das is auch nicht das problem.
der code an sich passt.
man muss zu allererst die exakte chip-typenbezeichnung des toshiba wissen. und die steht nunmal auf dem chip selber drauf.
sowas wie: TC58NVG3S0F
erst dann kann man da ran gehen.
warum bei dir unspare2 nicht geht kann ich nicht nachvollziehen.
hab hier gmTriplex gebootet-orig der auch toshiba chip hat und da gehts!(fw 1.2.54)
kannst auchmal statt "mtd1" mal "mtdblock1" versuchen.
 
Zuletzt bearbeitet:
Du musst dich einloggen oder registrieren, um hier zu antworten.

Ähnliche Themen

A
Tools/Anleitungen Solution: How to install updates for Petka without needing to upgrade past 8.3
Antworten
4
Aufrufe
5K
KARMAN81
K
S
ROM "Iphone 7" Wie bekomme ich die Letzte BETA oder DEV version auf mein Iphone 7 das muss eine 16 Version sein.
Antworten
0
Aufrufe
253
Soliver84
S
S
Portals
110 111 112
Antworten
2K
Aufrufe
107K
salidos
S
A
Primo NextGen Frontzosd Skins Frontzosd Silver Skin for New NextGen 64 bit
Antworten
9
Aufrufe
3K
Titanic52
M
Tipps & Tricks How to Use BMW ISTA P to Program and Code?
Antworten
0
Aufrufe
5K
Marshall87
M
Menü
Anmelden
Registrieren
Für die Nutzung dieser Website sind Cookies erforderlich. Du musst diese akzeptieren, um die Website weiter nutzen zu können. Erfahre mehr…