Posts by Jens

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.


Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.

Don't Panic. Please wash hands.

  • Mk2 Compatibility with Kawari

    Quote from Kaninbjerget

    It was just to examplify that for the SID you can trick it to think a non real SID like ARMSID, BackSID, SwinSID etc. is an genuine 8580 by bridging a 1k resistor on pin 25 and 26 thereby not being annoyed by a blinking LED and in chipset info it'll say 8580 detected.

    That suggestion originally came from me, somewhere in this forum. However, that's not an option on the VIC, as the detection doesn't work with a normally-unused pin, but with the black level output of the non-initialized VIC chip. So if the Kawari developers want to approach us from the other side, that "startup value" could be adapted.


    For the LED, I could think of a setting "disable error-blinking". I honestly don't remember how much space there is left in the MCU flash to add things, but we'll look into it. Peter's next visit is not too far away, and we should put that on higher prio next time.


    Jens

  • Bvision Program failed error

    Thanks - that explains it: Your PCI bridge is not listed in the autoconfig space, so the driver refuses to load. TBH, I don't know if that means you have a hardware problem, or if the PCI bridge is added to the autoconfig chain by software (so your CVPPC would just need a flash update). You should attempt to get that second entry in the autoconfig chain before you try anything else with P96.


    Hint: Please update your P96prefs program to V47.12 from Aminet, that version is a bit more verbose with it's error output and will tell you why most of the GUI options are greyed out.


    Jens

  • ZZ9000 and AmiTCP?

    You might have a conflict with Roadshow - if it was installed before, you may have parts of it still in your user-startup or other startup script. It may not be launched at all if you want to run AmiTCP. You can't have to stacks (and as a result, two bsdsocket libraries) in one system.


    Jens

  • Mk2 Compatibility with Kawari

    Quote from Kaninbjerget

    Pal it gets right. Here's the debug info:
    VIC-II: Unknown (3A 3A 0000 PAL)

    Does it also get NTSC right? Can you configure it to be NTSC and re-try?


    Quote from Kaninbjerget

    (but hey I've had two 85xx that detected wrong as 65xx

    Did this happen on one of our boards, and do we have a support case for that?


    Quote from Kaninbjerget

    When using it and Kawari and it has been powered off a a long time (few minuttes) then video is garbled and neither a regular nor the unstopable reset (KFF uses the unstopable) resolves it

    The VIC chip does not get a reset signal, so no matter what reset you're sending, it's not going to see it.


    Jens

  • Bvision Program failed error

    Would you please make an output file from showconfig? Not a screenshot, so please use


    showconfig >ram:config.txt


    and then attach the "config.txt" file to your posting.


    thanks,

    Jens

  • General Information on the various Indivision Models

    Quote from turrican9

    Would be nice with some kind of small circuit we could solder on the TC64V2s aswell to get rid of the ghosting.

    It will involve de-soldering some SMD components before such a PCB can be applied.Still need to find a contractor who can do SMD assembly and another miling run after components have been soldered. Solder spots on such a mod-PCB needs to have castellated holes at the edge, and this one is near-impossible to assemble if that milling process is done before component assembly.


    Again, not forgotten, but also impossible to bump in terms of priority right now.


    Jens

  • General Information on the various Indivision Models

    Quote from RokiS

    I think the priority should be to create an anti-ghosting mod for ECS v2.

    That's not off the table, but deeply buried in a huge pile of work that I need to do in order to keep the lights on here. We're *very* short on labour force right now, with half of my employees on sick leave.


    Quote from RokiS

    the only sensible one is to introduce HDMI

    I have already decided against that, for four reasons:


    1) price. My goal is to keep the "hobby Amiga" as affordable as possible, and adding HDMI is a major bump in the bill of materials.

    2) power consumption/heat: I'd like to avoid such a heat-source especially in an A600, where space is very congested and you have hardly any chance to dissipate the heat generated by the HDMI encoder

    3) there are WAY more VGA monitors that are compatible with 50Hz and V-Sync than there are DVI/HDMI monitors that can do the same. In continuation of my first point, these 50Hz/VSync compatible monitors are a lot cheaper than any HDMI monitor you can buy, and they often have the better aspect ratio for an Amiga (4:3 instead of 16:9).

    4) size: With a HDMI encoder, the circuit board will become larger, and it won't fit some target computers any more. I really don't want to have even more versions of flicker fixers.


    Quote from shan2752

    It would also be extremely convenient to allow for the display of Flash Floppy OSD, which is more viable for the Amiga 500.

    We won't be able to take in the same OSD as FlashFloppy is "inserting" into the RGB signals of an Amiga, but we may be able to add an interface for using the OSD that is in the flicker fixer already. If we're adding live config (which is very likely), we will need a similar CIA adapter as we are using on Indivision AGA MK3. We could add a connector there for a 3.3V (5V tolerant) serial interface, where an MCU could send OSD data at a fixed baud rate. We'd need contact to the authors of FlashFloppy, or some specification about the requried size (number of lines and chars/line).


    Quote from shan2752

    Oh and try to better match colors of a 1084 monitor display.

    I believe we've discussed this before: CRT monitors have a different colour space in the first place, and flat screens can't match the "black" that CRTs have. However, we will use a larger FPGA on the new version of Indivision ECS, so we may have the possibility to output a non-linear curve on each colour component. This is not a promise, though; I have no idea how much space we'll really have left in the FPGA after adding what we're already discussing internally!


    Jens

  • Indivision mk3 problem

    Quote from Atryda

    TF1260 50 MHz

    Please try a different or no accelerator and see if there's a difference. Also, please check if there are any software patches in your WB installation, maybe boot from a plain WB disk and see if the problem remains.


    Jens

  • USB for X-Surf-100

    The RapidRoad USB controller can't be made any more, because the host controller chip is not made any more. Looks like you need to make use of your right of revocation (and next time, please read the product description).


    Jens

  • Mk2 Compatibility with Kawari

    Quote from Kaninbjerget

    Something is clearly not always booting as fast as the MK2 expects components to be ready. If you want I can try with regular CIA to see if its the Kawari that is the issue.

    If it's just a matter of startup-time, we could change the MCU code to give the system more of that with a firmware update that can be applied through the USB port of the MK2 board. We may be able to add audio options then as well, but I don't want to promise anything right now. We're very short on labour force right now, with half of my employees on sick leave.


    Quote from Kaninbjerget

    If your Kawari is not on a new enough version you need to upgrade it in a machine that's using DRAM (regular ram, not those modern ram replacement modules).

    Would be interesting to know if this works on a C64 Reloaded MK1. While it uses D-Ram, it has some address-storage in place to fix a VIC bug.


    Jens

  • RR-Net 3 not working

    Quote from clbri

    is there a way to easily copy files via from PC to the SD card of a connected Turbo Chameleon 2 carrier cartridge?

    Nothing "wired" - you always have to remove the physical card and place it into the PC's card reader.


    Quote from clbri

    Or some other way to quickly iterate on actual C64?

    ChaCo (Chameleon Control tool) allows direct writing of a binary file into a memory location of your choice, while the C64 is running. I believe the API is open, so you could turn it into a step after compile/assemble in your equivalent of a make file.


    Here's where Tobias could help (he leads software development and documentation of the Chameleon project), but he's currently on sick leave. Might be a week or two until he's back in the saddle.


    Quote from clbri

    2) I notice that my own program is unable to receive data from the network when RR-Net is connected to Turbo Chameleon 2, *unless* I enable the Retro-Replay cartridge. That is quite odd.

    The key setting is the clock port and it's "enable" bit. While all the bit-wise details can be found in the Chameleon programming manual, not all of the registers should be accessed by any software. Again, Tobias should be able to help clarify what's considered good practise and what not.


    Quote from clbri

    The one thing I am aware of is that with a carrier, I should OR memory address 0xDE01 with 1 to set bit 0 there to enable the clock port. I wonder if there might be any other gotchas that I should know of, that could affect this?

    This enable-bit is located in the Retro Replay cartridge, so it's only logical that Chameleon ignores this bit when RR emulation is switched off. However, there may be a way to switch on the clockport without a specific user setting, using the Chameleon registers. And again, it may be considered bad practise to do so.


    Jens

  • Indivision aga mk3 a1200

    Quote from Tj1978

    I had to plug some speakers into the RCA jacks as i understand that Audio over HDMI isnt switched on by default ?

    Right - that's because we don't advertise it, and if Audio is switched on, you have a compatibility problem with DVI-only displays. So the default config is "audio off", and you'll need the config tool for making a change.


    Some settings can be changed (but not saved/persisted) using live config.


    Quote from Tj1978

    Is there a way to find out what firmware im on currently ?

    The OSD should display version information if I remember right.


    Jens

  • General Information on the various Indivision Models

    I'm already working on a follow-up version to Indivision ECS V3. Friday's poll in Twitter/X asked if the Live config feature should be ported from Indivision AGA MK3 to a new ECS version: https://twitter.com/schoenfeld…tatus/1715392636050083852

    Not a real competition between the options, I know, as the general usability increases by a lot if you have live config. Just wanted to point everyone to the advertisement I've posted there :-)


    Jens