Topics

rbf file programming

Sid Boyce
 

Thanks,
My confusion, no firmware needed.
73 ... Sid.

On 04/07/2019 23:02, David Fainitski wrote:
No, it is two ways of the same.
If you are not be able to write new bootloader.rbf trough pyw, you are forced to do this with Quartus programmer.

The Bootloader.pyw allows you to change bootloader and working firmware.
--
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

David Fainitski
 

No, it is two ways of the same.
If you are not be able to write new bootloader.rbf trough pyw, you are forced to do this with Quartus programmer.

The Bootloader.pyw allows you to change bootloader and working firmware.

Sid Boyce
 

My misunderstanding I thought I had to write both the pof with quartus and rbf with BootLoader_2.2.pyw.
73 ... Sid.

On 04/07/2019 17:17, David Fainitski wrote:
Sid,  bootloafer. rbf can not be written to slots 1-3.
Slots 1-3 are using only for working wirmware.
You can write bootloader to slot 0 only.
But why are you trying to do this if you did it earlier with programmator and Quartus?
--
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

David Fainitski
 

Sid,  bootloafer. rbf can not be written to slots 1-3.
Slots 1-3 are using only for working wirmware. 
You can write bootloader to slot 0 only. 
But why are you trying to do this if you did it earlier with programmator and Quartus? 

Sid Boyce
 

Check of file sizes.
# ls -l /c1/usr/src/XXX/Odyssey_BL_2.2
total 9032
-rw-r--r-- 1 root     root     7029 Jun 29 18:44 BL_2_commands.odt
-rw-r--r-- 1 root     root    18041 Jul  4 16:30 BootLoader_2.2.pyw
-rw-r--r-- 1 root     root  8388811 Jun 29 21:33 Bootloader.pof
-rw-r--r-- 1 root     root   571152 Jun 29 21:33 Bootloader.rbf
-rw-r--r-- 1 lancelot users  253515 Jul  4 16:05 Bootloader_2.2.zip
73 ... Sid.

On 04/07/2019 04:22, David Fainitski wrote:
Hello, Sid
I have found the mistake, please try again with new file.
Don't forget to flash the board with new 2.2 bootloader .pof

FPGA wirmware and PC programm - the pair, both should to have the same version.

This version will write mistakes in console.
--
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

Sid Boyce
 

Wrote Bootloader.pof 100% Success!

Problem with Bootloader.rbf.
73 ... Sid.

On 04/07/2019 04:22, David Fainitski wrote:
Hello, Sid
I have found the mistake, please try again with new file.
Don't forget to flash the board with new 2.2 bootloader .pof

FPGA wirmware and PC programm - the pair, both should to have the same version.

This version will write mistakes in console.
--
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

David Fainitski
 

Hello, Sid
I have found the mistake, please try again with new file.
Don't forget to flash the board with new 2.2 bootloader .pof

FPGA wirmware and PC programm - the pair, both should to have the same version.

This version will write mistakes in console.

Sid Boyce
 

Odyssey_BL_2.1 # python BootLoader_2.0.pyw
No problem with the above, Test of 192.168.10.89 works and finds the device at MAC 00:1e:c0:a6:10:99
73 ... Sid.

On 01/07/2019 12:48, David Fainitski wrote:

[Edited Message Follows]

Hello,  Sid.
Please try to run under console and read the messages if they are presented.
--
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

Sid Boyce
 

Hi David,
I click on Test which turns Green ... nothing happens, no messages.
I have to kill the pid as it is not responsive after clicking on Test.
73 ... Sid.

On 01/07/2019 12:48, David Fainitski wrote:

[Edited Message Follows]

Hello,  Sid.
Please try to run under console and read the messages if they are presented.
--
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

David Fainitski
 
Edited

Hello,  Sid. 
Please try to run under console and read the messages if they are presented.

Sid Boyce
 

I decided to give it a try before bedtime.
"python BootLoader_2.2.pyw" hangs on Test on 192.168.10.89, nmap sees it. That's on x86_64 and ODROID-N2. It can only be killed by CTRL-C or CTRL-ESC-Enter.

