sept18 branch

23 views
Skip to first unread message

Gurce Isikyildiz

unread,
Oct 6, 2018, 11:02:50 PM10/6/18
to MEGA65 Development
Hiya all,

I saw Paul's post on the improved monitor and matrix mode updates. I'd like to try update m65dbg to work with the latest changes.

So I've made a start at rebuilding the 'sept18' branch, but ran into this build issue:

make[2]: Leaving directory '/home/gurce/mega65/mega65-core/iverilog/driver'
make[1]: Leaving directory '/home/gurce/mega65/mega65-core/iverilog'
( cd src/verilog ; ../../iverilog/driver/iverilog  -tvhdl -o ../vhdl/6502_top.vhdl 6502_*.v )
sh: 1: sh: 1: /home/gurce/mega65/mega65-core/iverilog/lib/ivl/ivlpp: not found
/home/gurce/mega65/mega65-core/iverilog/lib/ivl/ivl: not found
Makefile:521: recipe for target 'src/vhdl/6502_top.vhdl' failed


I noticed that the two missing "iverilog/lib/ivl/ivlpp" and "iverilog/lib/ivl/ivl" executables were instead located at:

  • "iverilog/ivlpp/ivlpp"
  • "iverilog/ivl"


I thought I might try copy these to these two into "iverilog/lib/ivl/".


This then gets me the following error:


ERROR: Unable to read config file: /home/gurce/mega65/mega65-core/iverilog/lib/ivl/vhdl.conf
: error: target_design entry point is missing.

I guess I'm going about it the wrong way. Anyone have any thoughts? I'll keep prodding it to get some more ideas.

Gurce Isikyildiz

unread,
Oct 6, 2018, 11:10:23 PM10/6/18
to MEGA65 Development
Ah ok, think I figured it out. The make process builds iverilog, but it doesn't seem to install it.

So I had to do the following:

cd iverilog
sudo make install

Seems to be plodding along with the bitstream build now :)

Gurce Isikyildiz

unread,
Oct 14, 2018, 2:23:10 AM10/14/18
to MEGA65 Development
Alrighty, was getting re-acquainted with the m65dbg source. Connectd it to the nexys board, I'm seeing some things kinda work ('r' command, but seems to have extra carriage returns in it), other things don't ('d' and 'dis').

Just wondering where I can sniff about to learn the changes that occurred to the comms protocol? Should I suss out changes made in commits on mega65-core relating to it?

Paul Gardner-Stephen

unread,
Oct 14, 2018, 2:35:38 AM10/14/18
to Gurce Isikyildiz, C65GS Development
Hello,

There are also some further changes in the oct18 branch for the monitor syntax as I recall.
d now does disassemble, and up and down cursor keys and f1/f3 skip through memory dumping 128 bytes as hex each time.

Paul.

--
You received this message because you are subscribed to the Google Groups "MEGA65 Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to c65gs-developm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages