Date   
Re: rbf file programming

Sid Boyce
 

Hi David,
It does the erase then tries to write firmware and fails after 2 seconds.
73 ... Sid.

On 19/06/2019 03:27, David Fainitski wrote:
Hello, Sid

Try old one https://github.com/Dfinitski/Odyssey-2_2017_TRX/blob/master/BootLoader_2.0.pyw.zip
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: rbf file programming

Sid Boyce
 

Same error report.
73 ... Sid.

On 19/06/2019 03:27, David Fainitski wrote:
Hello, Sid

Try old one https://github.com/Dfinitski/Odyssey-2_2017_TRX/blob/master/BootLoader_2.0.pyw.zip
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: rbf file programming

David Fainitski
 

rbf file programming

Sid Boyce
 

Timeout writing firmware.

Timeout problems on LAN with 16 port Gigabit switch.


Moved to a direct connection to a laptop, same problem.

nmap scan on laptop.

# nmap -sT 192.168.10.0/24
Starting Nmap 7.70 ( https://nmap.org ) at 2019-06-18 22:40 BST
Nmap scan report for 192.168.10.89
Host is up.
All 1000 scanned ports on 192.168.10.89 are filtered
MAC Address: 00:1E:C0:A6:10:99 (Microchip Technology)

Nmap scan report for 192.168.10.80
Host is up (0.00032s latency).
Not shown: 999 closed ports
PORT   STATE SERVICE
22/tcp open  ssh

Nmap scan report for siddly (192.168.10.95)
Host is up (0.00033s latency).
Not shown: 999 closed ports
PORT   STATE SERVICE
22/tcp open  ssh

Nmap done: 256 IP addresses (3 hosts up) scanned in 51.92 seconds

73 ... Sid.

--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

Sid Boyce
 

Thanks David, Success at last!
What came up originally was PIC16F1887.
I forgot PIC16F1827 mentioned in your email while checking to find how to set LVP on.

*****************************************************

Connecting to MPLAB PICkit 3...

Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.56.00
Firmware type..............Enhanced Midrange

Target voltage detected
Target device PIC16F1827 found.
Device Revision ID = 7

Device Erased...

Programming...

The following memory area(s) will be programmed:
program memory: start address = 0x0, end address = 0xc47
configuration memory
Programming/Verify complete
73 ... Sid.

On 18/06/2019 14:50, David Fainitski wrote:
Check  the device name.   It should  be pic16f1827

Not 18877
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

David Fainitski
 

Check  the device name.   It should  be pic16f1827

Not 18877

Re: Bootloader update to 2.1

Sid Boyce
 

It's on.
73 ... Sid.

On 18/06/2019 13:08, David Fainitski wrote:
Sid,  did you see the picture in my last message?
It shows that MPlab X has this possibility.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

Sid Boyce
 

I have just seen it and I have it set.
Read complete

Device Erased...

Programming...

The following memory area(s) will be programmed:
program memory: start address = 0x0, end address = 0xc5f
configuration memory
program memory
Address: 0 Expected Value: 2f90 Received Value: 0
Failed to program device
73 ... Sid.

On 18/06/2019 13:08, David Fainitski wrote:
Sid,  did you see the picture in my last message?
It shows that MPlab X has this possibility.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

David Fainitski
 

Sid,  did you see the picture in my last message? 
It shows that MPlab X has this possibility. 

Re: Bootloader update to 2.1

Sid Boyce
 

Got a problem with VirtualBox not starting, troubleshooting that at the moment.

MPLABX GUI should be capable of doing the job of programming in LVP mode. I'll see if I can find more or raise the problem with Microchip.
73 ... Sid.

On 18/06/2019 06:24, David Fainitski wrote:
No, this is wrong way. It is meaning low voltage operation, not low voltage programming.
Try to programm trough Mplab or install Windows.

How will you use Thetis or Sdr-Console if you don't have a Windows machine ? Thetis need NET. platform too.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

David Fainitski
 

No, this is wrong way. It is meaning low voltage operation, not low voltage programming.
Try to programm trough Mplab or install Windows.

How will you use Thetis or Sdr-Console if you don't have a Windows machine ? Thetis need NET. platform too.

Re: Bootloader update to 2.1

Sid Boyce
 

I downloaded http://ww1.microchip.com/...pplication%20v3.10.zip.
Unzipped it and the ReadMe.txt says I need .Net v4.00 and to download from Microsoft -- that assumes a Windows box which I have not owned since the days of Windows 95.

I have just downloaded this ETN32_PICkit_3_Operation_at_Low_Voltage.pdf which details a hardware mod for LVP operation.
73 ... Sid.

On 18/06/2019 00:33, David Fainitski wrote:

[Edited Message Follows]

No, Sid, What about step 3 on the example ? Did you set the same option ? See the picture.

Why don't you use Pickit v3.10 as sugested many times before?
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

David Fainitski
 
Edited

No, Sid, What about step 3 on the example ? Did you set the same option ? See the picture.

Why don't you use Pickit v3.10 as sugested many times before?

Re: Bootloader update to 2.1

Sid Boyce
 

I can't find any such option on the GUI.
Looked at this URL not seeing anything like it --
https://microchipdeveloper.com/icd3:low-voltage-programming
73 ... Sid.

On 17/06/2019 15:22, David Fainitski wrote:
Sid, LVP mode you should to use for successful programm MCU.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

David Fainitski
 

Sid, LVP mode you should to use for successful programm MCU.

Re: Bootloader update to 2.1

Sid Boyce
 

Power connected to ODY-2 but not powered on --- won't power on with PICkit3 plugged to ODY-2 5-pin connector.
From the GUI:- Odysset_2_MCU (Load,Run)  Output tab
*****************************************************
Loading code from /c1/usr/src/XXX/Odyssey_BL_2.1/Odyssey_2_MCU.hex...
Loading completed
Connecting to programmer...
Programming target...
The programmer could not be started: Failed to program the target device


PICkit3 tab
============
Connecting to MPLAB PICkit 3...

Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.56.00
Firmware type..............Enhanced Midrange

Target voltage detected
Target Device ID (0x0) is an Invalid Device ID. Please check your connections to the Target Device.

Device Erased...

Programming...

The following memory area(s) will be programmed:
program memory: start address = 0x0, end address = 0xc5f
configuration memory
program memory
Address: 0 Expected Value: 2f90 Received Value: 0
Failed to program device
73 ... Sid.

On 17/06/2019 12:07, Sid Boyce via Groups.Io wrote:
Hi Marc,
I was looking for a quick solution in Linux having installed MPLABX-v5.20. Results from just a brief try so I have not yet looked any closer to see if I can discover the reason for the illegal access warning or to try the GUI.

This is what I get using the command line in Linux. Power LED is Green, Active light comes on periodically and Status LED solid Red and after a while changes to Solid Green.
It doesn't complete and come back to the command line.

From lsusb
---------------
Bus 001 Device 025: ID 04d8:900a Microchip Technology, Inc. PICkit3

# java -jar /opt/microchip/mplabx/v5.20/mplab_platform/mplab_ipe/ipecmd.jar -OL -TPPK3 -M -P16F18877 -F./Odyssey_2_MCU.hex
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.openide.util.lookup.implspi.ActiveQueue$Impl (file:/opt/microchip/mplabx/v5.20/mplab_platform/platform/lib/org-openide-util-lookup.jar) to field java.lang.ref.ReferenceQueue.lock
WARNING: Please consider reporting this to the maintainers of org.openide.util.lookup.implspi.ActiveQueue$Impl
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
*****************************************************
Connecting to MPLAB PICkit 3...
Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.51.08 *
Firmware type..............Enhanced Midrange
Now Downloading new Firmware for target device: PIC16F18877
Downloading bootloader
Bootloader download complete
Programming download...
Connection Failed.
73 ... Sid.

On 16/06/2019 07:22, Marc olanie wrote:

… and I will send you a translation for french speaking hams :- )

