<aw>
so 1484404 is done means load fjmem finished? so then what's the next step script trys to do? will 'frequency 6000000' mean UrJtag starting to set somethings into fpga?
<xiangfu>
sorry. next should be "initbus fjmem opcode=000010"
<aw>
what does this meaning? fpga trys to do somethings you guess?
<xiangfu>
aw, I would advice change on Jtag board. try reflash again.
<xiangfu>
using another jtag board, try reflash again.
<xiangfu>
initbus mean try to initializes the external memory bus, then we can access the flash chip
<xiangfu>
aw, each m1 you using different jtag board, right? then we can try to using one working jtag board on this m1. to detec if it's jtag board problem.
<aw>
xiangfu, yes, each m1 with its won jtag board. mmm...good idea
<kristianpaul>
also i wondered the dmesg output after connect that board, but yes better try another
<aw>
xiangfu, your this idea makes me happy now. ;-)
<kristianpaul>
:)
<aw>
although I don't change another jtag board to 0x32, but now it's flashing... I just tried to plug out and replug again though. ;-)
<aw>
ox32: hmm...d2/d3 dimly lit after flashed. with BEN shorter cable. :(
<aw>
let's change a new jtag board.
<aw>
after changed to other jtag rc1 board...still stops at 'Bitstream length: 1484404'
<kristianpaul>
hum, but jtag serial cabled passed testing all okay it seems, so dunno if can be a jtag-serial board  issue
<wolfspraul>
sounds like the problem is with the flash chip?
<xiangfu>
maybe
<aw>
used a new jtag rc2 still stops at there.
<aw>
okay, so you guys think it's probably a flash chip problem related?
<aw>
not bad. at least narrow the area to find possible cause.
<aw>
tks
<wolfspraul>
well
<wolfspraul>
we are guessing
<wolfspraul>
but at least 0x32 never successfully flashed and booted before
<wolfspraul>
unlike for example 0x34
<wolfspraul>
so for 0x32, yeah, maybe it's just a flash soldering problem?
<aw>
yes, never successfully flashed, but at least today became only was flashing... once
<wolfspraul>
yes, but then it didn't boot (configure)
<kristianpaul>
yeah, probably flash something around or flash chip it self
<aw>
possible . I'll see it. just asked here to know more steps about scripts. ;-)
<kristianpaul>
but from the pastebin looks like jtag lost connection with fjmem...
<kristianpaul>
xiangfu: hi,
<xiangfu>
kristianpaul, hi
<kristianpaul>
xiangfu: you did some dd from /dev/zero to the first blocks of the 512Mb flash you sent me, to make it recognice by mm bios?
<kristianpaul>
or formated? (mkfs.fvat)
<kristianpaul>
i made the mistake of format the card now it is recogniced but i hit a bug with the fat library implemented in bios...
<kristianpaul>
in wich it dint recognice files on the memory..
<xiangfu>
kristianpaul, ? I lost. what file I sent to you?
<kristianpaul>
card
<kristianpaul>
512mb and 1Gb remenber
<kristianpaul>
?
<xiangfu>
oh. memcard. 512MB.
<kristianpaul>
sorry my english is not very good today..
<kristianpaul>
yeah
<xiangfu>
the BIOS only know fat16.
<kristianpaul>
it was working well, actually i  put boot.bin cmdline.txt and initrd.bin on it
<kristianpaul>
yeah, but happen that i formated the card, in fat16, but the error is not about fat32 not supported.