proper offsets for gordon flash tool, and bringup.
Moderators: BigEvilCorporation, prophet36
proper offsets for gordon flash tool, and bringup.
Based on vhdl (actually assembly in mem_arbiter.vhdl) i would assume that fpga.bin is flashed at 0x0, and firmware.bin at 0x60000. Is it correct?
I've flashed and verified the spi using those offsets, but firmware is not booting up. I can confirm that fpga is loaded correctly. All voltages and jumpers are proper.
I've flashed and verified the spi using those offsets, but firmware is not booting up. I can confirm that fpga is loaded correctly. All voltages and jumpers are proper.
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
Re: proper offsets for gordon flash tool, and bringup.
Hi,fixel wrote:Based on vhdl (actually assembly in mem_arbiter.vhdl) i would assume that fpga.bin is flashed at 0x0, and firmware.bin at 0x60000. Is it correct?
I've flashed and verified the spi using those offsets, but firmware is not booting up. I can confirm that fpga is loaded correctly. All voltages and jumpers are proper.
try:
flcli -v <USB ID UMDK> -p J:A7A0A3A1:spi-talk.xsvf
gordon -v <USB ID UMDK> -t indirect:1 -w fpga.bin.bin:0x0
gordon -v <USB ID UMDK> -t indirect:1 -w firmware.bin:0x60000
That is from my notes. I can try it out if you have issues.
Cheers,
Minty.
Last edited by MintyTheCat on Wed Oct 29, 2014 12:53 pm, edited 1 time in total.
UMDK Fanboy
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
OK, I have tried both of those too and they work.fixel wrote:i've tried 20140524 and dev branches. At this point i'm inspecting my soldering. Could be that something is not soldered or shorted.
Prophet36 gives some advice on the hardware and bring up in this other thread:
viewtopic.php?t=1825&postdays=0&postord ... cededfb585
Please keep us posted on your progress and we will try to help you get up and running.
Cheers,
Minty.
UMDK Fanboy
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
it's mentioned in bulletpoint #9 here:MintyTheCat wrote: Could you tell us where you found that file please?
viewtopic.php?p=24032#24032
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
Mmmmm, but I cannot find it in the Repo. We shall have to ask Prophet36.fixel wrote:it's mentioned in bulletpoint #9 here:MintyTheCat wrote: Could you tell us where you found that file please?
viewtopic.php?p=24032#24032
My UMDK Kit was made for me and I only had to carry out the Unit-Test tests to verify the bitstream written to the FPGA and that the toolchain was correctly installed as the hardware had been checked prior to me receiving it.
The Unit-Tests do calculate expected results and then compare what the MD with UMDK connected returns but that is a step further on than you are at by this stage.
Step #9 is in order to check that the bitstream is correct and has been written correctly but I would have thought that it would fail at an earlier stage during writing and you would see that during the writing stage - what do you get on your command-line when you execute Gordon?
I am not at my MD Dev machine now but I can repeat the steps that you would need to carry out and see what I get and then compare that to what you get but give me a couple of days.
Perhaps send Prophet36 a PM and see what advice he can give.
Cheers,
Minty.
UMDK Fanboy
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany
Cksum is part of the early examples provided with FPGALink:
http://www.swaton.ukfsn.org/temp/vhdl_paper.pdf
http://www.swaton.ukfsn.org/temp/vhdl_paper.pdf
UMDK Fanboy
Ok, i got it to boot the firmware, but now chasing another issue:
The SD Card doesn't clock any data out ---
i see the command sent to SD, but no response, not even ACK.
I've noticed that spi_master is coded to be MODE3, but MODE0 is recommended for SD, could that be the issue?
Here is the LA trace -- no response on CMD0 from SD...
The SD Card doesn't clock any data out ---
i see the command sent to SD, but no response, not even ACK.
I've noticed that spi_master is coded to be MODE3, but MODE0 is recommended for SD, could that be the issue?
Here is the LA trace -- no response on CMD0 from SD...
-
- Very interested
- Posts: 484
- Joined: Sat Mar 05, 2011 11:11 pm
- Location: Berlin, Germany