Don't want anything bought from jahota-0 on eBay

I would assume it refers to pandrew's controller. I use one with a 5251 (although I didn't know he made one for the Displaywriter)
Amazing, frankly, the work people have done in mangling the firmware to fit on the damn thing. But since when was this the 1970s when 1k was a sensible amount of ram?NathanA wrote: 19 Oct 2021, 23:12 I've continued to play around with Vial-enabled builds, trying to find a combination of features that will run stable without disabling/sacrificing too many of them.
At this point, I'm guessing there is either some kind of RAM-contention issue or RAM space violation issue (one part of QMK scribbling over memory space belonging to another part). ATmega32U2 only has 1KiB of SRAM according to the spec sheet, and I have to believe that this microprocessor doesn't have any memory protection features, so neither would surprise me.
32u2 is a bad chip. Xwhatsit was a smart fella and it likely made a lot of sense back when he started out on his beamspring project, but the years have flown by since, with new silicon aplenty and software stacks like Vial he couldn’t have anticipated. Now 32u2 is in very short supply as well, thanks to the worldwide production shortage on legacy nodes. A true, new controller would dump that crap and go Arm or the like, and open up the software possibilities while also being cheaper and quicker to source!NathanA wrote: 20 Oct 2021, 22:54 from a brief glance there don't appear to be many keyboards that fit this bill. The 32U2 appears to be popular when it comes to macropads and the like, but not so much on full-blown keyboards (likely due to fewer GPIO lines compared to other MCUs).
since you clearly know better than everyone when it comes to this, i want you to explain your thinking behind both of these statements, and also choose and justify a better chip.Muirium wrote: 15 Jul 2022, 22:03 32u2 is a bad chip. A true, new controller would dump that crap and go Arm or the like, and open up the software possibilities while also being cheaper and quicker to source!
Well, all I'm reading is "credit where credit is due".
Thanks!
you're dodging my question lol. if you have no clue why the 32u2 was used for a new design then don't act like you know betterMuirium wrote: 16 Jul 2022, 10:04 Exactly. Credit is due to Pandrew, all the contributors to QMK, and to Xwhatsit. We’re all using derivatives of his work, for better and for worse: namely the 32u2 at the heart of it.
Thanks!![]()
Read NathanA’s struggles with that miserable chip on Ellipse’s thread. A lot of good hacking has been done just to make it work with Vial at all. Why? Because it’s still all we have.![]()
Anyway, Xwhatsit is an old friend so I don’t like seeing other people take his credit. The new guys who actually do the work of remodelling his design always name him in their documentation. We should respect their wish. Until someone designs a controller with more than 1024 bytes of ram, it’s still Xwhatsit’s little baby!kbdfr wrote: 17 May 2020, 08:43You may not know yet, but this is offtopicthority, where derainling threads is quite normal while fulling the spy with bumps is a nuisance.jsahmiens wrote: 16 May 2020, 22:57 holy shit guys, can you all stop trying to win this pointlessly long argument already? especially on other people's posts, there is no need to pollute all of deskthority.
pandrew wrote: 13 Sep 2020, 03:54 This design is based on the TH Xwhatsit ( viewtopic.php?t=23406 )
...
Displaywriter/Beamship are currently only supported by the TH.
Oh that's cool.Weezer wrote: 19 Jul 2022, 19:34 With the Displaywriter you have the use the Model F controller because of the PCB matrixes. Orihalcon did a post on it some years back.
QMK uses different firmware and is a different implementation than xwhatsit so they're not 1 to 1. I think Muirium was just commenting that they had the same EEPROM chip. I went and dug up Orihalcon's thread for everyone where the necessary pinout for xwhatsit is outlined. viewtopic.php?t=16469mmm wrote: 19 Jul 2022, 20:02Oh that's cool.Weezer wrote: 19 Jul 2022, 19:34 With the Displaywriter you have the use the Model F controller because of the PCB matrixes. Orihalcon did a post on it some years back.
The thread mentioned, also linking to firmware
The SMD version of the Model F controller. I'm guessing this should also work? The price for 5 of these were around 60 USD on JLCpcb a month ago (not including pro micros).
The pandrew version of QMK also has a configuration for a Displaywriter, not sure whether it's the Model F or Beamer edition, or if these happen to share configuration/matrixes.
Yes that's the thread I linked to!Weezer wrote: 19 Jul 2022, 22:25 QMK uses different firmware and is a different implementation than xwhatsit so they're not 1 to 1. I think Muirium was just commenting that they had the same EEPROM chip. I went and dug up Orihalcon's thread for everyone where the necessary pinout for xwhatsit is outlined. viewtopic.php?t=16469
I'm sorry you are being a bit vague about what about what you are looking for, and seemingly getting angry when people are trying to ask clarifying questions. I understand that some of the developments in the thread is off-topic, but you are not really helping yourself.headphone_jack wrote: 19 Jul 2022, 23:36 Only the TH version of the Andrei controller is displaywriter compatible, I tested the SMD one and it certainly does not work. The F model doesn't have the right hardware for the displaywriter matrix. I just need a displaywriter-compatible controller, I only specified Andrei because I *thought* that was the accepted standard these days. Apparently some people are still stuck debating over almost 7 year old semantics though.