Kachina 505DSP Transceiver

Users Resource Website

Updates

June 29, 2010
Added the "Updating Firware EPROMs" section information.

FIRMWARE

Software "Types"

Control and operation of the Kachina 505DSP is dependent on two types of software: (1) a control program operating on your PC, which we just call "software", and (2) a program contained within your 505DSP in either two (EP)ROM chips or a PCMCIA ROM card, which we call "firmware". Each type has a version number associated with it, often quite similar and confusing. See the section on SOFTWARE for version number information.

Firmware Files

At this time, we do not have any versions of the firmware online. Contact webmaster (see "Contact" section) if something is needed.

Updating Firmware EPROMs

Thanks to Claus (OZ2IE) for the following information:

General information for those thinking about programming new firmware EPROMs for their Kachina 505DSP.

I have had a long E-Mail story with Clyde, WA6DCM, concerning programming chips with newer firmware for the Kachina. The main issue in up-dating the firmware is to get the right EPROM. It is a jungle out there! First, it can be hard to find the chip, and second, to get them with the right speed. Now it sounds easy but the manufacturer of those chips makes it difficult by marking the speed on those EPROM in different ways, some are marked 15 or 20 and they are 150 and 200ns. Definitly too slow. Atmel AT27C256-45 is 45ns and will do the job, also the AT27C512R-45JU which I have used is working. Remember that it is a PLCC32 housing.

The chip must be better than 60ns. 50ns or 45ns is preferred making a margin to the limit of 60ns. Finding 27C256 might be difficult but then take 27C512 and make the image from X8000 to XFFFF.

I have made the 3.49 firmware and it is working in my B2 401 HW. I have used AT27C512R-45JU. To program the EPROM, you need a programmer and a adapter. I made the adapter from a 1:1 PLCC32 to DIP28 purchased from Hong Kong for US$2, a piece of prototype board and two Molex pin rows and 28 short wires.

I will be able to help programming the two EPROMS with either 3.49 or 4.49 firmware now I have made the adapter. E-Mail me for more details. Claus OZ2IE. Email address: claus (at) rimestad (dot) net
Photos below by Claus, OZ2IE:

PLCC32 to DIP28 PLCC32 to DIP28


The FIRMWARE PROJECT

Background

Without going into great detail, here's a recap of the situation: Kachina Communications Inc. (KCI), the manufacturer of our Kachina 505DSP transceivers is no longer in existence. Efforts to gain a copy of the firmware source have all ended without success. The original firmware writer and others contacted will not even reply to email. The techs who worked at KCI have supplied us with some information, but do not have the source files.

It is important to the life of the 505DSP to be able to make changes and additions to the radio's firmware. A couple years ago, an effort was started by AE5K to disassemble a version of firmware and to figure it out. "Figure it out" essentially means producing a reconstructed source code file that is reasonably commented with meaningful labels, one that will compile or assemble to produce the binary firmware files we already have. A disassembler was purchased and much work was done in placing comments and labels in the "reconstructed source" file. At this time, much more work is needed on this to be of any value to us.

How to Help?

For those owners who have some experience in assembly language programming and who can read and comprehend the schematic of the 505DSP, we could use your help on this project if you have some time to devote to it. The plan is to make available (see "Files Online" below) the original output from the disassembler plus the ongoing reconstructed source file. Anyone wanting to help can then select a section (subroutine, function, etc.) of the code and devise meaningful comments and labels for that part. That information would be sent to AE5K, and maybe after some peer review, he will incorporate it into the reconstructed source file. At this time, absolutely no changes will be permitted that will alter the binary firmware file from the original -- in other words, the reconstructed source file shall assemble and produce an identical binary file that we started with. It should be noted that this is assembly language, not "c" or other higher level language.

Files Online

Here are links to files needed for working on this project:
Original binary version 4.49
Original output from disassembler
Ongoing reconstructed source - updated periodically
Ongoing reconstructed source assembler listing - updated periodically
OpenOffice spreadsheet file of SRAM usage - updated periodically
MC68HC16 info - list of files, manuals, etc. (some large)

Special k505fw Discussion List

A separate email discussion list has been established for communication between only those participating in this firmware project. This will be used to let others working on the project know what you are working on, to ask questions, to give and receive help, to get some peer review of what you have done, etc. It is a separate discussion list from the main Kachina list in order to not cause owners not interested in all this to leave the main list. Since it is a separate list, members must go through the usual "mailman software" subscription process. Do this at http://lists.ae5k.us/listinfo.cgi/k505fw-ae5k.us NOTE: Please use your ham call in all uppercase letters in place of "Name" when it asks for it.

Please use the k505fw list for all project discussion -- not the regular Kachina list!

Technical Notes for Project Participants

Please let us know what you are working on and your progress. We'll post more information here as time goes on.

The file to start looking at is the "k449s.dis" as it will be here that your comments/labels are added.

Regarding the OpenOffice spreadsheet for SRAM usage, we need someone to figure out fix for missing function (DEC2'hex') for column B. I don't have time right now to find it and install, so would appreciate someone looking into it. Column A is decimal address and B is the hex address. (B shows error right now on my install)