<paowz>
I flashed upon sdcard each binaries like said in the README_sdcard.txt..right..
<paowz>
when I powered on the board, nothing appeared.. so I opened an image I manage to boot from. Therefore, I could compare offset binaries (flashboot.img, flashdata.img etc..)
<naobsd>
what's "nothing appeared"?
paowz has left #linux-rockchip ["Leaving"]
paowz has joined #linux-rockchip
<paowz>
sorry..
<naobsd>
what's "nothing appeared"?
<paowz>
well.. nothing came up at FIQ interface
<paowz>
I then thought I have missed something..
<naobsd>
and what's "manage to boot"
<paowz>
(no message whatsoever on serial)
<paowz>
"manage to boot" = succeed at booting
<naobsd>
I guess you write idb_sector_* but properly but you didn't write Flash*.bin etc
<naobsd>
I never tried such a case, but if it's really "nothing", then FlashData and FlashBoot didn't work
<paowz>
actually I did.. I "dd" a binary I look into before flashing it upon sdcard
<paowz>
so I opened rock_pro_lite_ubuntu_14.04_server_141030_sdcard.img which is functional out of the box
<paowz>
(I mean, you unzip it, you flash it, it works..)
<viric>
mh I can't recover my mk802iv
<viric>
I start maskrom mode
<viric>
it uploads a boot code, boots it, and it says "wait for maskrom start", hangs there 10 or 20 seconds, and "wait for maskrom failed".
<naobsd>
paowz: if rock_pro_lite_ubuntu_14.04_server_141030_sdcard.img is functional, why you got "Invaid tag" error? you didn't explain something?
<paowz>
sorry, I'm not clear.. I'm trying to build my own kernel and rootfs, that's why I've tried the link you gave me few days ago.. and when I saw I could not boot using the files supplied in the archive, I then started to look into a functional image to see how were offset the binaries..
<paowz>
naobsd: FlashData takes care of DDR init, if I'm not wrong.. this binary looks okay, I see DDR initialization..
<naobsd>
paowz: you said "I see nothing" "I see DDR initialization". which is correct?
<paowz>
hmm.. yes indeed I missed a step.. I forgot to mention my TTL2USB cable was dead..
<naobsd>
paowz: my binaries showed "nothing"? your dead ttl2usb cable showed "nothing"?
<paowz>
naobsd: I'm starting over to get sure of what I'm saying (did some many tests in every directions..) hold on a second ;)
<naobsd>
viric: you can explain more about detail
<naobsd>
viric: about what you did exactly
<paowz>
naobsd: ok, just flashed everything but the kernel and the rootfs.. and I got this: http://pastebin.com/A8AE9CLA
<paowz>
so this confirms the fact that I hadn't given another try to this binaries from the moment I realized the TTL2USB cable was dead..
<paowz>
..since this is the first time I see such an output..
<paowz>
here is the parameter file I flashed: http://pastebin.com/q6kqDfRn it tells the board a "boot" partition is at 0x2000, here's my question, aren't we supposed to flash parameter flash at this address ?? or "boot" is supposed to talk about parameter file, actually ?
RayFlower has quit [Read error: Connection reset by peer]
RayFlower has joined #linux-rockchip
<viric>
naobsd: I tried flashing things with rkflashtools...
<viric>
naobsd: not in maskrom
<viric>
I couldn't make it boot a linux kernel
<viric>
(that was months ago)
<viric>
this week I wanted to recover the supplied mk802iv image from rikomagic
<viric>
and I went into a "IDB failed" thing when trying to flash. Then I looked at forums and they seemed to suggest the maskrom mode
<naobsd>
paowz: I think I explained about "offset"... please see README.sdcard.txt
<naobsd>
paowz: you flashed parameter at logical 0x0 properly
<viric>
in this maskrom mode I can't get beyond "Wait for maskrom start"
<naobsd>
paowz: you need to flash boot and kernel to logical 0x2000/0x6000
<viric>
(and next fail after some seconds)
<naobsd>
viric: I think rkflashtool will not say "IDB failed" "wait for maskrom start" etc
<viric>
naobsd: right, with rkflashtool I failed to flash, then I tried upgrade_tool
<naobsd>
viric: what you need is explain what you did _exactly_
<viric>
What I did to reach this state?
<paowz>
naobsd: ok.. these are not absolute address, then..
<viric>
hm I downloaded the img from rikomagic to restore it to factory firmware
<viric>
(months ago I was doing experiments with linux kernels)
<viric>
I unpacked the image, and I tried to flash the parameters first, with rkcrc + rkflashtool
<viric>
(of course I didn't remember that there have to be multiple copies of the parameters, etc., but I thought that I can't brick it so I try)
<viric>
If I flash the parameters with rkflashtool, they appeared as "written". Reading and displaying them was working fine
<viric>
But once I rebooted, they were erased.
<viric>
I could flash parameters again, I checked they are right, I rebooted, and they were erased. Boot failed. I can't remember the serial port output
<viric>
it didn't boot any firmware; I didn't have to keep reset button to get into flashable mode. That's where it boots straight
<viric>
So as my attempts failed, I decided to run the upgrade_tool.
<viric>
(with the full image directly)
<naobsd>
viric: it sounds like NAND is dead. if you cannot remember serial console output, why you don't try to get output again?
<paowz>
naobsd: ok, parameter file expects logical addresses.. another thing I don't get (I feel a bit ashamed, in fact..) what do you put in "boot" partition, since FlashBoot.bin has already been used when you reach that point ?
<viric>
I think I pasted it here
<viric>
let me check logs
<viric>
SdmmcInit=2 20
<viric>
Fail!
<viric>
unsigned!
<naobsd>
paowz: FlashBoot.bin is _not_ boot.img
<viric>
Boot ver:
<viric>
!!!No parameter
<viric>
does this ring a belL?
<paowz>
naobsd: ok.. "boot" partition is for boot.img. This is the binary you get when you use mkbootimg for RockChip along with initrd, right ??
ssvb has joined #linux-rockchip
<paowz>
mkbooting(Image + initrd) ==> boot.img
<naobsd>
paowz: kernel+ramdisk image made by mkbootimg or ramdisk image by rkcrc
<naobsd>
paowz: no reason to assume it must be special
<paowz>
I mean why do we have to put kernel twice ?? (one in "boot" partition in boot.img and another one in "kernel" partition)
<naobsd>
viric: can you post complete output?
<viric>
naobsd: hm not now. I will in +5h
<naobsd>
paowz: no need to put kernel twice
<paowz>
parameter file contains "boot" partition and "kernel" partition
<naobsd>
paowz: parameter file contains only about partition layout. you can put (or not) any data freely.
<paowz>
ok.. so in the parameter file provided in the archive "kernel" partition is not mandatory since we supply a kernel in boot.img inside "boot" partition.. ?
<naobsd>
paowz: yes, 100% same as NAND case. nothing is special.
cnxsoft has quit [Quit: cnxsoft]
<paowz>
ok.. silly question, why this parameter file contains about 2 partitions ? it's just a proposal for a layout, in fact ?
<naobsd>
paowz: which parameter file? that one you posted shouldn't be mine
<naobsd>
paowz: and you can edit parameter freely with text editor
<naobsd>
paowz: as same as NAND case. nothing is special.