[chirp_users] An error has occurred. Image not supported by radio:

Jim Unroe
Sat Sep 12 21:22:18 PDT 2015


Debra,
Do not download anything from the KC9HI list. Use your BAO2.img or
BAO3.img to upload to radio #1.
Jim

On Sun, Sep 13, 2015 at 12:18 AM, dwilson <dwilson223 at cox.net> wrote:
> I am not sure which image to select in kc9hi list. The closet I see is
> N5R3403 but mine was N5R340A.
>
> What should I do?
>
>
> -----Original Message-----
> From: chirp_users-bounces at intrepid.danplanet.com
> [mailto:chirp_users-bounces at intrepid.danplanet.com] On Behalf Of Jim Unroe
> Sent: Saturday, September 12, 2015 8:36 PM
> To: Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
> Subject: Re: [chirp_users] An error has occurred. Image not supported by
> radio:
>
> Debra,
>
>
> On Sat, Sep 12, 2015 at 11:06 PM, dwilson <dwilson223 at cox.net> wrote:
>> Ok, rats, and I thot I was doing so good... have no idea where the
>> other firmware came from because I don't own any other radios and have
>> never been in chirp before today, but nevertheless...
>
> The radio probably got a bad load at the factory.
>
>>
>> May I ask how you could tell about the BFB firmware?
>
> The memory layout changed when going from BFB firmware to N5R firmware. They
> are not compatible an image from one to a radio of another is not good. So
> if CHIRP detects this, it aborts the upload.
>
>>
>> I would like to confirm I understand what needs done here before I do it.
>>
>> So now I need to actually upload an old build (7-14-2014) into chirp.
>
> Yes. You can use the "win32.zip" version. Just extract it anywhere
> convenient. That way it won't mess with your current CHIRP. Just find and
> double click on the "chirpw.exe" file.
>
> The old version is needed because it doesn't have the check that keeps you
> from uploading the wrong image into your radio. Without the old version,
> uploading the BAO2.img into radio #1 would fail.
>
>> Then I go to the KC9HI site and click on the F5R3407 BF-F8HP(150319N)
>> (factory) img and that will load the factory image into chirp? (if I
>> don't have the old build loaded this wont work?) and then I need to
>> upload the factory file into radio 1 and then I have to reload the latest
> chirp build.
>> Do I have that right?
>
> Not exactly. You don't need to download anything because you can upload your
> image from radio #2 or radio #3. Then once you are successful, you can
> remove the folder that the 7-14-2014 version of CHIRP is in.
>
>>
>> Will the other images I currently have in chirp be deleted when I load
>> the old version?
>
> Not if you do it the way I just explained to do it.
>
>>
>> So grateful for your help...
>>
>> -----Original Message-----
>> From: chirp_users-bounces at intrepid.danplanet.com
>> [mailto:chirp_users-bounces at intrepid.danplanet.com] On Behalf Of Jim
>> Unroe
>> Sent: Saturday, September 12, 2015 6:06 PM
>> To: Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
>> Subject: Re: [chirp_users] An error has occurred. Image not supported
>> by
>> radio:
>>
>> Debra,
>>
>> Yes. The squelch settings were changed in radio #1.
>>
>> All three radios have the same N5R340A firmware. You should be able to
>> able to upload an image from any one of them to any one of the others.
>>
>> The reason you can't (and it is a good thing you can't) is because
>> someone has uploaded and image from a radio with BFB firmware into
>> radio #1. It probably doesn't receive signal without pressing the
>> [MONI] button. You definitely do not want to upload BAO1.img into radio #2
> or radio #3.
>>
>> You need to follow the procedure in the link below and upload either
>> BAO2.img or BAO3.img (they are both identical) into radio #1.
>>
>> http://www.miklor.com/uv5r/UV5R-Recovery.php#N5R
>>
>> Once radio #1 if fixed, be sure to upgrade back to the latest CHIRP
>> daily build.
>>
>> Jim KC9HI
>>
>> On Sat, Sep 12, 2015 at 8:40 PM, dwilson <dwilson223 at cox.net> wrote:
>>> You know, I think on the first radio I might have changed the service
>> settings before I actually saved the first file...
>>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe at intrepid.danplanet.com
>>
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2015.0.6086 / Virus Database: 4419/10627 - Release Date:
>> 09/12/15
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe at intrepid.danplanet.com
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2015.0.6086 / Virus Database: 4419/10627 - Release Date: 09/12/15
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> To unsubscribe, send an email to chirp_users-unsubscribe at intrepid.danplanet.com



More information about the chirp_users mailing list