Thanks Sid

Marc f6itu (still collecting Ody’s components)

*De :*ody-sdr@groups.io <ody-sdr@groups.io> *De la part de* AA6I Stan via Groups.Io
*Envoyé :* samedi 15 juin 2019 21:16
*À :* ody-sdr@groups.io
*Objet :* Re: [ody-sdr] Bootloader update to 2.1

Sid;

*For people like me, a write up would be greatly appreciated. *

Thanks

Stan  AA6I

On 6/14/2019 11:22 PM, Sid Boyce wrote:

    Thanks David,
    That was the missing part of the puzzle as the ANP.rbf file was
    not there when I unzipped the download.

    OK on the Pickit3.

    *When all done I must do a write-up on all this. *
    73 ... Sid.

    On 15/06/2019 03:40, David Fainitski wrote:

        Hello, Sid
        Please understand the difference between bootloader and
        working firmware. You can write *Bootloader.rbf into slot 0
        ONLY.* Because slot 0 is the starting address of memory, FPGA
        dowloads this bootloader code after start.
        You can write working firmware like Odyssey_2_1.20_ANP.rbf
        into slots 1-3. You can not to write working firmware into
        slot 0.
        If you will try to do something wrong, the programm wil say
        you that file incorrect to avoid problems.

        If the bootloader code is damaged in memory, you can return it
        with Qartus. After that use Bootloader_2.1.pyw for upload
        working firmware to slots 1-3. If you did this before and
        slots filled, you don't need to do this more, only if you
        don't wont change firmware in certain slot.

        Pickkit 3 technically has only 5 lines, 6-th is not used for
        programming. Align the connectors first to first pin and leave
        on fly 6-th. MCLR pin on board is first.
        Set up manual device select, select 1.8V midrange family and
        choose needed MCU - PIC16F1827. After that set up LVP programm
        only. Select needed hex file and start programm the MCU.

