Configuration utility

[Daniel England]

Heyas!

I'm very excited to say that I've been working on a new utility for the Mega65 and that it is nearing completion.

Paul has been working on a whole new set of boot up options and has gotten me to write a configuration utility, the equivalent of a PC's BIOS configuration utility, which will be available from the kickstart/kickup procedure.  It is one of a number of utilities that will be available to the user from the start-up process to assist in the use and set-up of the machine.

I believe Paul has made it available in the latest version of the px100MHz branch if you want to see it.  I think the procedure to launch it is to boot once to BASIC (I think this is a temporary requirement) and then reset with the Alt key held down.  You will then be able to launch the configuration utility from a menu.

The utility has mouse support and is highly adaptable.  It will be easy to add features and options to it in the future.  I'm really rather proud of it.  It can be compiled to run on a stock C64 if you want to try it in VICE.

I hope you will like it!

Daniel.

[Gurce Isikyildiz]

Heya Daniel,

Had a look last night, and it is looking quite nice, a very retro BIOS feel to it :)

I hope to build the latest bitstream to see how it's looking on the hardware, but got this error on the latest from the px100mhz stream:

ERROR:HDLCompiler:806 - "/home/gurce/mega65-core/src/vhdl/charrom.vhdl" Line 4640: Syntax error near "X"3C"".
ERROR:HDLCompiler:854 - "/home/gurce/mega65-core/src/vhdl/charrom.vhdl" Line 25: Unit <behavioral> ignored due to previous errors.

Haven't had a chance to look into it yet, when I get back home...

[Gurce Isikyildiz]

Aah, I spotted it, a missing comma in "src/vhdl/charrom.vhdl", the build is chugging away now, looking forward to seeing it tonight :)

[Paul Gardner-Stephen]

Hello,

I have since fixed this bug in the auto-generation of charrom.vhdl

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-development+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Gurce Isikyildiz]

As I couldn't see the commit for your fix in the repo yet, here's a manual fix I did to get it building for me (I'm guessing this is what your fix was?):

Modified "src/tools/preparepng.c" as follows:

    // 4KB = 2x 256 char = 2KB charsets
    for(charsets = 0 ; charsets<21 ; charsets++) {

I also noticed a strange quirk... When re-synthesising, it kept complaining at the xst with the same error message as before:

ERROR:HDLCompiler:806 - "/home/gurce/mega65-core/src/vhdl/charrom.vhdl" Line 4640: Syntax error near "X"3C"".
ERROR:HDLCompiler:854 - "/home/gurce/mega65-core/src/vhdl/charrom.vhdl" Line 25: Unit <behavioral> ignored due to previous errors.

I found this odd, as the fix had generated a new charrom.vhdl file, and the line 4640 no longer contained the text mentioned in the error (X"3C").

The problem seemed to go away after I deleted the "build-logs/*_0.log" file related to the previous build. I've got no idea why doing that made any difference, but it did... And now my next synthesis seems to be chugging along fine now (it got through the xst step).

To unsubscribe from this group and stop receiving emails from it, send an email to c65gs-developm...@googlegroups.com.

[Gurce Isikyildiz]

Aah, my issue with the xst build log output seemed to be due to this line in "run_ise":

    echo xst ${ISE_COMMON_OPTS} -ifn "isework/${TARGETNAME}.xst" -ofn "isework/${TARGETNAME}.syr"
    xst ${ISE_COMMON_OPTS} -ifn "isework/${TARGETNAME}.xst" -ofn "isework/${TARGETNAME}.syr" >> $outfile1

Looks like it was appending to the pre-existing log file instead of starting the log file from scratch. I'll swap over to ">" and commit that change.

Also, I'm suspecting that Xilinx tools such as xst, map, par don't produce any exit status codes upon a compilation error, so the make system seems to want to plod along despite problems at these steps...

I was pondering whether I could add something in to detect errors within the contents of these log files. Something like this?

ERRORS=`grep "Number of errors" $outfile | cut -d":" -f2 | cut -d"(" -f1 | tr -d '[:space:]'`

Basically, it tries to hunt down any lines like this in the log output:

Number of errors   :    2 (   0 filtered)
Number of warnings :    0 (   0 filtered)
Number of infos    :    0 (   0 filtered)

So this new ERRORS var will just contain the error number "2", so we could then exit from run_ise with this value instead:

if [ $TASK == xst ]; then
    #
    # ISE: synthesize
    #
    echo "==> $datetime Starting: xst, see ${TARGET}.syr"
    echo xst ${ISE_COMMON_OPTS} -ifn "isework/${TARGETNAME}.xst" -ofn "isework/${TARGETNAME}.syr"
    xst ${ISE_COMMON_OPTS} -ifn "isework/${TARGETNAME}.xst" -ofn "isework/${TARGETNAME}.syr" > $outfile1
    ERRORS=`grep "Number of errors" $outfile1 | cut -d":" -f2 | cut -d"(" -f1 | tr -d '[:space:]'`
    exit $? $ERRORS
fi

How does that sound?

[Gurce Isikyildiz]

Ok, got a few things out of the way tonight, made an Ubuntu VM, monitor_load runs fine from there, managed to push the new bitstream across by via monitor_load and fpgajtag.

I saw the config screen on the hardware, nice way to end my day :-)

--

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-development+unsubscribe@googlegroups.com.