Activity
From 06/09/2017 to 07/08/2017
07/07/2017
- SA 11:05 PM Feature #24: A board with Atari SOUL!!!! (ROM in block ram support)
- ??? What you mean here?
- FO 09:26 PM Feature #24: A board with Atari SOUL!!!! (ROM in block ram support)
- Also of course nice and fast vs uncached sdram...
sysinfo fp test from 6x->20x :-) I probably need a cache to get this closer to 30-40x, but that will take some work. - FO 09:13 PM Feature #2: PBI support
- Added antic refresh cycles
07/06/2017
- FO 09:28 PM Feature #51: Debug port
- I have a first cut of this building. This will be part of the v15 core.
Next I need to build the capture software to stream this into the PC. Then some post-analysis software, probably a hacked up emulator.
07/05/2017
- FO 09:41 PM Bug #49 (Closed): CORE13 - NTSC/PAL switching
- FO 09:40 PM Bug #49: CORE13 - NTSC/PAL switching
- Fixed, will be in v15 when I release it.
07/04/2017
- FO 09:31 PM Bug #49: CORE13 - NTSC/PAL switching
- Trying to fix this one, but its nasty. I need more brain cycles to fix it...
- FO 09:29 PM Feature #14: Svideo core for first prototype
- Hmm, just reading that IRE is _relative_ so that might be why increasing voltage didn't make anything brighter!!
https://en.wikipedia.org/wiki/IRE_(unit)
So I wonder if I could have a 0V-0.5V signal that uses the correct relative s...
07/03/2017
- SA 06:42 AM Feature #14: Svideo core for first prototype
- Stephen wrote:
> Hate to be a dunce - where is the documentation for cabling s-video from this board?
You can use Green signal for composite video, or Green signal for Luma and Blue signal for Chroma for S-Video, from RGB connector.
- ST 12:31 AM Feature #14: Svideo core for first prototype
- foft wrote:
> For anyone with composite/svideo setup. Please can you tell me what you think of svideo_gtia6.sof vs the previous version.
> ...
Hate to be a dunce - where is the documentation for cabling s-video from this board? I have...
07/02/2017
- FO 10:50 PM Feature #14: Svideo core for first prototype
- For anyone with composite/svideo setup. Please can you tell me what you think of svideo_gtia6.sof vs the previous version.
This is generated more the 'atari way' - i.e. off hue/brightness with phase shifts, rather than being based on ... - FO 11:42 AM Feature #14: Svideo core for first prototype
- I mean svideo and composite, it's the same thing pretty much.
I've got the gtia style one running pretty well for ntsc now. Its interesting to implement if nothing else:) - FO 01:10 PM Bug #54: GTIA issue when Turbo > 4X
- Yeah, this kind of test program is very helpful. Thanks.
- SA 05:54 AM Bug #54: GTIA issue when Turbo > 4X
- Thanks Stephen!
- ST 03:46 AM Bug #54 (Closed): GTIA issue when Turbo > 4X
- I'm attaching a BASIC listing of a PMG test program I wrote to assist in diagnosing an issue with the 1088XEL. For fun, I tried running it with the various Turbo speeds. 1, 2, 4 work perfectly. 8, 16, 32 display issues as shown in the...
07/01/2017
- ST 06:43 PM Feature #14: Svideo core for first prototype
- sadosp wrote:
> Maybe is time to think about implementing one external RGB -> composite/s-video converter, fit directly to VGA output connector.
> ...
My thoughts (coming from NTSC land). We haven't had TVs or monitors with S-Video co... - SA 05:31 PM Feature #14: Svideo core for first prototype
- Maybe is time to think about implementing one external RGB -> composite/s-video converter, fit directly to VGA output connector.
But the question still remain for me if people really need it.
- FO 05:05 PM Feature #14: Svideo core for first prototype
- That works, kind of! Basic screen and star wars shields look the correct colours, but I have no red. Also very grainy and svideo is a single colour?!
- FO 12:59 PM Feature #14: Svideo core for first prototype
- Writing an 'atari-style' implementation instead of going via RGB. Fixed saturation, simple phase shift for colour.
- FO 07:10 AM Feature #14: Svideo core for first prototype
- Interesting...
http://atariage.com/forums/topic/29621-atari-video-circuits-experiment/
So fixed saturation (except gray), just phase shifted for the cols. Then add luma. Might try that rather than generic rgb component. - FO 03:59 PM Feature #53 (Closed): Add version number to settings
- Add version number to settings
06/30/2017
- ST 11:30 PM Bug #52: Atari Control Picture
- foft wrote:
> I checked an older core in case I introduced it with the antic timing changes for pbi. Was bad then, so unrelated.
> ...
Excellent - glad it will be of help. I only recently discovered this cool program. - FO 10:15 PM Bug #52: Atari Control Picture
- I checked an older core in case I introduced it with the antic timing changes for pbi. Was bad then, so unrelated.
This is a nice static picture to debug in sim or signaltap. I like this kind of test case:-) - FO 10:10 PM Feature #14: Svideo core for first prototype
- Added a poke 712,15 for comparison of max values. Interesting how the amplitude for basic 'blue' is so much higher yet the peak amplitude is comparable...
Atari:
!composite_atari_max.png!
Eclaire:
!composite_eclaire_max.png! - FO 09:54 PM Feature #14: Svideo core for first prototype
- I mean see how the 'white' on ready already takes most of the range, without trying to increase it.
- FO 09:54 PM Feature #14: Svideo core for first prototype
- Atari
!composite_atari_basic.png!
Eclaire
!composite_eclaire_basic.png!
We have a range of 0-1v on the DAC. 0-0.3V sync and 0.3V-1.0V is set by changing the dac level. So trouble is its not really enough. Might still need to chan... - FO 09:50 PM Feature #14: Svideo core for first prototype
- Added traces of Atari basic from the scope, to see the voltage level differences.
Eclaire is driving my monitor, Atari is through a 66ohm resistor (little low, so voltage is suppressed a little).
Still, a stark difference!
06/29/2017
- ST 11:30 PM Bug #52 (Closed): Atari Control Picture
- CORE14, PAL & NTSC exhibit the same behaviour. When displaying the attached Atari Control Picture, the colour blocks in column 0 are only displaying the rightmost 4 pixels, not the entire 8.
Altirra (and real hardware) : ACP.png
Ecl... - FO 08:59 PM Bug #49: CORE13 - NTSC/PAL switching
- I think I've identified the problem. If the zpu happens to exit the menu at the end of an 'original' cycle the pbi logic can block the response from a memory access. Now to think about how to implement this in a better way...
06/27/2017
- FO 07:54 PM No news
- No news, I've been ill but am almost better!
Is anyone still alive here?
On an unrelated note found this article on how FPGAs work and thought it might be of interest: http://blog.notdot.net/2012/10/Build-your-own-FPGA
06/23/2017
- FO 07:27 AM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- It's written in c. The Atari core is built with a DMA port and the ability to freeze the 6502. Outside that there is another CPU (the zpu) that draws the menu, handles USB, se card, drive emulation etc. It has quite a lot of custom hardw...
- 91 04:31 AM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- Okay, sounds great. So, is the system menu actually an Atari program or is it VHDL code?
06/22/2017
- FO 09:12 PM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- Yeah, that should work. You just described a multiplexor btw.
Got guests this weekend, so will do the plumbing next week.
06/21/2017
- 91 11:30 PM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- Mark,
It works great! Very Cool! Thank you for the test build. If we can add a toggle to the system menu and assign a variable such as *kb_type* to store the keyboard type, the code change would be pretty simple. I am not versed in VH... - FO 08:56 PM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- I put up a build with your mapping as ansikbd.sof in the usual place. Let me know if it works as expected please.
- FO 09:44 AM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- Thanks
11 is left alt
extended 11 is right alt - I use 1xx for extended xx.
I'll build a test core with your changes, then we can add a switch later. I wonder if I can identify ansi/iso automatically. - 91 02:55 AM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- Rethinking this, I'm not sure if we need to have a user-mappable keyboard at all as long as we have support for both ANSI and ISO keyboards. The only major change from the default ISO layout (besides moving a few keys to account for diff...
- 91 02:37 AM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- TEST
- 91 12:06 AM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- I would say just use a text file, it's easier to create/edit. Also, The EclaireXL could have keys that have no equivalent in an emulator such as a keyboard shortcuts to map each drive, a key to increase the acceleration on the fly, freez...
- FO 09:02 PM Bug #33: Wizard of Wor
- I'm going to build a debug tool to make it easier to track these things down.
For now, a workaround. Use 2x turbo mode! It hasn't crashed yet...
06/20/2017
- SA 09:41 PM Feature #2: PBI support
- Excellent!
- FO 07:08 PM Feature #2: PBI support
- Hias tried out PBI on the v1.
Surprise: Turbo freezer didn't work! Mine works perfectly on v2...
He investigated and found three things:
i) REF_N pullup is a little low, so with any increased capacitance it takes too long to ris... - ND 07:51 PM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- its keyboard mapping from ATARI800WIN Emulator, see attached file
- FO 07:41 PM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- What is an a8k file? Is there already a keyboard mapping file format we can use?
- FO 07:36 PM Feature #14: Svideo core for first prototype
- Worth a read for some background: http://codeandlife.com/2012/10/09/composite-video-decoding-theory-and-practice/#more-1032
After this its 'Video Demystified' for the details - FO 07:12 PM Feature #51 (New): Debug port
- I'm finding it hard to track down issues in some games/programs. Output debug information so I can look into the problem after the fact.
I'm thinking as a starting point something like this:
8-bit output at 4x clock:
AH,AL,D,FLAG
...
06/17/2017
- ND 08:17 AM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- i think reading a key-map file from the SD CART is a good idea, an a8k file? if the key-map file is corrupt or missing a default map will be loaded from the fpga
- 91 05:08 AM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- foft wrote:
> Computer generated c code for TK2 is here: http://atariage.com/forums/topic/263044-developerstesting-required-for-mini-itx-clone-system-eclairexl/page-6#entry3783384
> ...
Is it worth the time,effort, and fpga space? Coul...
06/15/2017
- FO 10:24 PM Bug #33: Wizard of Wor
- Turbo freezer does not freeze it when its in 'frozen blocks' state but does otherwise.
- FO 10:21 PM Bug #33: Wizard of Wor
- Tried a different version and I get the 'freeze with blocks' at the end of every level. Will have to see what happens here - is the 6502 still running until I hit f12 and freeze it?
- FO 09:30 PM Bug #33: Wizard of Wor
- Well I tried many settings in Altirra and can't reproduce with a different hardware variant.
Things I found:
i) Recursive NMIs
ii) No illegal op codes, even works on 65C02 etc.
iii) Still works with zero initialised ram (the eclaire ...
06/14/2017
- FO 08:54 PM Bug #33: Wizard of Wor
- I see this too. Any luck tracking down the cause? I'm hoping @xxl or @xuel can help me here with their machine code wizardry:-)
For now I'm not concerned about the F12 issues, more the core game problem ignoring the F12 menu. There ar... - 91 07:54 AM Bug #33: Wizard of Wor
- I checked a car version on core 14, it started this behavior on the first level after killing monsters and an additional two monsters re-spawn in the upper left which will only move vertically in a small area. After killing these two mon...
06/13/2017
- FO 10:20 PM Feature #11: Non-uk keyboard support (custom keyboard mapping)
- Computer generated c code for TK2 is here: http://atariage.com/forums/topic/263044-developerstesting-required-for-mini-itx-clone-system-eclairexl/page-6#entry3783384
Might be nice to integrate this, archive looks fairly large though i... - SA 08:24 PM Bug #50: CORE13 - Option on initial powerup does not disable BASIC
- foft wrote:
> I suggest multiple os roms with a key to toggle
Yeeha! Sound perfect option in my ears!
- FO 06:45 PM Bug #50: CORE13 - Option on initial powerup does not disable BASIC
- Yeah we should absolutely save this setting too
- FO 06:44 PM Bug #50: CORE13 - Option on initial powerup does not disable BASIC
- I suggest multiple os roms with a key to toggle
- SA 12:24 PM Bug #50: CORE13 - Option on initial powerup does not disable BASIC
- I have catch my self many times to set the older Atari OS (memopad) as default on settings menu only for this reason!!!
Ok if you still do not want to proceed with my proposed way, is possible to change your firmware as to save this spe... - SA 12:17 PM Bug #50: CORE13 - Option on initial powerup does not disable BASIC
- Is the same thing like someone put a simple switch to rom, to disable the Basic on original hardware.
Really I dont mean to patch either a line in OS rom. ;-) - SA 12:12 PM Bug #50: CORE13 - Option on initial powerup does not disable BASIC
- foft wrote:
> Basic on/off is an os thing, I don't want to patch the os in firmware.
> ...
I not mean to patch the firmware Mark.
Asking for a way to disable the Basic with an electronic switch within your firmware. I mean to think th... - FO 08:49 AM Bug #50: CORE13 - Option on initial powerup does not disable BASIC
- Basic on/off is an os thing, I don't want to patch the os in firmware.
Yes we need to see how to get usb keyboard state early on power on. - SA 06:12 AM Bug #50: CORE13 - Option on initial powerup does not disable BASIC
- I don't remember if in the past have ask from Mark to add a future within settings menu, as to be possible to disable the Basic and save the setting.
- SA 06:03 AM Bug #50: CORE13 - Option on initial powerup does not disable BASIC
- Stephen wrote:
> When initially turning on the Eclaire, holding F8 does not disable internal BASIC. However, once booted, if I hold F8 then press F10 to restart, BASIC does get disabled. The built in self test shows the keyboard is re... - ST 02:18 AM Bug #50 (New): CORE13 - Option on initial powerup does not disable BASIC
- When initially turning on the Eclaire, holding F8 does not disable internal BASIC. However, once booted, if I hold F8 then press F10 to restart, BASIC does get disabled. The built in self test shows the keyboard is responding.
- ST 05:31 PM Bug #48: CORE13 - Veronica BASIC not working
- foft wrote:
> So all tests work but veronica basic does not?
> ...
Yes, everything on the ATR I attached works. I will attach the version of Veronica BASIC I was trying to use. This evening I will arrange my desk better so that I can... - FO 08:51 AM Bug #48: CORE13 - Veronica BASIC not working
- So all tests work but veronica basic does not?
I know a bit about veronica, I built a veronica clone for the ultimate cart but never debugged it. - ST 02:40 AM Bug #48: CORE13 - Veronica BASIC not working
- OK - I got the rotator demo working. However, I cannot get Veronica BASIC to load. It either hangs or says it cannot communicate with the cart. Pressing F10 causes my monitor to see the input switch, but I get a black screen, and have...
- ST 02:25 AM Bug #48: CORE13 - Veronica BASIC not working
- Guys - I am very sorry. I was not loading the BIOS first. Veronica is working properly. I tried to delete this, but must not have appropriate permissions.
- ST 02:23 AM Bug #48: CORE13 - Veronica BASIC not working
- VREGREAD passes both tests, VRAMTEST passes the 4 tests.
- ST 02:21 AM Bug #48: CORE13 - Veronica BASIC not working
- Also, VREGREAD fails both tests, and VRAMTEST fails all 4 tests.
- ST 02:14 AM Bug #48 (Closed): CORE13 - Veronica BASIC not working
- I've tried various RAM and NTSC/PAL settings. When I run "detector.com" from the attached ATR, the screen flickers and I get "Veronica Not Detected". My Veronica is a black cased Revision 2.0.
- FO 11:16 AM Bug #49: CORE13 - NTSC/PAL switching
- Yeah I've noticed this too. I think there is a lockup on exiting the menu in general.
- ST 02:17 AM Bug #49 (Closed): CORE13 - NTSC/PAL switching
- I've noticed several times when I switch between PAL and NTSC, then do a "save and apply", when I exit, and exit the main screen the core has frozen and no keys respond (F10, etc.) It doesn't seem to matter if I go from PAL to NTSC, or ...
06/12/2017
- SA 09:57 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- foft wrote:
> It should work with any decent USB supply. So I think we need to improve our end to handle this variation.
> ...
I am ok with this. Is an option!
But if you ask my opinion, I would say that the final purpose of eclaire... - FO 09:37 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- These are all 'quality' usb supplies - well Apple anyway!
- FO 09:34 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- It should work with any decent USB supply. So I think we need to improve our end to handle this variation.
I checked my scope on a 5V supply I built at university and confirmed it does show 5V with that:-) - SA 09:23 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- foft wrote:
> I have power supplies who state 5V, but if I measure them they are not.
I know Mark, and this is the reason who I ask you to buy a tested psu from Samsung.
- SA 09:09 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- ndary wrote:
> i have a meter, just need clear instruction what to do and where to check
> ...
Prepare your meter for *DC Volts* in a range of 10 or 20 volt. After power up your eclaireXL without any peripheral device connected, and pl... - FO 09:03 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- I have power supplies who state 5V, but if I measure them they are not.
You can measure on the joystick ports - or between the power switch and gnd. - ND 08:58 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- i have a meter, just need clear instruction what to do and where to check
Nir - SA 08:50 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- Same reading in the 1st board also?
What the other guys said about it? None have a multi meter to check the voltage?
Can you find this in Switzerland? Is 5.2 volt at 2 Amper! My meter read 5.16 volt on board! Same thing is also the... - FO 08:38 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- I mean tps63002.
I have a multimeter. It still reads 3.8V today after the regulator - and 5V on the input. I trust the scope more - when the software is working:-) - FO 08:36 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- I read it at the switch. I checked with 4 psus - checking each time on the regulated outputs that my scope was still working.
I think we need one of these: tps63001 - SA 08:34 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- Mark, I think is time to send you a digital multi-meter as a gift! ;-)
I have a question. You read the 5v directly at the input, or at the end after the joystick port?
- FO 08:21 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- "It is specified that devices' configuration and low-power functions must operate down to 4.40 V at the hub port by USB 2.0 and that devices' configuration, low-power, and high-power functions must operate down to 4.00 V at the device po...
- FO 08:17 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- "The ATX power supply specification states the 5VUSB rail can be between +4.75V and +5.25V."
I guess we need a regulator to actually get 5V! I also read that many ports output only 500mA until sending them a message.
I wonder if th... - FO 07:59 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- OK, I restarted my scope software and now get the correct readings. So a bit of a mystery but I suspect a plain old bug...
Anyway now I get 3.3V,2.5V and 1.1V as expected. However the 5V line is anything but 5V. I checked 4 different ... - SA 12:36 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- Hi Mark.
I use my 4 digits digital multimeter to take readings. My analogue scope TEK2445, isn't usefull at all for accurate voltage readings, although it have on screen readout. As for the digital scopes, I don't know how accurate are.... - FO 07:29 AM Bug #47: CORE 13 - Paddle, Touchtablet issues
- Ok, so assuming my scope is wrong for now. Its a usb one, I don't trust the absolute levels that much. What are you using to measure Panos?
One thing fed almost direct is 5V from psu to touch tablet. It might be sensitive. I can check...
06/11/2017
- SA 10:41 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- Even a worthless psu rated at 5v @ 500mA who in reality supply with 5.26v, after the regulator read 3.333v
- SA 10:33 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- I use these two power adapters below..
[[https://m-service.prom.ua/p47863721-zaryadnoe-ustrojstvo-white.html]]
[[http://www.awax3.pl/product-pol-4023-Ladowarka-Samsung-EP-TA10EWE.html]]
- SA 10:14 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- foft wrote:
> Maybe my tools are just not calibrated properly.
I don't have touch tablet in my possession, but I try two different psu's with 5 and 5.2 volt output, and at any case I read 3.333v with my voltmeter. I check it on v1 bo... - SA 10:14 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- foft wrote:
> Maybe my tools are just not calibrated properly.
I don't have touch tablet in my possession, but I try two different psu's with 5 and 5.2 volt output, and at any case I read 3.333v with my voltmeter. I check it on v1 bo... - SA 10:12 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- foft wrote:
> Maybe my tools are just not calibrated properly.
I don't have touch tablet in my possession, but I try two different psu's with 5 and 5.2 volt output, and at any case I read 3.333v with my voltmeter. Check it on v1 boar... - SA 10:11 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- foft wrote:
> Maybe my tools are just not calibrated properly.
I don't have touch tablet in my possession, but I try two different psu's with 5 and 5.2 volt output, and at any case I read 3.333v with my voltmeter. Check it on v1 boar... - FO 09:04 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- Maybe my tools are just not calibrated properly. Well anyway the touch tablet does not seem to work with a decent PSU due to small voltage adjustments on the LM339 level. So I think we need to adjust the resistors on that slightly. I thi...
- SA 08:59 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- foft wrote:
> Still this this should be checked, but think its a red herring. I get the same reading on my scope - and on the v1 and prototype. I don't remember these being so far off but guess they have always been. Panos, what did you... - FO 08:52 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- OK, I found that if I connect the Eclaire to my laptop for power, it works. If I connect it to a PSU, it doesn't! The voltage is slightly higher and pushes the threshold too high.
So: weak PSU, touch tablet works. string PSU, touch ta... - FO 08:32 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- Still this this should be checked, but think its a red herring. I get the same reading on my scope - and on the v1 and prototype. I don't remember these being so far off but guess they have always been. Panos, what did you get when you m...
- FO 08:19 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- Going to check this on my scope, I don't trust my multimeter...
- FO 07:53 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- The odd thing is I get 3.8V instead of 3.3V. I don't understand that at all, investigating... This would push the threshold on the LM339 too high for the paddle, but why is it 3.8V?!
- SA 07:42 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- foft wrote:
> I checked the touch tablet, confirmed not working on the new board. Very odd since this worked on v1 and paddles are working, except the bad mapping! Will investigate...
If I remember well these work on core 7 or 8??..
- FO 07:39 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- I checked the touch tablet, confirmed not working on the new board. Very odd since this worked on v1 and paddles are working, except the bad mapping! Will investigate...
- FO 07:36 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- ", then I will check the touch tablet"
- FO 07:36 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- Yeah I mixed them up.
We swapped joystick ports 0/1 and 2/3 on the silkscreen. I made the same changes in the core... except its different for paddles since we'd only really swapped port 0 and 1!
I'm building with the order correct... - SA 07:30 PM Bug #47: CORE 13 - Paddle, Touchtablet issues
- To one point I don't remember till which firmware version, these work well. Maybe Mark later confuse something in Core?
- ND 05:47 PM Bug #47 (Closed): CORE 13 - Paddle, Touchtablet issues
- Touch Tablet not working
Paddles buttons and Knobs are not correlate for the same Paddle
- ND 09:13 PM Bug #45: CORE10 - IDE2+ SDX not working
- testing IDE2+ on an ULTIMATE 1MB does not behave correctly as well
- FO 09:08 PM Bug #45: CORE10 - IDE2+ SDX not working
- Does the IDE2+ work in those modes on a real system? I mean on a standard version of those upgrades, not one of these new ones that latches portb bits..
- ST 08:53 PM Bug #45: CORE10 - IDE2+ SDX not working
- Stephen wrote:
> In CORE10, when I boot with the IDE2+ installed, the machine initially goes right into self test mode. Pressing reset will take me to a BASIC prompt with "ERROR 12 at Line 0" and typing LIST gives me the repeating 0s f... - ND 05:44 PM Bug #45: CORE10 - IDE2+ SDX not working
- Tested and working on core 13
Nir - FO 08:48 PM Bug #25: F10 Hard Reset Ignore inserted cartridge (Core v7)
- This is still on the list, but not yet in place...
- ND 05:45 PM Bug #43: Core 10 - IDE2+ Menu does not show when powering the computer with START key pressed
- Tested and working on Core 13, need other guys to test on MIO and BlackBox
Nir - FO 12:11 PM Bug #43: Core 10 - IDE2+ Menu does not show when powering the computer with START key pressed
- More info from Simus:
$D800..$DDFF is a ROM, $DE00...$DFFF is a RAM.
MPD is kept low all the time when apropriated bit in PDVREG ($D1FF) is set. EXTSEL is pulled down 40-50ns after one of two conditions occured:
1. MPD is low and a... - ND 03:09 PM Bug #34 (Closed): Problem booting with Core 9
- this happen on every core after flashing, to solve it i simply remove and put back the SD Card and it works
- ND 03:07 PM Bug #44 (Closed): CORE 11 - Bug in PBI - EclaireXL will not boot with IDE2+ Is connected and when Turbo Freezer connected goes directly to Cart EMU not main screen
- Checked IDE2+ On core 13 and i works!
case closed - FO 02:09 PM Bug #44: CORE 11 - Bug in PBI - EclaireXL will not boot with IDE2+ Is connected and when Turbo Freezer connected goes directly to Cart EMU not main screen
- Even on v13 it goes straight to the cart emu menu. My turbo freezer goes straight to the cart emu menu on my 600xl though, so it seems normal... I think that didn't happen on older cores because my reset was broken.
- FO 01:54 PM Bug #44: CORE 11 - Bug in PBI - EclaireXL will not boot with IDE2+ Is connected and when Turbo Freezer connected goes directly to Cart EMU not main screen
- Found a bug I introduced here. When MPD_N is low I was also disabling the rest of the OS rom... Ooops! IDE2+ holds it low, hence the failure to boot. Fixing in core 13.
- ND 03:07 PM Bug #46 (Closed): CORE 10 - VOICE BOX does not work with Eclaire board
- solved in CORE 13
- FO 01:53 PM Bug #46: CORE 10 - VOICE BOX does not work with Eclaire board
- I've wired this up in core 13, but I need to checking the timing is correct on the logic analyzer.
- SA 11:30 AM Bug #46: CORE 10 - VOICE BOX does not work with Eclaire board
- Pin 12 of SIO connector is used only by ancient Atari's 400 and 800 as a 12v dc supply. On eclaire XL is unconnected.
- FO 10:01 AM Bug #46: CORE 10 - VOICE BOX does not work with Eclaire board
- I guess you mean pin11? I think you confirmedthis works, but is quiet?
The problem is I think that this uses sio clock out and the implementation is incomplete.Will check...
06/10/2017
- SA 11:43 PM Document: Main Board Interface 1 & 2 Pin-outs - v3 prototype
- ND 01:45 PM Bug #46 (Closed): CORE 10 - VOICE BOX does not work with Eclaire board
- i tested my Voice Box on a real Atari and on the Eclaire board and on the Eclair it does not work!
to run the VoiceBox you need to VoiceBox hardware connected to the SIO Port.
i belive that the VoiceBox output its Audio through PIN 1...
06/09/2017
- ST 11:40 PM Bug #43: Core 10 - IDE2+ Menu does not show when powering the computer with START key pressed
- ndary wrote:
> can you confirm that you get to the MIO Menu?
> ...
After dinner I will find a power supply for the MIO. First I have to confirm it works on real hardware, and then yes, I will let you guys know if it works with CORE11 ... - ND 09:45 PM Bug #43: Core 10 - IDE2+ Menu does not show when powering the computer with START key pressed
- can you confirm that you get to the MIO Menu?
Nir - ST 09:38 PM Bug #43: Core 10 - IDE2+ Menu does not show when powering the computer with START key pressed
- ndary wrote:
> i found this document.. can it be missing voltage on the PBI port?
> ...
Nir, I do have a 256kB MIO. Two issues. First I don't know if it works, as I don't believe I've ever even turned it on since I bought it. Second... - FO 08:23 PM Bug #43: Core 10 - IDE2+ Menu does not show when powering the computer with START key pressed
- IDEPlus info from Simius:
IDE+ detaches OS ROM between $D800 and $DFFF and plug his own memory there. I uses also $D1xx page and $A000...$BFFF area for SDX
IDE+ uses all PBI signals, except: RAS, CAS, RDY, REF, EXTENB and AUDIO
IDE+ l... - FO 09:59 PM Bug #44: CORE 11 - Bug in PBI - EclaireXL will not boot with IDE2+ Is connected and when Turbo Freezer connected goes directly to Cart EMU not main screen
- Though that logic should only get hit after it stabilises... Hmmm. Well registering it anyway (grasping at straws!!)
- FO 09:46 PM Bug #44: CORE 11 - Bug in PBI - EclaireXL will not boot with IDE2+ Is connected and when Turbo Freezer connected goes directly to Cart EMU not main screen
- I think I know why it won't boot with v11.
MPD_N is combinatorial logic driven from the address - and I use it too soon. - ST 09:26 PM Bug #44: CORE 11 - Bug in PBI - EclaireXL will not boot with IDE2+ Is connected and when Turbo Freezer connected goes directly to Cart EMU not main screen
- I am also confirming that with Core 11, the exlaire will not boot with IDE2+ Rev C. A video signal is generated as my monitor picks up the 50Hz signal via HDMI, but when pressing F12 no text is visible.
- FO 07:10 AM Bug #44: CORE 11 - Bug in PBI - EclaireXL will not boot with IDE2+ Is connected and when Turbo Freezer connected goes directly to Cart EMU not main screen
- I see the cart emu thing, I had not tested that... I had it disabled. Interesting, will check the manual for when that fires up, might give me a clue.
- FO 09:59 PM Feature #2: PBI support
- Turn on data write to bus earlier, for things that snap it early (like IDE2+).
Register MPD_N before feeding to the address decoder and disable it when disabled. - ST 09:29 PM Bug #45 (Closed): CORE10 - IDE2+ SDX not working
- In CORE10, when I boot with the IDE2+ installed, the machine initially goes right into self test mode. Pressing reset will take me to a BASIC prompt with "ERROR 12 at Line 0" and typing LIST gives me the repeating 0s forever.
I can p...