--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

Sid Boyce
 

Hi Marc,
I was looking for a quick solution in Linux having installed MPLABX-v5.20. Results from just a brief try so I have not yet looked any closer to see if I can discover the reason for the illegal access warning or to try the GUI.

This is what I get using the command line in Linux. Power LED is Green, Active light comes on periodically and Status LED solid Red and after a while changes to Solid Green.
It doesn't complete and come back to the command line.

From lsusb
---------------
Bus 001 Device 025: ID 04d8:900a Microchip Technology, Inc. PICkit3

# java -jar /opt/microchip/mplabx/v5.20/mplab_platform/mplab_ipe/ipecmd.jar -OL -TPPK3 -M -P16F18877 -F./Odyssey_2_MCU.hex
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.openide.util.lookup.implspi.ActiveQueue$Impl (file:/opt/microchip/mplabx/v5.20/mplab_platform/platform/lib/org-openide-util-lookup.jar) to field java.lang.ref.ReferenceQueue.lock
WARNING: Please consider reporting this to the maintainers of org.openide.util.lookup.implspi.ActiveQueue$Impl
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
*****************************************************
Connecting to MPLAB PICkit 3...
Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.51.08 *
Firmware type..............Enhanced Midrange
Now Downloading new Firmware for target device: PIC16F18877
Downloading bootloader
Bootloader download complete
Programming download...
Connection Failed.
73 ... Sid.

On 16/06/2019 07:22, Marc olanie wrote:

… and I will send you a translation for french speaking hams :- )

Thanks Sid

Marc f6itu (still collecting Ody’s components)

*De :*ody-sdr@groups.io <ody-sdr@groups.io> *De la part de* AA6I Stan via Groups.Io
*Envoyé :* samedi 15 juin 2019 21:16
*À :* ody-sdr@groups.io
*Objet :* Re: [ody-sdr] Bootloader update to 2.1

Sid;

*For people like me, a write up would be greatly appreciated. *

Thanks

Stan  AA6I

On 6/14/2019 11:22 PM, Sid Boyce wrote:

Thanks David,
That was the missing part of the puzzle as the ANP.rbf file was
not there when I unzipped the download.

OK on the Pickit3.

*When all done I must do a write-up on all this. *
73 ... Sid.

On 15/06/2019 03:40, David Fainitski wrote:

Hello, Sid
Please understand the difference between bootloader and
working firmware. You can write *Bootloader.rbf into slot 0
ONLY.* Because slot 0 is the starting address of memory, FPGA
dowloads this bootloader code after start.
You can write working firmware like Odyssey_2_1.20_ANP.rbf
into slots 1-3. You can not to write working firmware into
slot 0.
If you will try to do something wrong, the programm wil say
you that file incorrect to avoid problems.

If the bootloader code is damaged in memory, you can return it
with Qartus. After that use Bootloader_2.1.pyw for upload
working firmware to slots 1-3. If you did this before and
slots filled, you don't need to do this more, only if you
don't wont change firmware in certain slot.

Pickkit 3 technically has only 5 lines, 6-th is not used for
programming. Align the connectors first to first pin and leave
on fly 6-th. MCLR pin on board is first.
Set up manual device select, select 1.8V midrange family and
choose needed MCU - PIC16F1827. After that set up LVP programm
only. Select needed hex file and start programm the MCU.

--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

Sid Boyce
 

Thanks,
Got it.
73 ... Sid.

On 15/06/2019 18:54, David Fainitski wrote:
Sid, you can find it in the previous topic https://groups.io/g/ody-sdr/topic/new_firmware_1_20_anp_for/31991146?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,31991146
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

Re: Bootloader update to 2.1

