apache-labs.com

Read the "sticky/tacked" threads here and use Bootloader:

viewforum.php?f=18

Where is the jumper bootloader on Orion MK 2 board?

LU2FAF wrote:Where is the jumper bootloader on Orion MK 2 board?

JP17

Look for the Bootloader switch on the bottom or back of case. No jumper except on 100d and older ones. My 200D has switch on the bottom and 8000dle and 7000 on the back. Yours should be below the 10mhz reference SMA connector.

Tom
KA1GXR

LU2FAF wrote:

LU2FAF wrote:Where is the jumper bootloader on Orion MK 2 board?

JP17

Fixed with this guide: viewtopic.php?f=18&t=2333
Sad that I had to
1. Use windows to run that soft because there wasnt any source code or no pcap binary for linux.
2. Had to open the case, removing the heatsink, connect directly to a windows machine ( without the switch)

Next time try SparkSdr. There's a Linux version and i think it can program the firmware too.
(look for "Gateware Upload" in the SparkSdr manual.)
https://www.sparksdr.com/

LU2FAF wrote:Fixed with this guide: viewtopic.php?f=18&t=2333
Sad that I had to
1. Use windows to run that soft because there wasnt any source code or no pcap binary for linux.

There most certainly is a Debian version of Bootloader. If you used the guide you referenced above it would take you to the Git repo for Bootloader where both Windows and Debian versions can be downloaded. And all source code is available there as well. But if you did not follow the link in the guide for obtaining Bootloader that may be your problem.

2. Had to open the case, removing the heatsink, connect directly to a windows machine ( without the switch)

Anyone who builds their own hardware using any Apache board should definitely add an external Bootloader switch. That's the fault of the builder, not the board design.

And you do not need to use a direct connection. Bootloader will run through most (not all) dumb switches. But it will not run through a managed switch. This is explained in the guide.

PD3LK wrote:Next time try SparkSdr. There's a Linux version and i think it can program the firmware too.
(look for "Gateware Upload" in the SparkSdr manual.)
https://www.sparksdr.com/

Thank you for that
I think we need a better way to store that kind of info. Using a thread isn't an option, maybe here: http://openhpsdr.org/wiki/index.php?tit ... d_software
thats so outdated.

w-u-2-o wrote:

LU2FAF wrote:Fixed with this guide: viewtopic.php?f=18&t=2333
Sad that I had to
1. Use windows to run that soft because there wasn't any source code or no pcap binary for linux.

There most certainly is a Debian version of Bootloader. If you used the guide you referenced above it would take you to the Git repo for Bootloader where both Windows and Debian versions can be downloaded. And all source code is available there as well. But if you did not follow the link in the guide for obtaining Bootloader that may be your problem.

2. Had to open the case, removing the heatsink, connect directly to a windows machine ( without the switch)

Anyone who builds their own hardware using any Apache board should definitely add an external Bootloader switch. That's the fault of the builder, not the board design.

And you do not need to use a direct connection. Bootloader will run through most (not all) dumb switches. But it will not run through a managed switch. This is explained in the guide.

I found the source, but isn't git clone ready, no make file. Maybe we can help people out there making everything simpler.
I think the bootloader switch shouldn't be used every time you need to upgrade. Maybe the procedure is wrong. I don't store my aux wheel on front seat.
I know you can find many reasons to leave things as they are, but maybe there is a way to improve them.

LU2FAF wrote:I found the source, but isn't git clone ready, no make file. Maybe we can help people out there making everything simpler.
I think the bootloader switch shouldn't be used every time you need to upgrade. Maybe the procedure is wrong. I don't store my aux wheel on front seat.
I know you can find many reasons to leave things as they are, but maybe there is a way to improve them.

Remember that all of the software and firmware are open source and developed by volunteers. Apache only builds hardware, loads the firmware, and supports the open source dev's.

There are only two ways to improve the software and firmware:

1. Learn to code, then make the changes yourself.

2. Find a like-minded developer who is interested in your specific ideas and convince them to do the work.

All of the software and firmware we have is a labor of love created for free by a very, very small group of people. There probably aren't as many as 10 people in the world who have made significant contributions to PowerSDR and Thetis. And only 3 people that I'm aware of who have ever worked on the Protocol 2 firmware. We are super lucky to have what we have. Warts and all it's an amazing body of work by such a small group.

