Jump to content

Fonzie

New Members
  • Content Count

    25
  • Joined

  • Last visited

Community Reputation

9 Neutral

About Fonzie

  • Rank
    Space Invader

Profile Information

  • Gender
    Male

Recent Profile Visitors

2,700 profile views
  1. Was unable to pull up RXB 2015...message said There was a problem with the preview.
  2. I have a couple of spare Mitsumi keyboards. Although the keys are not black they both a white sticker with Mitsumi on them on a brown back plate. I’d be wary.
  3. I sent Custodio (Jaime) both of my nanoPebs to fix the printing problem, one in late December 2019 and the other in early January 2020. Both have been returned and work perfectly now. Custodio rocks.
  4. I tried using 2 stop bits in Putty to see any changes and got the same output as 1 stop bit. But I did learn one thing. The extraneous characters are not random. I had typed a few lines of 80 columns text and then copied these until I had about 15 lines to print. Every line had an extraneous first character but the same character appeared on every line that contained the exact same text. As I wrote earlier, Custodio Malilong made contact with me. However, most references about fixes in this and other threads mentioned Jaime. Could he be one and the same person? I guess I should ask him. Anyway, Ksarul generously offered to supply an XB 2.7 cartridge to allow testing. I’ll contact Custodio in the next day or two with all the information I have gathered relative to my problem and let him know of the offer of the XB 2.7 cartridge for testing.
  5. Editor Print File Device Name: RS232.BA=1200.DA=8.PA=N (If this setting isn’t correct for STOP BITS = 1, then I don’ t know how to type it in correctly to get it to print anything). Putty Setting: Speed (baud) 1200 Data Bits 8 Stop Bits 1 Parity None Flow Control XON/OFF
  6. Does anyone with a Nanopeb V1 use the editor in TI-Writer found in the Extended Basic V.2.7 Cartridge Suite to print to Putty or another Terminal program on their PC via the serial null modem cable without getting a single random character at the beginning of each line? Here is why I ask. I bought 2 Nanopebs, 1 in in late 2017 and the other in early 2018. It took a long time reading forum threads before I was able to successfully transfer DSKs back and forth from console to PC over a serial null modem cable to USB connection at the PC. Eventually, thanks to guidance from several forum members, I started printing volume catalogs to Putty using DM3 and printing my own catalog of volume files in Excel. Things seemed golden. Flash forward to a couple days ago. I fired up my Extended Basic v2.7 Suite cartridge, chose Writer/Assembler and then text editor. On a whim I decided to see if Nanopeb could print to Putty like a word processor for any text I typed. So I typed an article from a magazine I had been reading, chose PF Print File and set the serial parameters to: rs2232.ba=1200.da=8.pa=n. Then I set Putty to the same configuration and hit enter on the console. Text immediately appeared on my PC in Putty and I thought, “wow, It works.” Well not exactly. You see at the beginning of every line an extraneous random character appeared (e.g. 2HAD…,OGIVES… etc.) A little research in the forum turned up another Nanopeb user in 2017 that had described the same problem. Apparently, back then Jaime Malilong had left out some reference, (which I am not clear on) to SIO or the serial connection in the DSR of one or more of his Nanopeb batches. The user sent back his device. The DSR was updated, Nanopeb returned and the user did not experience any more extraneous characters at the beginning of lines. Here is where it really gets confusing. So, I sent an email to the contact given at www.nanopeb.com. I explained my problem, the identical or nearly identical problem in 2017 fixed by a DSR change and asked how I might get my problem resolved. I received a speedy reply from Custodio Malilong. He said, “I’d be glad to help. I don’t have TI-Writer, but can you tell me where I can get FunnelWeb? I’ll load it up and see if I can solve the issue. I have Putty. Just a follow-up. I’m using the print option on Editor/Assembler and I see a “P” at the beginning of each line. Is this what you are seeing?” He also told me he was using a CF7 to print to his parallel printer. Apples and oranges?. No! my characters are random. And just to muddy the waters further I dug out an Editor/Assembler Cartridge loaded some text and used the print function to print to my TI serial printer. I got text with the same “P” at the beginning of each line as he had. I emailed Custodio and emphasized to him random characters when using TI-Writer/Putty or when using TI-Writer directly to my serial printer. I told him of the consistent “P” when printing out of EA. I also said I was going to take a few days and do further research. Hence, my first line question. I am going to see what other information I can provide him to assist in my problem. I welcome any further guidance I might supply to him.
  7. Today I changed my router’s SSID from one which had a space in the name to one without spaces. I immediately descended into the basement where Tipi is located to see if this change would allow me to connect to the internet. SUCCESS!!! I connected to Heatwave bbs and created an account profile. Now I am in the middle of re-connecting all devices for the 4 users in this multi-generational household. Counting all computers, laptops, Amazon dots, kindles, iPods, iPads, printers, chrome book, ring doorbell, security camera, WIU, PS4, I’m nearing 30 devices (really). A change to the Tipi’s confit might have been easier. Count one damaged pi3 (my mad) also. Now to try and figure out the quickest way to make full use the Tipi, with only console, no F18a.
  8. Received a new pi3 yesterday from Amazon identical to the other except this one was manufactured in China and not the UK. Proceeded to test if Tipi would work. Here's what I did: 1. Re-flashed mini sd with Tipi sdimage 1.41. and inserted into pi3. 2. Cut a small thin piece of plastic from a sandwich bag and inserted it between the (2) 5-pin cables ends that abutted with metal connectors face-to-face at the back end of Tipi. Then correctly oriented and connected the other cable ends to pins 31-40 on Tipi. I hoped this would eliminate any possibility of shorting that I raised. 3. Powered up Tipi and waited for it to boot. 4. Powered up 32k sidecar and monitor and waited for monitor to warm. 5. Turned on console and chose TI Basic. 6.Typed CALL TIPI (enter) 7.Tipi screen appeared in seconds. Yeah!! 8. Typed S (enter) and Tipi screen when to SSID: and waited for input. 9. Typed my SSID and pressed enter. Typed P and entered. 10. Tipi screen went to PSK: and waited for input. 11. Typed my password (upper and lower case as necessary) and entered. 12. Pressed W to write the configuration. I waited but an IP address never showed up. So I quit (Q enter) tried again re-flashing sd card and once or twice more (but not always re-flashing card) even substituting my 1st pi to see if the plastic barrier between cable ends would allow Tipi to get to that first screen. But before I wear out the sd card and my legs (Tipi in basement, re-flashing computer on 1st floor) I thought I would ask for advice. My SSID consists of upper and lower case letters with one space: e.g. Xxxxxx Xxxxx_5G, and my PSK: e.g. XxXxxXxxxxxXxxXxxxxxxxx, 23 characters, upper and lower case letters, the at symbol and several digits. Anything unusual, length? that might be causing a problem? Anything else I might try before I send Tipi off for possible repair?
  9. I need to think about this for a while. I don’t have another pi so I would have to order one and wait for delivery. It is possible that the voltage did no harm to the pi’s gpio or pins 31-40 used for connecting to Tipi do not impact the pi from otherwise appearing to operate normally. I’ll hold up shipping off Tipi for now.
  10. Tested continuity, all good. I have it packaged up and will ship it Greg’s way tomorrow. Thanks to all for your suggestions.
  11. I successfully loaded Raspbian on my pi3. This was my first introduction to the Linux OS. I especially appreciated watching the screen display change as the installation progressed. This eliminates the pi from the list of possible culprits for Tipi failing to install. So not knowing Tipi inticracies, I am listing the following as possible causes. 1. Corrupted CPLD 2. Corrupted EEPROM 3. Both CPLD and EEPROM corrupted 4. Cabling problems 5. Current Tipi image not compatible with early EEPROM programming. (18 month lag between Tipi purchase and Current attempt to install). I have neither the expertise nor tools to troubleshoot further. Has a repair service for Tipi been established? Any further suggestions are welcome.
  12. I tried swapping connector ends at the Tipi inside to outside and vice versa with the same result. I also removed all cables and powered up console, sideport 32k memory and Tipi and I still get the same triple tone without any connection to the pi. So here are my thoughts: 1. connecting to the JTAG connection compromised the CPLD, the programming eeprom or both. 2. (longshot here) The 5-pin cables are shorting out on whichever end requires them to abut metal contacts face-to-face while keeping the same wire orientation. 3. Something is the matter with the pi3. I am going to try the pi without Tipi installing NOOBS and see it boots and works. Is there a way to verify that the Tipi CPLD is not fried? Could it be the eeprom was compromised by connecting to the JTAG connector. I'm beyond frustrated and just grasping at straws here. Your thoughts.
  13. Yes, circled connector is exactly where I plugged in first go. All subsequent tries have used rear connection. I downloaded image from the Tipi wiki site and flashed it to SanDisk 64 mb micro sd card with Etcher. I studied cabling diagrams even tracing wires pin-to-pin like pin 31 on pi to pin 1 on Tipi etc. So I am pretty confident I have cabling correct. However, there are only a couple of different connection combinations available with the 5-pin cables if I only change at the Tipi. I am assuming I don’t have to reflash the image at each different connection trial. Would you agree? I’ll let you know tomorrow.
  14. Good news, I did NOT plug into the wrong side of the pi but I did connect cables from the pi to the Tipi 10-pin connector by the led and powered up. Whether this is a 2nd way to destroy the cpld I don’t know. Still no joy. Correctly connecting cables, reflashing the sd and repeating the install sequence several times still leaves the TI hanging at the CALL TIPI entry. I do hear the triple tone each time The TI main screen appears if that helps. Any further ideas? Should I purchase another cpld and try again?
  15. Yep, I am pretty sure I connected the PI and TIPI cables to the wrong pins and screwed things up. I had Tipi for nearly a year and a half but hadn’t installed it because I felt intimidated. I am the furthest person from a geek you could find, never burned an image, never used linux etc. But yesterday I got the courage up, gathered everything needed and …failed miserably. How could that happen? Here's how. I orientated both boards flat side-by side, Pi on the left, Tipi on the right and proceeded to hook the 5-pin cables up. Instructions said one set of cables was blue the other purple (my cables however were multi-colored). But I knew that wouldn’t matter as long as I oriented them correctly. So, thinking the long bar in the Tipi illustration represented the right edge of the board I dutifully connect the cables to the 10-pin connector, one cable set from the outer set of pins from the Tipi to the inner 5 pins on the PI and the 2nd cable from inner to outer pins as shown in the drawing. I powered up the PI and waited fully 2 minutes to be sure it had booted. Then I turned on my console went to TI Basic, typed CALL TIPI and waited and waited and well you got the picture. Nothing happened on screen. After a good while I powered off the PI (no way to shut it down except to power off ) and console and figured I must have done something wrong…again. After a good deal of thought it dawned on me the illustration of Tipi was an end view (the connector at the end opposite the led) not a top view like the PI next to it as I originally thought. Too late, damage done but what could it hurt to hook the cables to the end connector and try again anyway, which I did with the same result. Now the question(s), how much damage did I do? Can it be repaired? I am assuming the Tipi needs repair. Has the PI itself been damaged or the micro sd and its image? How to proceed? I do have an authentic TL866II burner that I have never used other that periodically updating it successfully. But, given my lack of confidence and goof history, its use would be a tough go. Any advice or suggestions would be appreciated.
×
×
  • Create New...