AA6I Stan
 

Thank you in advance.     DE AA6I


On Jun 16, 2019, at 3:28 AM, Isaac <iweksler@...> wrote:

Hi guys.

I decided to help Odyssey-2 users and composed a detailed instruction on programming the MCU by PICKIT-3 and the Bootloader by USB Blaster and Quartus Programmer. This is based on instructions posted by David and others in Russian forums and my personal experients of several tens of programmings I've performed on my Odysey. Hope it will help.

And please look for mistakes which I possibly made. I'll welcome any comments and corrections. Questions as well.

 

73 Isaac 4Z1AO

 

From: ody-sdr@groups.io <ody-sdr@groups.io> On Behalf Of AA6I Stan
Sent: שבת 15 יוני 2019 22:16
To: ody-sdr@groups.io
Subject: Re: [ody-sdr] Bootloader update to 2.1

 

Sid;

 

For people like me, a write up would be greatly appreciated.

 

Thanks

Stan  AA6I

 

 

On 6/14/2019 11:22 PM, Sid Boyce wrote:

Thanks David,
That was the missing part of the puzzle as the ANP.rbf file was not there when I unzipped the download.

OK on the Pickit3.

When all done I must do a write-up on all this.
73 ... Sid.

On 15/06/2019 03:40, David Fainitski wrote:

Hello, Sid
Please understand the difference between bootloader and working firmware. You can write *Bootloader.rbf into slot 0 ONLY.* Because slot 0 is the starting address of memory, FPGA dowloads this bootloader code after start.
You can write working firmware like Odyssey_2_1.20_ANP.rbf into slots 1-3. You can not to write working firmware into slot 0.
If you will try to do something wrong, the programm wil say you that file incorrect to avoid problems.

If the bootloader code is damaged in memory, you can return it with Qartus. After that use Bootloader_2.1.pyw for upload working firmware to slots 1-3. If you did this before and slots filled, you don't need to do this more, only if you don't wont change firmware in certain slot.

Pickkit 3 technically has only 5 lines, 6-th is not used for programming. Align the connectors first to first pin and leave on fly 6-th. MCLR pin on board is first.
Set up manual device select, select 1.8V midrange family and choose needed MCU - PIC16F1827. After that set up LVP programm only. Select needed hex file and start programm the MCU.

 

<Instructions (MCU-BL).docx>

Re: Bootloader update to 2.1

Isaac
 

Hi guys.

I decided to help Odyssey-2 users and composed a detailed instruction on programming the MCU by PICKIT-3 and the Bootloader by USB Blaster and Quartus Programmer. This is based on instructions posted by David and others in Russian forums and my personal experients of several tens of programmings I've performed on my Odysey. Hope it will help.

And please look for mistakes which I possibly made. I'll welcome any comments and corrections. Questions as well.

 

73 Isaac 4Z1AO

 

From: ody-sdr@groups.io <ody-sdr@groups.io> On Behalf Of AA6I Stan
Sent: שבת 15 יוני 2019 22:16
To: ody-sdr@groups.io
Subject: Re: [ody-sdr] Bootloader update to 2.1

 

Sid;

 

For people like me, a write up would be greatly appreciated.

 

Thanks

Stan  AA6I

 

 

On 6/14/2019 11:22 PM, Sid Boyce wrote:

Thanks David,
That was the missing part of the puzzle as the ANP.rbf file was not there when I unzipped the download.

OK on the Pickit3.

When all done I must do a write-up on all this.
73 ... Sid.

On 15/06/2019 03:40, David Fainitski wrote:

Hello, Sid
Please understand the difference between bootloader and working firmware. You can write *Bootloader.rbf into slot 0 ONLY.* Because slot 0 is the starting address of memory, FPGA dowloads this bootloader code after start.
You can write working firmware like Odyssey_2_1.20_ANP.rbf into slots 1-3. You can not to write working firmware into slot 0.
If you will try to do something wrong, the programm wil say you that file incorrect to avoid problems.

If the bootloader code is damaged in memory, you can return it with Qartus. After that use Bootloader_2.1.pyw for upload working firmware to slots 1-3. If you did this before and slots filled, you don't need to do this more, only if you don't wont change firmware in certain slot.

Pickkit 3 technically has only 5 lines, 6-th is not used for programming. Align the connectors first to first pin and leave on fly 6-th. MCLR pin on board is first.
Set up manual device select, select 1.8V midrange family and choose needed MCU - PIC16F1827. After that set up LVP programm only. Select needed hex file and start programm the MCU.