ath_ddr_initial_config(278): (ddr2 init)
ath_sys_frequency: cpu 775 ddr 650 ahb 258
Tap values = (0x8, 0x8, 0x8, 0x8)
Base:0x80000000, Top:0x80400000, Res logbuf:0xa03fb000, log_magic:0xffffffff kseg: 0xa0000000
Top of RAM usable for U-Boot at: 803fb000
Reserving 247k for U-Boot at: 803bc000
Reserving 192k for malloc() at: 8038c000
Reserving 44 Bytes for Board Info at: 8038bfd4
Reserving 36 Bytes for Global Data at: 8038bfb0
Reserving 128k for boot params() at: 8036bfb0
Stack Pointer at: 8036bf98
I suspect I fried the RAM, or the FLASH or both.
if it's just the flash chip, and I can replace it ( I can work with SOIC ), can it be revive?
If it's the RAM chip I guess I'll just keep it in the bin for now
U-boot decides there is only 4 MB of RAM. I think that Atheros chips probe for RAM rather than have it hard-coded in uboot. So if that's the case there's a RAM-related hardware failure. If it is hard coded in uboot maybe your uboot is corrupt.
It's a stupid mistake on my part out of being curious.
I had it running well untill I decided to probe what's going on in the background.
I tried to use a usb to serial that has a jumper option for 3.3v/5v , it was set for 5v.
I just realized just now that one pad of the four is probably supply output and not input.
I assume that it could be the RAM because it only sees 4MB out of 128, I saw a similar
output from a wiki post that shows the correct amount of memory.
I don't have access to u-boot, it's not accepting any input.
It obviously is not correct, it is dead but definitely showing some sign of life.
I reflashed the corrupted original bin file I saved and I'm now back to original serial output that hangs.
I'm not inclined to buy another one just yet so I could extract u-boot to save this one, 'will wait and search for now.
This will probably not materialize, as I got me a used UAP-AC-PRO, hopefully it doesn't die before I bricked it again this thing can cook an egg