Page 1 of 1
Updating ZX firmware
Posted: 17 April 2006, 6:32 AM
by DH*
How long should it take to update the ZX firmware? I used the IDE option with zx24_1-1-6.zvm.
My red LED is constant, my green LED has been flashing slowly and the IDE has been frozen for several minutes now.
UPDATE: After 10 minutes or so I disregarded the dire warnings of doom, powered down the ZX-24 and used the three-finger salute on the IDE.
Fortunately the ZX-24 was still running the factory test app.
I tried updating the ZX firmware from the command line with the same result. The red LED is constant, the green LED is flashing and there is a single dot in the DOS window. Here's hoping it will survive another power cycle.
UPDATE2: No such luck. The second power cycle scrambled its brains. Here's hoping the emergency rescue procedure works.
BTW, is there a copy of the factory test application available for download? I always used the one from NetMedia as a test after glitches like this.
Posted: 17 April 2006, 7:13 AM
by mikep
The firmware update seems to flash the green LED at a constant rate irrespective of what is happening with the download itself. The way you know it is working it that a period appears on the IDE console for each 1% complete. There are four lines of periods with a percent count that goes something like 26%, 51%, 77%, 100%. These are not equal 25% portions but that doesn't really matter.
I think you have three options:
1. Retry the firmware download again. If you cannot download programs and the ZX runtime is stuck then you need to go to option 2.
2. Do an emergency update (see
http://www.zbasic.net/doc/ZBasicRef/ZBasicRef92.html)
3. If the emergency update doesn't work then Don will need to help with getting you a replacement.
UPDATE: I don't get emails for your updates. So judging by your latest append, it looks like you are now on option 2. The factory installed program is somewhat similar to the first example program in the ZBasic reference. It doesn't realy matter too much what it is providing is sends debug lines to the console and flashes the LEDs.
Posted: 17 April 2006, 7:51 AM
by dkinzer
An update normally takes several minutes. If the progress indicator is not advancing then something has gone awry.
The "Hello" program installed in manufacturing is:
Code: Select all
Private msg as StringVectorData({ "ZX-24 says...", " Hello, world!" })
Sub Main()
Dim j as Integer
j = 0
Do
Call Hello(j)
j = (j + 1) And 1
Loop
End Sub
Sub Hello(ByVal idx as Integer)
Debug.Print msg(idx + 1)
Call PutPin(25, 0)
Call Delay(0.5)
Call PutPin(25, 1)
Call PutPin(26, 0)
Call Delay(0.5)
Call PutPin(26, 1)
End Sub
Posted: 17 April 2006, 8:18 AM
by DH*
I'm confused by the emergency update procedure. The example in the docs reads...
- zload –c2 –e zvm_1-12.zpd
What is
zvm_1-12.zpd?
If ever I get this working again would it be possible to revise zload.exe so I can pass a handle to a window on the command line that it will send % complete updates to so I can call zload.exe from my Windows application and provide a progress window. I think it makes things less confusing for end users of the applications I create.
Posted: 17 April 2006, 12:28 PM
by dkinzer
What is zvm_1-12.zpd?
The extension should be .zvm. The update file is the same whether you use the "normal" or the "emergency" update.
[W]ould it be possible to revise zload.exe so I can pass a handle to a window on the command line...
Perhaps so. Alternatively, since the source code for zload.exe is available on your system you could integrate the code and make it look exactly like you want it to look. You can find the source code at */source/zload/zload.c where * is the directory where you installed ZBasic.
Posted: 17 April 2006, 13:31 PM
by DH*
dkinzer wrote:The extension should be .zvm. The update file is the same whether you use the "normal" or the "emergency" update.
The emergency procedure worked and I was pleasantly suprised to see the
Hello app was intact but I have to say this whole experience leaves me a bit uneasy. How often does an update fail via the IDE or command line?
I have quite an assortment of jumpers with various clips but I found I had to solder a machined pin SIP socket to the SPI pads in order to make the necessary emergency connections. I am reluctant to suggest that to folks who may build my DIY applications.
Alternatively, since the source code for zload.exe is available on your system you could integrate the code and make it look exactly like you want it to look.
I write my Windows apps using VB4-32 so I'm not sure the C code will be of much help. I will look at it.
Posted: 17 April 2006, 15:21 PM
by dkinzer
How often does an update fail via the IDE or command line?
So far, there has been only one other instance that I recall. Unfortunately, it is difficult, if not impossible, to ascertain what caused the failure. The emergency update procedure was implemented because it seemed likely that it would be useful from time to time.
I have quite an assortment of jumpers with various clips but I found I had to solder a machined pin SIP socket to the SPI pads in order to make the necessary emergency connections.
I've used jumpers with
E-Z Mini Hooks, available at Digi-Key and elsewhere. The Micro Hook might work even better.
Posted: 17 April 2006, 17:00 PM
by DH*
dkinzer wrote:I've used jumpers with
E-Z Mini Hooks, available at Digi-Key and elsewhere. The Micro Hook might work even better.
My mini-hooks must be less mini than yours. I guess I'll need micros for a microcontroller.
it is difficult, if not impossible, to ascertain what caused the failure
It is indeed somewhat strange that the same hardware that failed with both IDE and command line works with the emergency hookup.