I know that I personally would love to see the functionality of the P1 firmware loader, P2 firmware loader, and the Bootloader all combined into a single tool and made completely automatic, with prompts as necessary to operate the Bootloader switch. And for a way to fix the Bootloader firmware to use a legal MAC address. Maybe build this all into Thetis, too. But as someone who is not a developer unfortunately all I can do is dream about such functionality.

If you are really passionate about having Bootloader on Linux, it would not be too hard to create a better repo with the necessary make files. The folks who control the TAPR Git repo would be happy to host such an improvement on the main repo in place of what is already there.

Rick,
Running your latest firmware (Protocol_2_v2.1.18) on 8000 here and all is good so far, no issues.

Thanks and 73's,
Joe
WD5Y

V2.1.18 running good here.

Mark

So far no issues. Firmware (Protocol_2_v2.1.18) running on my 7000 MKII . Thanks for the update!

73
Mike W4GM

2.1.18 is super stable for me so far on an older 8000. Not a single seq error or glitch in many hours of operation.

Okay, where do I get this to try out?

Checkout the first post of this thread

w2ner wrote:Okay, where do I get this to try out?

2.1.18 working here with no issues so far. Thanks for your work on this Rick

new update seems to be working ok.. the only negative affect it had was it automatically turned on the "Limit drive on external amp overload" which caused it to reduce to zero power. I don't run a amplifier. So i had to go back in and uncheck that.

Loaded into my blue face 7000DLE. So far with a hot radio no issues, and this AM with a cold radio everything seems to work.

Been using it all morning on my 8000, Rick. No issues thus far.

Hi Rick and all,

Running now the new FW 2.1.18. Its all very stable, no Problems with my 7000 DLE MKII with blue Face.

One Question: Shows Thetis 21F the correct FW-Version if it was 2.0b ?? I get this Radio used, and i am not shure witch Version was on it.
In Thetis 21F i see only 2.0.0

Thanks for the hard Work on the Firmware!!

73 Erwin

Erwin,

Proper display of firmware version information required cooperative firmware and software updates. While there are some early alpha firmware versions floating around out there that might work, officially anything older than Thetis 2.8.11-21f and firmware 2.1.18 will not display the full, correct firmware version in Setup > General.

73,

Scott

Question: has anyone else noticed that with FW 2.1.18 the PTT transients on the DUP display are no longer evident?

w-u-2-o wrote:Question: has anyone else noticed that with FW 2.1.18 the PTT transients on the DUP display are no longer evident?

Scott have not noticed this, but have not noticed it before. Can you describe what you were seeing?

NC3Z wrote:

w-u-2-o wrote:Question: has anyone else noticed that with FW 2.1.18 the PTT transients on the DUP display are no longer evident?

Scott have not noticed this, but have not noticed it before. Can you describe what you were seeing?

When you activate or deactivate PTT you often see a noise burst on the DUP display, like a key click.

I see one of those transients on both sides of the passband in the waterfall at the end of every transmission. V2.1.18 21f

Mark

K1LSB wrote:I see one of those transients on both sides of the passband in the waterfall at the end of every transmission. V2.1.18 21f

Mark

Running 2.1.18 on my 7000 DLE MK2 (black face) for a couple of hours. No problems so far. No issues on ptt.

73 Ernst

OK, I updated the FW to 2.1.18 on my 7K DLE MKII, Setup/General/HW now shows ver 2.1. I see no new buttons or changes. I also changed my Skin & buttons to Clarity N from W1AEX site. Does FW 2.1.18 include the 21f changes? Is there a Change Notice document that lists all the changes to 2.1.18?

Dave
k4em

Dave30019 wrote:OK, I updated the FW to 2.1.18 on my 7K DLE MKII, Setup/General/HW now shows ver 2.1. I see no new buttons or changes. I also changed my Skin & buttons to Clarity N from W1AEX site. Does FW 2.1.18 include the 21f changes? Is there a Change Notice document that lists all the changes to 2.1.18?

Dave,

You may be confusing software with firmware. Firmware makes the hardware in the ANAN unit run, and pre- and post processes data for the software. Firmware will not have any significant affects on the software, Thetis.

If you are running Thetis 2.8.11-21f and firmware 2.1.18, then you will see "Firmware Ver: 2.1.18" in Thetis Setup > General. If you don't see this then it sounds like either a) you did not get your firmware properly updated and/or b) you are not running Thetis 2.8.11-21f.

Scott,
No I did not install 21f, just the 2.1.18 FW which went smoothly.

Dave
k4em