Finished another 2000 (two thousands) writes/reads full hex operations on OP v0.11.0 (w/ modifications), this time running on a Single Core Raspberry PI ZERO!
1000 hex writes, followed by a 1000 flash reads, logs saved, checked: ALL OK!
Alternating 2 different binary hexes, so to help catch errors if they happens...
EVERYTHING 100% SUCCESS!
Zero errors!
Just mentioning again, below, a description about changes to the "op.c" file, introducing timming delays, so that it can run on RPI3 and RPIZero without USB communication problems...
File: "op.c" version v0.11.0
[1. lines 648 to 651, commented]
if(v==0){
PrintMessage(strings[S_lowUsbV]); //"Tensione USB troppo bassa (VUSB<4.5V)\r\n"
return 0;
}
changed to
//if(v==0){
// PrintMessage(strings[S_lowUsbV]); //"Tensione USB troppo bassa (VUSB<4.5V)\r\n"
// return 0;
//}
[2. line 657, changed the 1500 to 3000]
for(;(v<(vreg/10.0-1)G||v>(vreg/10.0+1)G)&&t<t0+1500;t=GetTickCount()){
changed to
for(;(v<(vreg/10.0-1)G||v>(vreg/10.0+1)G)&&t<t0+3000;t=GetTickCount()){
[3. line 928, commented, added 1 line after]
usleep(x>MinDly?x:MinDly);
changed to
//usleep(x>MinDly?x:MinDly);
usleep(15000); //add this line after the 928, 15000 = 15 miliseconds
Change 3 add a 15 miliseconds between a write to USB and a read USB.
Control Device ("PC"): Raspberry PI Zero HW
OP Version: v0.11.0 CLI - command line interface
Firmware: v0.11.0
External Powered USB Hub: 2500 mA
Target MCU: PIC 12F1822 I/P
Now I am considering a "long run" on RPI Zero...
Since this particular PIC12F is already around 3000 writes cycles, I am considering the idea to run a full non-stop 7000 writes and 7000 reads, then, get all the output docs and publish the results...
Since Microchip states that 10000 write cycles is the minimum lifetime for this kind of MCU, we can run it to around this number and document what we get...
Before deciding about it, I have to take a better look at the control code and firmware routines, also need a better pair of hexes beyond the blink-led...
In anyway, I am quite happy with the PI3 and PIZero results, since this kind of setup is what I was hoping as preferred way to use OP, dedicated device...
For my current expectations and needs, the 2000 + 2000 operations are enough of "objective evidence" that the device and the software can work with the little SBCs...
Regards all,
Valter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So you are stressing the device as well as the programming platform.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-04-13
8000 HEX writes/reads, 100%!
Just completed 8000 HEX writes and reads without a single issue!
Tests can go way better but at least I now have a pattern of behavior
from OP running on the Raspberry PI Zero and PI 3, and if I found
any deviation from this pattern, then I know there is something
"out of place"...
For people that may also be interested in running OP with a SBC,
I believe these results are very encouraging, especially considering
that the RPI Zero is Single Core ARMv6 and powered by a 32Bits OS.
RPI Zero HW
12F1822 - 2000 HEX writes/reads batch - 100% OK
12F1501 - 2000 HEX writes/reads batch - 100% OK
16F18313 - 2000 HEX writes/reads batch - 100% OK
Two different alternated HEX files for each MCU type.
LOGs checked for errors.
LOGs checked for corrected DeviceID.
Readed HEXes cheched with md5sum.
Total: 8000 HEX writes/reads - 100% OK, no errors!
Both PIs Operating Systems are, 32Bits Raspbian.
OP Command Line: Version 0.11.0 (w/ timming delay modifications)
Firmware 0.11.0, recompiled for 20MHz Oscillator, 18F2550
External Powered USB Hub with 2500 mA.
Regards,
Valter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Finished another 2000 (two thousands) writes/reads full hex operations on OP v0.11.0 (w/ modifications), this time running on a Single Core Raspberry PI ZERO!
1000 hex writes, followed by a 1000 flash reads, logs saved, checked: ALL OK!
Alternating 2 different binary hexes, so to help catch errors if they happens...
EVERYTHING 100% SUCCESS!
Zero errors!
Just mentioning again, below, a description about changes to the "op.c" file, introducing timming delays, so that it can run on RPI3 and RPIZero without USB communication problems...
File: "op.c" version v0.11.0
[1. lines 648 to 651, commented]
if(v==0){
PrintMessage(strings[S_lowUsbV]); //"Tensione USB troppo bassa (VUSB<4.5V)\r\n"
return 0;
}
changed to
//if(v==0){
// PrintMessage(strings[S_lowUsbV]); //"Tensione USB troppo bassa (VUSB<4.5V)\r\n"
// return 0;
//}
[2. line 657, changed the 1500 to 3000]
for(;(v<(vreg/10.0-1)G||v>(vreg/10.0+1)G)&&t<t0+1500;t=GetTickCount()){
changed to
for(;(v<(vreg/10.0-1)G||v>(vreg/10.0+1)G)&&t<t0+3000;t=GetTickCount()){
[3. line 928, commented, added 1 line after]
usleep(x>MinDly?x:MinDly);
changed to
//usleep(x>MinDly?x:MinDly);
usleep(15000); //add this line after the 928, 15000 = 15 miliseconds
Change 3 add a 15 miliseconds between a write to USB and a read USB.
Control Device ("PC"): Raspberry PI Zero HW
OP Version: v0.11.0 CLI - command line interface
Firmware: v0.11.0
External Powered USB Hub: 2500 mA
Target MCU: PIC 12F1822 I/P
Now I am considering a "long run" on RPI Zero...
Since this particular PIC12F is already around 3000 writes cycles, I am considering the idea to run a full non-stop 7000 writes and 7000 reads, then, get all the output docs and publish the results...
Since Microchip states that 10000 write cycles is the minimum lifetime for this kind of MCU, we can run it to around this number and document what we get...
Before deciding about it, I have to take a better look at the control code and firmware routines, also need a better pair of hexes beyond the blink-led...
In anyway, I am quite happy with the PI3 and PIZero results, since this kind of setup is what I was hoping as preferred way to use OP, dedicated device...
For my current expectations and needs, the 2000 + 2000 operations are enough of "objective evidence" that the device and the software can work with the little SBCs...
Regards all,
Valter
So you are stressing the device as well as the programming platform.
8000 HEX writes/reads, 100%!
Just completed 8000 HEX writes and reads without a single issue!
Tests can go way better but at least I now have a pattern of behavior
from OP running on the Raspberry PI Zero and PI 3, and if I found
any deviation from this pattern, then I know there is something
"out of place"...
For people that may also be interested in running OP with a SBC,
I believe these results are very encouraging, especially considering
that the RPI Zero is Single Core ARMv6 and powered by a 32Bits OS.
RPI Zero HW
12F1822 - 2000 HEX writes/reads batch - 100% OK
12F1501 - 2000 HEX writes/reads batch - 100% OK
16F18313 - 2000 HEX writes/reads batch - 100% OK
Two different alternated HEX files for each MCU type.
LOGs checked for errors.
LOGs checked for corrected DeviceID.
Readed HEXes cheched with md5sum.
RPI 3 B+
12F1822 - 2000 HEX writes/reads batch - 100% OK
Total: 8000 HEX writes/reads - 100% OK, no errors!
Both PIs Operating Systems are, 32Bits Raspbian.
OP Command Line: Version 0.11.0 (w/ timming delay modifications)
Firmware 0.11.0, recompiled for 20MHz Oscillator, 18F2550
External Powered USB Hub with 2500 mA.
Regards,
Valter