Recent content by hpo14

A good suggestion of using Rose's metal. But, as i had modified my router to an online nand programmer and i also have another offline nand programmer. It let me easily change / switch nand chip live, without worried about the soldering or desoldering. OK, back to my issue XD. I think the ECC...

With your full nand dump, I got the same "bad result" as mine before. :p (I use a new nand chip with 0 bad block.) NAND ECC BCH-8, page size 0x800 bytes, spare size used 108 bytes NAND flash device: , id 0xc2da block 128KB size 262144KB ... nand: device found, Manufacturer ID: 0xc2, Chip ID...

Although i already have two full nand dump by my own with two different tools from a good rt-ac86u. (one was a python script using dn command to dump content from cfe mode. Another was a nand programmer) But, yes. I'd be glad if you can share it (Prefer google driver or Mega.nz, or i can provide...

OK, back to my situation. The reason i want to build CFE was due to this NAND problem The "bad" one has already replaced a new nand chip. (the full log is in attachment) My good rt-ac86u nand: Could not find valid ONFI parameter page; aborting nand: device found, Manufacturer ID: 0xc2, Chip ID...

maybe HW error ? I found the difference between my good rt-ac86u and bad rt-ac86u (boot loop, already replaced with a new NAND chip) The Good one nand: Could not find valid ONFI parameter page; aborting nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xda nand: Macronix NAND 256MiB 3,3V...

I copied the self build CFE binary (cfe4908.bin, cfe4908ram.bin, cfe4908rom.bin) to "targets/cfe/sysdeps/RT-AC86U" to replace the default files. and make a full build make rt-ac86u with success. Then flash the custom firmware (RT-AC86U_<version>_cferom_ubi.w) to my RT-AC86U. With a reboot after...

It's really wired. :p

Maybe ~ Its magic that the "commit b93cd5bb222db1733668e9d89cfca0153880c0d7 (HEAD, tag: 384.19)" only exist on github's source code but not in the code I downloaded. $ git log --all | grep -B5 "384.19 final" commit 8c72854f4d1037a5fbab468135143560fee7d80e Author: Eric Sauvageau...

oops, our source code maybe different ..... This is what i got. when checkout to Tag @ 384.19 hpo14 @ ~/.../ac86/docker/asuswrt-merlin.ng (build-cfe) $ git tag -l | grep 384.19 384.19 384.19-ax 384.19-beta1 384.19-beta1-ax 384.19-beta1-mainline 384.19-beta2 384.19-beta2-ax...

After checkout to Tag "384.19-mainline". Still failed when trying to build CFE binary For error ... make[2]: *** No rule to make target 'bcm63xx_devs.o', needed by 'cfe4908'. Stop. ... So, I modified "src-rt-5.02hnd/cfe/cfe/board/bcm63xx_ram/src/Makefile", remove the line "bcm63xx_devs.o \"...

Very Helpful, but i still meet some error. After build success for full rom docker@6629d9866e60:/build/release/src-rt-5.02hnd/$ make rt-ac86u i tried to build cfe rom. docker@6629d9866e60:/build/release/src-rt-5.02hnd/cfe/build/broadcom/bcm63xx_rom$ export declare -x BRCM_CHIP="4908" declare...

I had the same problem but for RT-AC86U. There do has a manual for build full firmware of router (*.w), but the CFE source code was not even compiled. And the CFE binary was copied from a prebuilt folder "sysdeps". And i modified the CFE source code try to make some build error, but nothing...

Hi, how do you build the CFE firmware ? i just tried to build a custom rt-ac86u fw with some debug printf in cfe code. But i found out the cfe.bin in output was simply copied from a prebuilt folder ( "targets/cfe/sysdeps/RT-AC86U" )

maybe you can mail to "Chris Bellows" https://www.atredis.com/blog/2021/4/23/live-nand-swap He seems find out the pinout. "After enumerating the JTAG pinout on the unpopulated header with a JTagulator, it was possible to confirm access using OpenOCD:"