slipstream:/c1/usr/src/XXX/Odyssey_BL_2.2 # nmap -sT 192.168.10.0/24
Starting Nmap 7.70 ( https://nmap.org ) at 2019-07-01 00:12 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)
73 ... Sid.

On 30/06/2019 23:54, Sid Boyce via Groups.Io wrote:
OK,
I see BootLoader_2.2.pyw is included.
73 ... Sid.

On 30/06/2019 22:24, David Fainitski wrote:
Hello, Sid

Here is new version 2.2 of bootloader for test. Don't need to change MCU FW after 2.1 version.

Were added couple futures:
Up to 5 tries before fail to avoid missed packets
Sequence number for each packet to avoid double packets

Please try this on your computers.
--
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

Sid Boyce
 

OK,
I see BootLoader_2.2.pyw is included.
73 ... Sid.

On 30/06/2019 22:24, David Fainitski wrote:
Hello, Sid

Here is new version 2.2 of bootloader for test. Don't need to change MCU FW after 2.1 version.

Were added couple futures:
Up to 5 tries before fail to avoid missed packets
Sequence number for each packet to avoid double packets

Please try this on your computers.
--
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

Sid Boyce
 

Thanks David, I'll have a try tomorrow with BootLoader_2.0.pyw
73 ... Sid.

On 30/06/2019 22:24, David Fainitski wrote:
Hello, Sid

Here is new version 2.2 of bootloader for test. Don't need to change MCU FW after 2.1 version.

Were added couple futures:
Up to 5 tries before fail to avoid missed packets
Sequence number for each packet to avoid double packets

Please try this on your computers.
--
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

David Fainitski
 

Hello, Sid

Here is new version 2.2 of bootloader for test. Don't need to change MCU FW after 2.1 version.

Were added couple futures:
Up to 5 tries before fail to avoid missed packets
Sequence number for each packet to avoid double packets

Please try this on your computers. 

Sid Boyce
 

The system where it worked second try is an ODROID-N2 running Ubuntu 18.04.2 LTS aarch64.

All my other boxes are  openSUSE Tumbleweed/Leap 15.1 and Kubuntu 19.04 -- these boxes didn't have a problem with earlier Linux software releases.

Quite likely we'll see the problem reported frequently when others upgrade.

No problem, I'll keep my ODROID-C2, ODROID-N2 and Atomic Pi at Ubuntu 18.04.2 LTS as upgrading to later results in non-bootable systems.
73 ... Sid.

On 25/06/2019 13:35, David Fainitski wrote:

[Edited Message Follows]

According to your exchange log one time Odyssey had not answered to PC program. I don't know why.  May be that packet was blocked by OS.

PC program send a FW to Odyssey with many packets by 512 bytes. Every time Odyssey should to send answer about successful writing to memory previous data for starting next iteration.

Unfortunually I can not repeat this mistake on my system.

But I can try to implement in the PC program second and third trying to write packet if  no answer.

Will think about this.
--
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

Sid Boyce
 

Thanks David,
It is very strange that such a problem only happens now with recent Linux distributions.
The erase seems to work but writing is the problem.

I experienced what seems to be the identical problem with HPSDRProgrammer_web, HPSDRProgrammer_V2 and HPSDRProgrammer_V2_nocap when trying to program hl2b5up.rbf to the Hermes-Lite2. As the EEPROM was erased, the HL2 wouldn't start. I had to use quartus+USBBlaster and hl2b5up.jic instead.
73 ... Sid.

On 25/06/2019 13:35, David Fainitski wrote:
According to your exchange log one time Odyssey had not answered to PC program. I don't know why.  May be that packet was blocked by OS.

PC program send a FW to Odyssey with many packets by 512 bytes. Every time Odyssey should to send answer about successful writing to memory previous data for starting next iteration.

Unfortunually I can not repeat this mistake on my system.

But I can try to implement in the PC program second and third trying to write packet of no answer.

Will think about this.
--
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

David Fainitski
 
Edited

According to your exchange log one time Odyssey had not answered to PC program. I don't know why.  May be that packet was blocked by OS. 

PC program send a FW to Odyssey with many packets by 512 bytes. Every time Odyssey should to send answer about successful writing to memory previous data for starting next iteration. 

Unfortunually I can not repeat this mistake on my system. 

But I can try to implement in the PC program second and third trying to write packet if  no answer. 

Will think about this.

Sid Boyce
 

I left it alone.

I don't know what the problem is except that openSUSE Tumbleweed/Leap 15.1 and Ubuntu 19.04 have the same problem, not only with your python program and ODY-2 but also Hermes-Lite2 with HPSDRProgammer programs.

They all used to work so may be something in the current Linux Networking stack has changed, affecting such programs.
73 ... Sid.

On 24/06/2019 23:11, David Fainitski wrote:
Hi, Sid

A don't know what is the problem. Will leave it as is for now.

David
--
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

David Fainitski
 

Hi, Sid

A don't know what is the problem. Will leave it as is for now.

David

Sid Boyce
 

Hi David,
Same problem on ODROID-N2 first try device -- did not respond in time   --- second try success!.
73 ... Sid.

On 23/06/2019 20:04, Sid Boyce via Groups.Io wrote:
Hi David,
May be there is a problem with current Linux distributions -- openSUSE Leap 15.1/Tumbleweed and Ubuntu 19.04 as I am experiencing similar problems trying to program Hermes-lite2 using HPSDRProgrammer, HPSDRProgrammer_V2 and HPSDRProgrammer_V2_nocap on all the x86_64 boxes.
I wonder if the above and BootLoader_2.0.pyw are no longer compatible with latest distros.

Erase works then when write is attempted, it can't communicate with the SDR.

With Hermes-Lite2 I had to use quartus to program the hl2b5up.jic file as the erase left the HL2 undiscoverable after a number of tries.

I'll try BootLoader_2.0.pyw on ODROID-N2 (ARM64) and Atomic PI (x86_64), both with Ubuntu 18.04.2.
73 ... Sid.



On 22/06/2019 04:12, David Fainitski wrote:
Hello, Sid

Please try this bootloader.pof
--
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