Eric Christopherson <echrist...@gmail.com> writes:
> I'm wondering if it can be compiled with only free tools,
Yes, specifically avr-gcc, avr-libc, (GNU) make and Perl
> what OSs are supported,
I know it compiles on Linux, I've heard that it might compile on
FreeBSD, I would guess that it does on OSX and it might even work on
Windows with Cygwin. Assuming that you install an avr-gcc toolchain.
> what's used for testing, etc.
Usually a real C64 and actual hardware.
> One thing I'm especially interested in is whether there is an emulator
> for an actual assembled uIEC-SD device so it can be tested with
> OpenCBM or VICE.
OpenCBM should be able to send commands to a uIEC, but its accelerated
transfer modes are not supported. There is no emulation of any
sd2iec-based device in VICE.
-ik
--
You received this message because you are subscribed to the Google Groups "µIEC Users Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uIEC-users+...@googlegroups.com.
To post to this group, send email to uIEC-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/uIEC-users/uk2h9npx5.fsf%40dragon.akana.de.
For more options, visit https://groups.google.com/d/optout.
> Eric Christopherson <echrist...@gmail.com> writes:
>>
>> (When I mentioned OpenCBM on VICE on IRC, groepaz said he thinks the
>> OpenCBM support in VICE is crap and useless; and, should be removed, which
>> horrified me!)
>
> I fully agree with groepaz on that point. The OpenCBM support in VICE is
> basically a high-level drive emulation that forwards the commands and
> file accesses to an external drive, resulting in poor compatibility even
> if you try to access a 1541 through it. That makes the feature rather
> useless in practice; it would be much better if people would just use
> d64copy to create an image file; and, load that into VICE than trying to
> access a real 1541 from VICE with OpenCBM.
Agree, this should never have been implemented. Every question I've ever
seen about it dealt with the limitations. Has anyone ever used it; and, it
worked for what they wanted it to? :)
On Tue, Jun 28, 2016, Ingo Korb wrote:
> Eric Christopherson <echrist...@gmail.com> writes:
>
> > I have noticed that OpenCBM's cbmcopy command allows you to upload a
> > turbo program to the C= device (the specific code depends on the model
> > cbmcopy thinks it is) and also allows you to specify the X*1541
> > communication mode; for me only the "original" (=slowest) mode works
> > with the uIEC. So when you say "accelerated transfer modes" do you
> > mean one of the things I just described?
OK. I'm still not sure, though, what specific "accelerated transfer modes"
you were referring to in the email further upthread (i.e., when you said
"OpenCBM should be able to send commands to a uIEC; but, its accelerated
transfer modes are not supported."). Would you care to clarify?
Eric Christopherson <echrist...@gmail.com> writes:
> I'm wondering if it can be compiled with only free tools,
Yes, specifically avr-gcc, avr-libc, (GNU) make and Perl
> what OSs are supported,
I know it compiles on Linux, I've heard that it might compile on
FreeBSD, I would guess that it does on OSX and it might even work on
Windows with Cygwin. Assuming that you install an avr-gcc toolchain.
On Tue, Jun 28, 2016 at 1:12 PM, Ingo Korb <m...@akana.de> wrote:
Eric Christopherson <echrist...@gmail.com> writes:
> I'm wondering if it can be compiled with only free tools,
Yes, specifically avr-gcc, avr-libc, (GNU) make and Perl
> what OSs are supported,
I know it compiles on Linux, I've heard that it might compile on
FreeBSD, I would guess that it does on OSX and it might even work on
Windows with Cygwin. Assuming that you install an avr-gcc toolchain.
OK, thanks. I was able to get it built under Linux. But when I put the .bin on the card (in the root of partition 1), it didn't seem to read it in; the version string is the same as before (something including g73a4dfc). I seem to recall the bootloader checks to see if it's a valid firmware, and not the one currently installed. How does it do that?
(I'm thinking it was via CRC. I see that a CRC is generated in the build process.)