Hi, Andre. F1C800 differs in : another DRAMC controller and more SDRAM memory regarding f1c100 or f1c200s/f1c600, faster core, two TVIN, MIPI. It's more convinient to solder for DIY fans, etching and soldering at home, as i am. Notable devices using this chip? I know at least 3 car multimedia systems, one is under Pioneer brand, two car videoregistrators, few adverticement displays... not so much, though, but i've not tryed to find more. Boot0 for this SoC jumps to FEL if it can''t find boot1, but how to upload u-boot in this case? Using sunxi-tools while in FEL, but DRAM init already made? If device can't work by it's own, but only with PC sunxi-tools help, it's a dead end... I already learned that disassembling and porting code-flow to C will not work so easely, without datasheet for DRAM controller there are nothing to debug, because we know nothing. Anyway if noone interested, i'm abandoning this project, thanx for the answer and good luck. воскресенье, 5 января 2025 г. в 05:37:19 UTC+3, Andre Przywara:
> On Tue, 24 Dec 2024 12:50:48 -0800 (PST) > Sergey Goncharov <kho...@gmail.com> wrote: > > Hi, > > > Hi, guys. Is enyone interested in participating in adding support for > > f1c800 in u-boot? I have Melis SDK, current status is: disassembled > using > > IDA boot0, reversed all uart-clock-dram-related stuff, u-boot starts, > > spawns messages to console, but seems i made a mistake somewhere or most > > likely can't find usual AW init magic, because after my dram_init every > > register related to clock/dram mimics those after init using original > > boot0, but dram anyway fails to read and fails at 10-th write, so > > dram_size_detect can't be passed. Original boot0.bin 100% ok, burned it > to > > sd-card, device detects dram, passes all tests and fails at part where > it > > wants boot1, i have it as a separate bin but can't use because boot0 > want > > it on flash instead of sd-card, my custom board have only sd-card. If > > someone interested in such project, mail me, i'll upload somewhere my > > u-boot sources. > > Do you know how different the F1C800 is from the F1C100/200? We support > the latter in mainline U-Boot, including DRAM init. > As for "anyone interested in participating in adding support": there > seems to be little interest in the ARMv5 Allwinner SoCs lately, > especially when it comes to mainlining something. There was some > momentum like 2 or 3 years ago, but it pretty much dried up since. Are > there any notable devices using this chip? > > As for using the vendor boot0: Try to just have boot0 on an SD > card, and nothing else. If boot0 cannot find boot1 anywhere, I have > seen some versions entering FEL mode (after DRAM init), so you could > then upload U-Boot proper or a kernel, and use it from there. > Otherwise you might be able to hack boot0 to enter FEL mode by > branching to 0xffff0020, at some time after it has initialised the DRAM. > This worked for me on some chips. > > Otherwise debugging the DRAM init routines is not easy (as you probably > already know), and I am afraid there are not many people out there > being able to help you. > > Cheers, > Andre > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. To view this discussion, visit https://groups.google.com/d/msgid/linux-sunxi/7af8e811-226b-44a4-a287-c32e22f2e605n%40googlegroups.com.
