Jump to content

jyeandle

6502
  • Content Count

    16
  • Joined

  • Last visited

Profile Information

  • Location
    Indiana
  1. The integration of the protocol was done with the idea of having there be a menu a la windows 10 that lists networks and allows the user to connect and disconnect from different networks, and updates on the fly when opened with a list of available networks. It also allows the esp to periodically send updates to the mac on signal strength, which changes the menu icon to reflect, and do so while continuing to send ip packets to the mac over the same lines. It doesn't need to be that way to work, but I thought it would be a fun challenge. Eventually I hope to circle back to finish the interface.
  2. I started working on a similar device that connects to the external serial port a few years back, before life got in the way and I had to focus on other things. I modified the esp slip firmware to add escape sequences to the slip protocol that allow me to set up and control the wifi network connection through the slip interface. Worked well. Where I got bogged down was on the mac software end. Using a serial terminal I could poke out values to set up and start the wifi connection, then connect via the InterSlip driver, and it works just fine. But writing my own slip driver to combine the wifi
  3. I somehow had missed GetDCtlEntry, though I did figure out another solution that works. I just put the ParamBlockRec that I passed to the PBread as the first listing in the struct that is the dCtlStorage field. So, the pointer that gets passed to the completion routine for the ParamBlockRec is the same address as dCtlStorage, and only needs to be typecast to my storage struct to give me full access to the data I want.
  4. Rewrote my code to use a VBL task instead of a Timer Task, and now it's not hanging on every read from the serial port. But, next question: Is there an elegeant way to pass a pointer to a completion routine? According to Inside Macintosh, a completion routine gets called with the ioResult in D0, and a pointer to the ParamBlockRec in A0. All well and good. But I'd like to access a different structure full of driver specific variables. Should I use a global variable, or is there some slick way to pass an additional pointer that I'm not thinking of?
  5. New to Mac programming, although I have a lot of C experience in windows/linux/embedded system environments. I'm using Codewarrior 8 to write a driver in C on the mac. And I'm looking for resources on programming drivers for the mac (targeting system 7). I'm building a serial to wifi adapter based on the esp8266. The communication between the mac and the adapter is based on a modified slip protocol, using unused slip escape sequences to handle wifi setup/connection/etc. I have the firmware on the esp written and working correctly, and it's usable on the mac using a simple program I wrote that
  6. Reopening this thread, I apologize if that's an etiquette faux pas... Back in 2001 I had a summer job working in the salvage and excess warehouse at Lawrence Berkeley National Lab, and because I was the only tech savvy person in the building, I ended up being the person who refurbished computers for internal redeployment. The lab had been a primarily Mac based institution from 1984 through the late 90s, so I saw lots of various models (some of which I got to keep, or buy off the government super cheap [under $5, usually] which was a perk). The one catch was the hard drives. This was shortly af
  7. I actually kind of like the idea of using an IC that's meant to deal with this problem. Poked around and stumbled across the datasheet for the MAX809JTRG. It's a 3 pin IC like you mentioned, with a 4v trigger threshold. So I could connected its Vin as is to pin 7 on the sound IC, which is normally at 5v and drops to 3.84 when the button is pressed, which is below the threshold for it to pulse the reset output, which I can connect to the RESET line. Should work, unless I'm completely wrong about how the IC operates. Didn't get a chance to swap the SWIM chip out today, or deal with the machin
  8. As I said a few posts above, retracing what I had done I realized after the fact that I brainfarted and connected one probe to +12 and the other to a logic pin, likely one of the phase lines, though I'm not sure which one. So, I'm figuring most likely the swim is dead as a result. And hoping it's ONLY the swim is dead as a result. I do have one I can swap over, though I'm waiting on some chipquik to arrive tomorrow to do that. So is UA5 responsible for toggling the line low/high? I know it does when the reset button is pressed, but does it also do that on power up? It had been working fine
  9. Hmmm... Upon plugging it back in and turning it on today, I'm back to a checkerboard. Only, this time it's not being caused by the CPU reset line... Anyone know of where I can get a new logic board without having to buy (and ship) a whole new classic off ebay? Working would be preferred, but even if it doesn't, at this point I'm not above chip swapping until I have a working board.
  10. Its not the clearest of pictures, sorry. Drew an arrow pointing to pin 6. Although it's hard to tell from this angle, it is cut. There's no contact between the pin and the board.
  11. Bleh. I know what happened... I flipped the connector in my head, put the negative probe of the multimeter on +12 rather than ground, and the positive probe on 5v... Hence why the multimeter gave me a reading of -7. And why I smelled a chip dying... Hopefully I haven't killed the entire board. I do have a spare logic board that was a victim of battery explosion, which someone removed the BBU from. And the 68000 on it, along with the VIA, RTC, and sound IC, are all corroded and probably unusable. But, I can harvest the RAM, SWIM, SCSI, and SCC and swap those onto the now formerly working board
  12. Scratch that... Back to not working. While trying to diagnose the lack of working floppy, I was probing signals at the floppy connector to verify voltages. They were reading funky, as in -7.4, -10.2, etc. Then I started smelling what smelled like a cap shorting out, the screen froze, and upon power cycle, new video fun...
  13. Got tired of trying to figure it out. Cut pin 6 on the sound IC. Boots right up. Everything works except the reset button on the side. Even selecting restart from the special menu works. Also, sound still works. Only thing not working at this point is the floppy drive. I have two drives, and neither of them worked. But, new problems for a new day. For now I'll just be content with the fact that it once again boots.
  14. Any elegant way to pull up UA5? I havent quite worked my soldering chops up to the level of cleanly removing surface mount ICs, and I don't have access to any reflow equipment. It's not seated flush to the board, so I was able to floss around an alcohol wipe underneath to some extent through the gaps in the pins around the corners. If it can be done, I have no objections to pulling it up to clean, but I don't want to risk destroying it in the process. R73 is measuring 0.98k on the board. The right side of the resistor is at 5V, the left is reading 91.6mV. R93 is measuring in at
  15. Any idea what the source was? I quickly skimmed a few of his books that I could find in pdf online and and saw nothing about sounds ICs in any of them.
×
×
  • Create New...