Jump to content

acadiel

+AtariAge Subscriber
  • Content Count

    2,108
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by acadiel


  1. 13 hours ago, Vorticon said:

    I really need to bite the bullet and go for my ham license. I've been considering this for 3 decades! I even bought the AARL book from Radio Shack and still have it :lolblue: Probably long outdated. I did do some RTTY receiving using the C128 at some point.

    Free review of all the question pool:  http://arrlexamreview.appspot.com/

    (Seriously, this is the ones they actually use...)

    • Like 1

  2. Should be able to check the voltages at the regulator with it plugged in - make sure you're getting Vout at 5V.  I know there's precious few other components, but he has them all globbed/soldered on top of each other.  Troubleshooting is working out which one is causing the bus contention that is keeping the system from powering on.  

     


  3. 12 hours ago, dhe said:

    Come on ArcadeShopper - I'm thinking commercial product here! 😃

    If Greg gets a nice 3d printed adapter going that will allow the DIN to fit in the back power space, he can easlily build those adapter cables.  We just need to be completely clear about verifying pinout on them with what's in the console between the regular and QI motherboard revs.  

     

    We could also make a dummy PCB with a switch and a triple pole relay in lieu of the adapter (so that the TI power switch could continue to be used)  - I'm pretty confident the relay would allow everything to power on simultaneously, but I haven't done any testing.  I need to find a lower profile triple pole relay first that can handle the current of up to 1.2A.

     

    Plug----------->PSU------------->|[Female DIN]----------4pin_board_with switch_and_relay<--------console_psu_connector

     

    • Like 2

  4. For those of you who want to know where I got the internal PSU specs... the RS Archer 277-1016 has them on the back.  (Remember when Radio Shack sold excess keyboards and power supplies?)

     

    And also, if anyone is looking for the internal power supply male and female connectors - here ya go.  I remember Tursi had a keyboard adapter that tapped into the internal PSU at one time and there was an issue at the time identifying what worked.

     

    archerPSU.jpg

    40C89EBB-12DC-4BDC-B4E5-3AFA64A64F7C.jpeg

    • Like 1

  5. 5 hours ago, helocast said:

    I'm pretty sure this is what I based mine off of (your 2015/2016 post perhaps?). Good stuff and nice project!

     

    I would just caution anybody that doesn't know their way around a multimeter before modding, that I've found several QI motherboards

    that don't have their voltages marked correctly. Don't ask me how I know that 💣 ... it only took finding the first one!

    Never found any original motherboards marked incorrectly and that's the majority just about everybody has/comes across.

    Now, it isn't a big deal with TI factory power supplies, because they obviously knew and just pinned the molex correctly to compensate.

    So, like some errors on the schematics, don't necessarily believe what your eyes are telling you.

     

    Doug

    QApowertap.JPG

    Agreed - mine wasn't marked, so I actually found the ground rail (easy enough) and then measured the voltages on the other pins.  And then numbered both the motherboard and the female molex connector with 1-4 so I could write a small table with which pin was what. When, I coordinated with the five pins on the DIN connector and voila... 


  6. 1 hour ago, matthew180 said:

    The correct voltage are only part of the requirements.  You also have to consider the current for each voltage, and overall power capability.  Looking at the photo of the Meanwell PS you are using, it is probably equal or greater than the 99/4A PS, but you should still know the capability of the PS you are replacing.

     

    And to that point, do we know the 99/4A's PS specifications?  I took a quick look at the linear PS schematic that is part of the 99/4A schematic set, and it looks like the -5V is 500mA, the +5V is 1A, and the +12V is 1.2A.  I also think the linear supply was replaced with a switcher at some point?

     

    Edit:

    The Meanwell PS looks a little low on the +12V and -5V current capability compared to the original 99/4A PS.  But it has +5V current to spare.

     

    From what I have measured in the past, the TI drew nowhere near the max current on the native PSU and nowhere near the max capacity of any of the three Meanwell voltages.  It’s been a while, though, since I measured.  I was running with speech, F18, and an Ubergrom running.

     

    IMHO, TI over-engineered the linear and switching PSUs.  
     

    edit; here ya go:

     

    0941DF80-E2F2-4BC9-912E-AFFF277402BE.jpeg

    • Like 1

  7. I had done this a while back - I wanted to replace the brick and internal power supply with a single piece unit.  I found a Meanwell power supply (pictured below) that had all the voltages the console needed - three of them.  At first, I had soldered a DIN connector directly to the underside of the console, but I went ahead this week and took that out and made a proper adapter. 

     

    I have pictures of everything color coded and numbered.  The Meanwell power supply has five pins - two are ground, three are the voltages.  I tied the grounds together in the adapter.  To make the adapter, you simply need a female DIN5 connector, some nice gauge wire, and a Molex .156 KK Male header (I used Molex part number WMLX-229 - 4 pin, .156 header 3.96mm).  I put heat shrink around the connectors on one end (I probably should have done both - I just taped the DIN end.)  I simply connected the adapter, routed the DIN connector through the console, and voila.  The internal power switch doesn't function any longer, but you can always add an IEC in line on/off switch.  I think the new power supply is a Meanwell GP25A13A-R1B.  Mine was an older P25A13A-R1B.

     

    If someone wants to create a 3D Printed adapter for the DIN5 to fit in the square former power mount in the back of the console, it would make it detachable - I just have not done so.    

     

    Anyway, enjoy.

    IMG_6624.jpg

    IMG_6623.JPG

    IMG_6622.JPG

    IMG_6621.JPG

    IMG_6629.jpg

    IMG_6627.JPG

    IMG_6626.jpg

    • Like 5

  8. 3 hours ago, InsaneMultitasker said:

    If I updated MidiMaster for use with the Ubergrom UART I have no recollection of doing so, though it is on my wishful thinking list. You might be remembering the modification for nanopeb serial port compatibility?

     

    I know someone did in here.... I’ll have to do a power search ;)

     


  9. 5 hours ago, Tursi said:

    You misremember my concerns slightly. I disabled the UberGROM overriding the console GROMs because the MPD will use the same tech, and then you'll have two TTL devices (one in the console, one in the cartridge port) both driving the bus at the same time if you try to overload the console GROMs. That /will/ damage one or the other. 

     

    Gotcha, thanks for the correction!  


  10. 14 minutes ago, OLD CS1 said:

    My guess is something in the audio path to the jack in the recorder itself if all else is checking out.  Is this your only recorder?

     

    Greg posted the schematics a while back but I do not have them handy.

    I've tried multiple recorders and multiple cassette cables - so have eliminated everything but the console.

    • Sad 1

  11. I am having issues with my current main console (which I never used a cassette with) where the input into the /4A from the cassette recorder is very low (the white ear jack).  I'm using the standard cassette cable (mic, ear, and remote), and the deck works fine with other consoles.

     

    The Output from the /4A is fine.  I can play the tape back (after yanking the ear cable) and it plays fine on the recorder.  Just that it is barely audible going into the /4A.  I've reflowed and checked all the pins on the DB9 connector.  I'm assuming this is a transitor, cap or other component that might be having an issue.  Anyone have any ideas?

     


  12. 13 hours ago, INVISIBLE said:

     

    Nice to see this thread bearing some fruit!

    I'm one of the developers of the UG - Tursi, Ksarul and myself.  There were a lot of thoughts bandied around about what we could do with these features after Tursi implemented all these ATMega functions.  The original was expansion terminal program showing Linux running via the attached serial port (demo'd at the TI Faire).  Tursi also had plans for the UG to support his Multiple Personality Distorter (which lets you run a /4 GROM on the /4A), but had concerns about TTL overdriving and hurting the GROMs in the console.  IMHO, the GK, Gromulator, and other devices did that without issue by "shouting" over the TI GROMs and didn't seem to hurt anything.

     

    Kudos to Fred Kaal for coming up with the first good idea for the expansion pins:  http://www.ti99-geek.nl/Projects/ti99hdx/ti99hdx_ubergrom.html - others have followed the serial port lead, and I've even experimented with XBee, Bluetooth and other things using TTL serial.  :)  I believe someone also tried a MIDI program over the serial port (InsaneMultitasker?)

    • Like 7

  13. 74LS139N Pinout
    
    Pin		Connected to				Function	Notes
    1		Cut off from CRUCLKB (origin)		Ea		Hooked before the CF40058 chip to what was supposed to go to pin #20 (CRUCLKB)
    2		139 Pin 14 (H)				A0a		Forced high by Vcc
    3		139 Pin 15				A1a		S0 Keyboard Scan (CF40058 pin 18) via Pin15 on the '139
    4		n/c
    5		CF40058 #20	CRUCLKB			O1a		Hooked to CF40058 CRUCLKB (Pin #20)
    6		n/c
    7		4B 2564 EPROM #22 /CE			03a		Turns EPROM 4B on or off
    8		n/c
    9		Cut off from S0 keybd scan (origin)	03b		Hooked before the CF40058 chip to what was supposed to go to pin #18 (KEYBD S0)
    10		n/c
    11		n/c
    12		n/c
    13		n/c
    14		139 Pin 16 (H)				A0b		Forced high by Vcc
    15		CF40058 #18 KEYBD S0			Eb		Hooked to CF40058 S0 Keyboard Scan (pin #18)
    16		Vcc (H)					Vcc		Vcc
    
    Notes:  A0a, A0b are high because they are hooked to VCC.  A1a and Eb are hooked together for state.
    
    Truth Table (A0 being low taken out):
    -------------------------------------
    Inputs				Outputs
    Ea	A0	A1		O1	O3
    H	X	X		H	H	
    L	H	L		L	H
    L	H	H		H	L
    

     

    Above is the pinout of a dead bug (seen here and other places:  http://www.ti99.eu/?attachment_id=3164 and http://www.ti99.eu/?attachment_id=3165 and http://www.ti99.eu/?attachment_id=3166 and here https://atariage.com/forums/uploads/monthly_2020_03/IMG-1044.JPG.3788dcca167e2aec344af26576fd2c38.JPG) that is attached to different pins on the 99/2 - with, I believe, the express purpose of turning pin #22 off on EPROM #4B to do bank switching in the >4000 address space.

     

    Those with a 99/2 - can you please verify this pinout?  

     

    Those who can - can you figure out what's going on here logic-wise?  The Keyboard Scan S0 and CRUCLKB pins were cut - they originally went directly through to the KEYBD S0 and CRUCLKB pins on the I/O controller.  Now, they're being diverted through this 74LS139, which only had 9 pins connected:

    - Three pins were what was originally going to pins #18 and #20 on the CF40058 I/O controller

    - Two pins going from pins #18 and #20 on the CF40058 I/O controller TO the 74LS139

    - One pin going to Vcc

    - One pin going to the CE pin (22) of the 2564 4B EPROM, to turn it on/off

    - Two pins forced high (A0a and A0b) on the two sides of the 74LS139 to probably impact the truth table

     

    I'd love to see an explanation of this - would explain how the 99/2 did bank switching.


  14. Different audiences, different capabilities.

     

    • I've been making UberGROM images of all the proto GROM carts.  That way, people can make single use dedicated carts - like the three Disney games, Plant Genetics, Germ Patrol, etc.
    • Dedicated games like Breakthrough that used GROM are also an ideal dedicated use for an UberGROM
    • UART: UberHDX from Fred - with a serial dongle, or a Bluetooth radio (which I use to talk to my laptop via a Bluetooth COM port)
    • Unused capabilities:
      • GROM bases (in 8K banks, supports 16 access bases)
      • RAM - 15K (8K and 7K)
      • EEPROM - 4K
      • GPIO - 4 pins
      • Analog to Digital Converter - 4 pins

    - So yeah, we're thining of using the GRAM part for the BASIC Support Module... so add that one to the list of "cool new use of an UberGROM."

    - The GPIO is just waiting for someone like Vorticon to measure/test/do something with general purpose pins

    - The ADC is just waiting for an analog to digital converter use case - like an analog joystick

     

    There's tons of cool uses that we haven't even thought about with this cart yet.  We've just scratched the surface with UberHDX (and TIMXT - kinda works) with the DB9 serial and Bluetooth serial.

     


     

     

    • Like 3

  15. 27 minutes ago, brain said:

    The cc40 is emulated, I thought.  That would give video controller data

     

    Jim

    I think wierd_w is talking about this.

     

    I know of only one person that has this.  The other one was sold on eBay a few years ago when Michael Becker emptied his magic basement.  Ksarul or Atrax likely knows who purchased it - the purchaser has been silent and never came forward.

     

     

     

    videoback.jpeg

    videofront.jpeg

    • Like 1

  16. 17 minutes ago, brain said:

    Sounds like some debugging is in order.  I can put my kit together again, but it'll be a few days.  If the arduino uses the USB as a serial port (I think it does), then you might be able to use the built into UART code in the prj to sniff out what is going on when the save is requested.  BAV should go low, as I recall, and HSK should then almost immedaitely go low to ack the request.  It sounds like that is not happening.

     

    Jim

     

    No worries about timing.. this has been something on my workbench for a while. 

     

    The compile looks ok:

     

    [email protected] MINGW64 /d/dev/HEXTIr-master
    $ ./make.exe CONFIG=config-arduino
      MKDIR  obj-m328p-arduino/src/
      CONF2H config-arduino
      CC     src/diskio.c
      CC     src/ff.c
      CC     src/hexbus.c
      CC     src/led.c
      CC     src/main.c
      CC     src/sdcard.c
      CC     src/spi.c
      CC     src/timer.c
      CC     src/uart.c
      CPP    config.h
      AS     src/crc7asm.S
      LINK   obj-m328p-arduino/HEXTIr.elf
      BIN    obj-m328p-arduino/HEXTIr.bin
      HEX    obj-m328p-arduino/HEXTIr.hex
      SIZE   obj-m328p-arduino/HEXTIr.elf
    obj-m328p-arduino/HEXTIr.elf  :
    section                      size      addr
    .data                          14   8388864
    .text                       12344         0
    .bss                          878   8388878
    .stab                         204         0
    .stabstr                       58         0
    .comment                       17         0
    .note.gnu.avr.deviceinfo       64         0
    Total                      101941
    

    I looked at the debug statement for the Arduino for when it programs, and just tried programming it with the same syntax (I did this one on the Windows command line):

     

    "C:\Program Files (x86)\Arduino\hardware\tools\avr/bin/avrdude" -C"C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf" -v -patmega328p -carduino -PCOM4 -b115200 -D -Uflash:w:D:\dev\HEXTIr.hex:i

    
    avrdude: Version 6.3-20190619
             Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
             Copyright (c) 2007-2014 Joerg Wunsch
    
             System wide configuration file is "C:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf"
    
             Using Port                    : COM4
             Using Programmer              : arduino
             Overriding Baud Rate          : 115200
             AVR Part                      : ATmega328P
             Chip Erase delay              : 9000 us
             PAGEL                         : PD7
             BS2                           : PC2
             RESET disposition             : dedicated
             RETRY pulse                   : SCK
             serial program mode           : yes
             parallel program mode         : yes
             Timeout                       : 200
             StabDelay                     : 100
             CmdexeDelay                   : 25
             SyncLoops                     : 32
             ByteDelay                     : 0
             PollIndex                     : 3
             PollValue                     : 0x53
             Memory Detail                 :
    
                                      Block Poll               Page                       Polled
               Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
               ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
               eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
               flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
               lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
               hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
               efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
               lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
               calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
               signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
    
             Programmer Type : Arduino
             Description     : Arduino
             Hardware Version: 3
             Firmware Version: 4.4
             Vtarget         : 0.3 V
             Varef           : 0.3 V
             Oscillator      : 28.800 kHz
             SCK period      : 3.3 us
    
    avrdude: AVR device initialized and ready to accept instructions
    
    Reading | ################################################## | 100% 0.01s
    
    avrdude: Device signature = 0x1e950f (probably m328p)
    avrdude: safemode: lfuse reads as 0
    avrdude: safemode: hfuse reads as 0
    avrdude: safemode: efuse reads as 0
    avrdude: reading input file "D:\dev\HEXTIr.hex"
    avrdude: writing flash (12358 bytes):
    
    Writing | ################################################## | 100% 2.38s
    
    avrdude: 12358 bytes of flash written
    avrdude: verifying flash memory against D:\dev\HEXTIr.hex:
    avrdude: load data flash data from input file D:\dev\HEXTIr.hex:
    avrdude: input file D:\dev\HEXTIr.hex contains 12358 bytes
    avrdude: reading on-chip flash data:
    
    Reading | ################################################## | 100% 1.99s
    
    avrdude: verifying ...
    avrdude: 12358 bytes of flash verified
    
    avrdude: safemode: lfuse reads as 0
    avrdude: safemode: hfuse reads as 0
    avrdude: safemode: efuse reads as 0
    avrdude: safemode: Fuses OK (E:00, H:00, L:00)
    
    avrdude done.  Thank you.

    No change.  

     

    I'll be glad to help debug when you get everything setup again, please let me know.  Thanks a bundle for all your replies today!

     

    p.s. tested for shorts too.... 

     

    1BA3168B-C0DF-4DB1-B640-660B28EE8DDC.jpeg

    9B1ECEA7-19DC-4D8D-89A8-C9B6DE666129.jpeg

    • Like 1

  17. 4 minutes ago, brain said:

    The unit responds by default on #100

     

    The LED does double duty.  When on, it means file is open.  When flashing, it means an error has occurred.  The unit has code to set the device # from 100-107:

    static inline uint8_t device_hw_address(void) {
    return 100 + !((PIND & (_BV(PIN4) | _BV(PIN5) | _BV(PIN6))) >> 4);
    }

    Gotcha, thanks!  I have it hooked up, and the Arduino power light is on - L1 is not.  I've double checked my pinouts by hooking a Hexbus cable to a CC-40 and oriented both devices the same way to verify the 8 pins orientation were correct.  I've double checked the pins, the 1GB SD card is formatted FAT32, and the tab is set to allow writes.

     

    The CC-40 does power up with the device attached; however, any time I try to save "100.FILE", I don't get any response (just an I/O 255 error.)  I've tried a couple different FAT32 SD cards.  Since I've triple checked the wiring, it might be the way I compiled it or programmed the Uno, since I'm not seeing any activity on it at all when I try to complete Hexbus saves.  I'm assuming I don't need the Hexbus format command.

     

    Thoughts?


  18. 11 minutes ago, brain said:

    Yes, that is correct.  Maybe add that to the pull request

    One final question - what is the behavior of the L1 LED supposed to be?  Which device # does this respond to?

     

    About to go hook it up to my CC-40 now that I verified the pins were correct.  Will also try on the 74.

     

×
×
  • Create New...