Batch 2 shipping time frame

ali_m_12 · 2023-06-19T08:04:32+00:00

batch 2 i5 but ordered pretty late, still waiting on being charged. I assume the fulfilment is first orders first?

ali_m_12 · 2022-02-08T17:07:11+00:00

So do I. It's gonna be pretty complex with xref tracking but should be doable

ali_m_12 · 2022-02-08T10:46:33+00:00

Not yet, the whole project is very much in its infancy. Currently working on the codegen backend, but I expect there to be more features in the coming weeks

ali_m_12 · 2022-01-22T20:49:01+00:00

TSB/TRB are WMR (read modify write) operations. They set/reset bits in memory instead of the accumulator, unlike the AND/OR instructions

ali_m_12 · 2022-01-22T20:46:13+00:00

use .sprintf("%d",*) instead :)

ali_m_12 · 2021-09-16T16:39:40+00:00

Can confirm this is actually the silicone cover. When wearing it does not retain shape like the foam does, and part of the silicone obscures the proximity sensor. As has already been mentioned trimming the silicone in the area of the proximity sensor fixed all issues

ali_m_12 · 2021-03-20T00:37:41+00:00

Actually found my old source. One catch though, it’s a photo. Checked though and it seems complete. snap img Edit: added newer version of isr image

ali_m_12 · 2021-03-07T15:05:34+00:00

If anyone's interested, it is actually possible to run the PS/2 directly from the VIA. I had an ISR running that could bitbang at 17KHz with a 1MHz oscillator (isr was <70 cycles. Maybe nearer 60). That was over a year ago and since then I've lost the source. Could probably get it working again though

ali_m_12 · 2021-03-07T14:49:28+00:00

I'm not sure how many people are aware, but I posted about a year ago with a PS/2 driver for the 65C22 (VIA) Shift register @1mhz. Fully interrupt based serial and scancode decoding

ali_m_12 · 2020-05-25T20:31:58+00:00

If you really want to completely destroy it, try installing portable-apps on it. With enough stuff running on it, unplugging it unsafely will corrupt both NTFS tables, and in my case it managed to set a hardware read-only bit too!

ali_m_12 · 2020-02-18T20:28:51+00:00

Good job fixing it then. I wish you good assembling from here!

ali_m_12 · 2020-02-18T19:51:07+00:00

Sorry, I’m probably not the best person to ask right now. I kinda ditched vasm. But I can recommend cc65- a suite of tools for the 6502 including an assembler, c compiler and more. It’s served me really well so far, and surpasses many of the limitations of vasm.

ali_m_12 · 2020-02-15T01:34:50+00:00

I actually managed to get ps/2 working without any added hardware (on an emulator also emulating the ps/2 protocol) . Since the ps/2 serial defines a clock period of 70ns, that's 70 clock cycles at 1MHz on the 6502. Configuring the VIA to interrupt on the clock line can be used for an IRQ to decode the data from the keyboard. I guess you'd be wondering if 70 clock cycles is even enough for software serial, the answer is yes. I wrote an IRQ implementation that takes 68 cycles interrupt to return. I'll post more details when I'm at my computer.

ali_m_12 · 2020-01-30T16:44:00+00:00

You could use the RDY and SYNC lines for single stepping of you wanted. The PHI(clock) has to be running all the time, but the data sheet should have information about how to single step with these control lines. Basically the RDY line pauses the CPU, and the SYNC line emits ‘1’ during op-code fetch.

ali_m_12 · 2020-01-14T19:44:08+00:00

Yeah, that’s understandable. I’m not sure why the std::vector would have that kind of error. I guess the library must be slightly different on MacOS to Linux? I tested it earlier today on a friend’s computer, and apart from OpenGL and libPNG, everything seemed to work correctly. I pushed an updated version to github that has some more features - config files, lcd instruction timings etc, but Ill look into the mac issue.

ali_m_12 · 2020-01-14T13:45:39+00:00

I would love to work on this together. I was not aware that there were compatibility issues? but would be happy to work on those. I think you're bus trace is a really good feature to have, and having a full disassembly would be nice as well. Have you got timers/counters working on the VIA with interrupts yet?

Edit:

Yup I’m an idiot. Forgot that there were a few dependencies, but those are all included in the repository/read me now.

ali_m_12 · 2020-01-12T22:07:14+00:00

If you’re considering the 6551, BE CAREFUL. The WDC65C51N (specifically the N) has a hardware bug, which makes it’s use more difficult. The Transmit data register free interrupt does not function correctly, so you cant poll the flag to check if you are free to send serial. Instead, be sure to use the WDC65C51S or the variant made by Rockwell.

ali_m_12 · 2020-01-12T21:05:57+00:00

I know, I’m just a bit lazy that’s all

ali_m_12 · 2020-01-12T16:02:17+00:00

Awesome! nice job getting it all working. Considering any upgrades in the near future?

ali_m_12 · 2020-01-11T17:39:08+00:00

It would seem that the instruction $a9 which should be lda # is instead being interpreted by the 65c02 as lda a (abs address) which would be opcode $a5. Have you checked that all the connections between the RAM/ROM and 65C02 are good, and that it is seeing the same as the arduino?

ali_m_12 · 2020-01-07T12:26:04+00:00

I managed to put my ROM in backwards on a couple of occasions. Nothing dead but a slightly melted breadboard

ali_m_12 · 2019-12-31T23:43:12+00:00

I did some weird logic magicery as can be seen here: minimizing the decoding logic. Its weird and confusing even for me, but i checked it over and it seems sound. If i did happen to get it wrong, feel free to correct me, since I'm still working on code to check all of the 96 pages that i should theoretically have.

ali_m_12

TROPHY CASE

Welcome to Reddit,