Jump to content

acadiel

+AtariAge Subscriber
  • Content Count

    1,623
  • Joined

  • Last visited

  • Days Won

    2

acadiel last won the day on February 13 2018

acadiel had the most liked content!

Community Reputation

1,231 Excellent

About acadiel

  • Rank
    Stargunner

Contact / Social Media

Profile Information

  • Custom Status
    www.hexbus.com
  • Gender
    Male
  • Location
    USA
  • Interests
    TI-99/4A Hardware hacking

Recent Profile Visitors

18,932 profile views
  1. That’s what I finally wound up doing. It’s a replicated Radio Shack 277-1008. It actually worked.
  2. I know someone did in here.... I’ll have to do a power search
  3. I've tried multiple recorders and multiple cassette cables - so have eliminated everything but the console.
  4. I have... but I'm not sure if this mod is on the schematics, since it appears to be done to production boards (Farmer Potato and Klaus').
  5. 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?
  6. 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?)
  7. 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.
  8. 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.
  9. 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.
  10. 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....
  11. 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?
  12. 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.
  13. @brain - in this document: https://github.com/go4retro/HEXTIr/blob/master/doc/arduino/Assembly Instructions.txt Do you mean to increment the data pins? i.e. HEX D0 -> A0 HEX D1 -> A1 HEX D2 -> A2 HEX D3 -> A3 At least, that's what I'm assuming
×
×
  • Create New...