Jump to content

HiassofT

Members
  • Content Count

    1,203
  • Joined

  • Last visited

  • Days Won

    1

HiassofT last won the day on November 10 2011

HiassofT had the most liked content!

Community Reputation

715 Excellent

About HiassofT

Contact / Social Media

Profile Information

  • Gender
    Male
  • Location
    Salzburg, Austria

Recent Profile Visitors

21,420 profile views
  1. I haven't got around to update the documentation with the changes I did in the 3.11 (beta) versions. Please have a look at the "ChangeLog.txt" in the latest software ZIP - currently https://www.horus.com/~hias/freezer/software/beta/freezer-software-200413.zip (see also below). The majority of the documentation is still valid, only very few things changed (eg the "M" memory map command) and most of the new additions like the CartEmu presets should be pretty self-expanatory (I hope). One difference of the new Panos Freezer that might not be too obvious is that it uses a different flash chip than the previous versions. This chip has a smaller internal block size (4k instead of 64k), which is a good thing as it allows you to separately reflash each 8k bank and you no longer need to worry about the previous 64k restriction. Here's the list of changes from the 2020-04-13 changelog: BTW: the current 3.11 beta software versions also work on the older 2005 and 2011 Freezer models. so long, Hias
  2. Simple, non-technical explanation: without a proper power supply anything can happen and it's pure luck if something works or not. A bit more technical/detailed: glitches in the power rail may lead to shifts in the thresholds of the input-stage of circuits. Or internal circuitry in ICs, like flip-flops, may loose their state. Glitches on the power rail also usually also affect the output stage of ICs and produce glitchy output. Input stages of other circuits, even if their power source is stable, react differently to those glitches as the exact switching point between low and high isn't specified but dependent on manufacturing processes and variations in silicon etc. So, what possibly could have happened is that a short glitch on the power rail caused a glitch on the PHI2 signal which was "noticed" on one CPLD (your problematic freezer) and lead to double-clocking of the Freezer state machine, but not on the other CPLD. A glitch on the reset input at the wrong time could have caused similar fatal effects. There are a lot of other effects that can happen due to short or longer power glitches and one common thing of these is that they are nasty and can be hard to diagnose from the software/logic side. So, in case of odd issues (no matter if it's on a PC, an old Atari, a router or some other system) it's always a good idea to check all external and internal power rails with a scope. Switch-mode power supplies are the norm nowadays so a standard DMM won't do a job and may show a stable 5V or 3.3V supply. But a scope will reveal if there's ripple/glitches on the rail, eg due to aging capacitors. so long, Hias
  3. Ah, bad/insufficient power makes perfect sense, that's about the number one cause of most odd/unexplainable/intermittent issues. so long, Hias
  4. Very puzzling. I had expected to see issues from the production tool as well - not sure why flash and RAM access seem to be fine but freezing doesn't work on this one XE model. I can't remember ever seeing such an issue combination. A shot in the dark: if you have a scope it might be interesting to probe the PHI2 and the shortened PHI2 signals (the latter is on pin 13 of the HCT123), both on the working freezer and the non-working one when plugged into the problematic XE. The falling edge of the shortened PHI2 should be about 50ns before the falling edge of PHI2. so long, Hias
  5. Can you try flashing the Freezer to (latest version) stock firmware with the production tool? https://www.horus.com/~hias/tmp/prodtool-200726.zip This will wipe the whole flash memory and also perform some basic Freezer RAM tests. Just set the flash write and ramdisk switch to "on", all other switches to "off" position and boot the ATR. If something's not quite right then you should get some error messages on screen - a screenshot of that could help narrowing down if there's some issue with flash or RAM. so long, Hias
  6. -k disables hotkey support - I usually have that enabled. Especially SHIFT+CONTROL+S is quite handy if some program trampled over the stack area or if you later power up/enable another drive. So far no one reported compatibility issues with hotkey support enabled. * hotkeys: The keyboard IRQ routine of the OS is patched and you can control the SIO patch using various keystrokes: SHIFT+CONTROL+S Clear SIO speed table and enable highspeed SIO SHIFT+CONTROL+N Disable highspeed SIO (normal speed) SHIFT+CONTROL+H Enable highspeed SIO SHIFT+CONTROL+DEL Coldstart Atari so long, Hias
  7. I had a quick go at it and added options to only verify and fix 16k XL/XE OS ROM checksums to my patchrom tool. I've attached a win32 console executable. Run "patchrom -c atari.rom" to verify the ROM checksums or "patchrom -C atari.rom fixed.rom" to save the ROM with fixed checksums to "fixed.rom" so long, Hias patchrom-133.zip
  8. Have a look at the "patchrom.cpp" (and "patchrom.h") file of my highspeed SIO patch, esp the update_rom_csum function (and the get_csum1/2 and update_checksum_block functions it calls): https://github.com/HiassofT/highspeed-sio/blob/master/patchrom.cpp#L135 so long, Hias
  9. Thanks for the quick merge! So far only @Tempest seems to have been affected by the issue, we were PM'ing the last couple of days trying to figure out why his cart stopped working. Took us a while to figure out that RespeQt was the culprit. so long, Hias
  10. A very important warning: don't use RespeQt versions from late 2018 up to 5.3 when flashing your The!Cart. These versions have broken 8k-sector-size ATR handling and will soft-brick your cart - you can revive them by reflashing with "FLASH.COM" from "thecart.atr" though (latest version is here https://www.horus.com/~hias/thecart/software/thecart-software-170924.zip) RespeQt version 4 from here https://github.com/ebiguy/RespeQt/releases (and previous versions) are working properly. I've opened a PR with a fix, so future RespeQt versions should be safe to use again https://github.com/RespeQt/RespeQt/pull/6 so long, Hias
  11. /dev/atarisio0 is for using 16550/16C950 UARTs (on-board or on PCI/PCIe) with the AtariSIO kernel driver. If you are using a USB SIO2PC adapter it's not relevant to you. If you use a 16550/16C950 UART that driver will in general work better than the /dev/ttySx support in AspeQt/RespeQt (and result in lower system load). I've created AtariSIO almost 20 years ago, when "real" serial ports were the norm and USB adapters were exotic, and still support it. In the meanwhile it can also deal with USB adapters and other serial ports and you can also use it with eg a Lotharek dual 1050-2-PC/SIO2PC USB adapter or a Raspberry Pi to directly access a 1050 or XF551 in 1050-2-PC mode. You can find more info about AtariSIO and download it here: https://www.horus.com/~hias/atari/#atarisio so long, Hias
  12. Just to be clear: I don't recommend getting an old boat anchor, I only mentioned that as a last resort in case of a really limited budget as the other options in the < 350 USD range aren't too great either. Quality-wise you can't count much on it, these are 25-40 year old things that can break down any time and may be unrepariable. And feature-wise the current hobbyist scopes also have a lot more to offer. Features in used LeCroy, R&S or HP/Agilent (digital) scopes may be better but good luck finding them for 200-300 USD 🙂 so long, Hias
  13. In this case it's best to look out for a used scope in the <= 70 USD range and hope it'll keep working for some time. If it breaks down you won't have lost too much money. To repair an analog scope you'd need another scope (chicken, egg...) and lots of the mid/late 1980ies and later models contain custom parts that are unobtainable (eg the Tek 2465 etc). Digital scopes are basically unrepairable, unless it's some very basic thing like a broken cap in the power supply. OTOH new scopes in the 200-300 USD range aren't too attractive by today's standards and sooner or later you may realize you really miss the features that would have been present in the 350 USD models. As these cheap scopes have almost no value on the second-hand market (everyone knows about their limitations) you'd have to completely write off the money spent on it if you want to move on to a better model or just keep using it. Buy cheap, buy twice. so long, Hias
  14. This is a really bare bone digital scope and I wouldn't recommend it unless your budget is really tight and you can get it for 50 - max 100 USD. The ~350 baseline set by the mentioned Rigol and Siglent hobbyists scopes is where I'd start looking as they offer a lot more value for the money than the older/cheaper scopes (like the Hantek or eg the Rigol DS1052E which seems still to be available for about 250 USD). With these newer/current scopes you'll get higher waveform update rates which are not only helpful to catch occasional glitches but are only used to do intensity graded display. I.e. you get an "analog scope like" display where glitches/rarer occurring waveforms are displayed in darker color. That's enormously helpful to get a quick impression how the signal looks like. You'll miss that with the Hantek and older Rigol, they'd just jump between the waveforms (or might not even catch that every tenth time the signal only reaches 3V instead of 5V). Large sampling memory (several megpoints compared to a few kpoints), especially in combination with segmented memory is really helpful to capture a longer sequence and then zoom in. Or, with segmented memory, record a bunch of traces and then check into the one you are interested in (which might be eg the 5th or 6th occurrence of the trigger, not the first or the last). You get a really nice choice of advanced triggering features that the simpler/older scopes don't offer. Some of them are really helpful as well as you can trigger for setup/hold violations, occasional glitches etc. Ah, and also helpful are the various builtin decoders (RS232, I2C, SPI). While these decoders are a bit bare-bone compared to the one of (PC-based) logic analyzers they are still quite usable and you can quickly check eg which command frame your Atari sent to a disk drive etc. so long, Hias
  15. All Rigol DS1000 and 2000A models ship with all options included. For more bandwidth either buy the higher specced models or search the eevblog forum for riglol so long, Hias
×
×
  • Create New...