Re: XCat NG changes
<swguest@...> wrote:
The way the legacy Xcat worked was that all frequency / PL / scan list
changes just updated RAM for the special "VFO" mode (mode 1). A
separate (custom) command
By
Skip Hansen
·
#386
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
Jumper is in for 2K mode.
By
Casey Crane
·
#385
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
IIRC his setup was originally a 2k.
I dont know if he ever had or tried to install a 2864
By
swguest
·
#384
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
I don't care what's in it. One mode is fine.
I had the pins offset wrong. You have to hang 4 over the edge for a 2k
eeprom. It now shows fail 01/82 which is a bit of progress.
I don't have a floppy
By
Casey Crane
·
#383
·
|
Re: XCat NG changes
I'm thinking the data update write to EEPROM is going to be (relatively) slower than a mirror copy to RAM.
It seemed logical to pre-calculate all the bytes to change to their new values, checksum the
By
swguest
·
#382
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
Don't forget that the radio has a jumper for EEPROM size.
De
By
Dennis Boone
·
#381
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
Hmmm..odd that it didnt complain about a 9k but did about a 2k. being 2048 byte but trimmed to 0-2047 in you hex editor.
Well you know it does something. The radio may have hung on the fact that the
By
swguest
·
#380
·
|
Re: XCat NG changes
My plan is to have an area in RAM that mirrors the EEPROM data. The
PIO state machine would DMA data from the RAM buffer to the GPIO pins
automagically. The CPU would have nothing to do except
By
Skip Hansen
·
#379
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
No joy yet. It loaded up the uhf file off the web site and the
software didn't complain. I was able to transfer it to the device's RAM and
verify and it was happy. However, the radio just stays on
By
Casey Crane
·
#378
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
Mine is 6.00SP so it's old.
[email protected]> wrote:
By
Casey Crane
·
#377
·
|
Re: XCat NG changes
needs *BE* to online serving data before that.
and not the WWW definition of online.........
By
swguest
·
#376
·
|
Re: XCat NG changes
No, I get it. That's what I was thinking. I like that design too, once I mulled it over a bit....ala KISS.
...that was part of the epifany.
Why worry about addr change? Let it read the addr and write
By
swguest
·
#375
·
|
Re: XCat NG changes
The /CE input will be wired directly to a bus transceiver between the
bus and the Pico. The CPU won't be aware of /CE state. I may be
overly optimistic, but the plan is for the PIO state machine to
By
Skip Hansen
·
#374
·
|
Re: XCat NG changes
CE in regard to what?
[email protected]> wrote:
By
Casey Crane
·
#373
·
|
Re: XCat NG changes
I didnt se a /CE input.
I had one of those 3:42 am epifany's this morning........
By
swguest
·
#372
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
Just curious.? R8.01 runs is a cmd window without griping. Keep me from having to mess w/the NEC..............which
I fired it up today after a long time down...the HDD spun up but the bios was
By
swguest
·
#371
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
I don't recall now. My IP rolled or VPN Pi tunnel imploded or something and
I can't get back to the home PC to check. It's some SP 128 mode version I
think, or at least that's what I recall the folder
By
Casey Crane
·
#370
·
|
Re: XCat NG changes
As in Next Gen?
Off to the Wiki.....
By
swguest
·
#369
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
There is a byte (lost dics) on zero page that identifys the band.
I dont thinks the radio will implode, create a micro black hole and suck in the known universe but I'm reasonably sure it wont like
By
swguest
·
#368
·
|
Re: Has anyone fully decoded the X9000 memory mapping?
Awesome, thanks!
[email protected]> wrote:
By
Casey Crane
·
#367
·
|