Unable to flash new firmware

2 views
Skip to first unread message

Eric Christopherson

unread,
Jul 8, 2016, 10:08:32 AM7/8/16
to uIEC-...@googlegroups.com
I seem to have gotten my device into a state where I can't flash any new firmware. Right now my version string (disk status) is "73,sd2iec v1.0.0.1ALPHA0,00,00"; I believe this version resulted from me flashing something identical to commit aa8395c in sd2iec, except that I bumped the fix number to 1.

I've tried flashing several other firmwares:
1. additional small modifications to aa8395c
2. official release sd2iec-0.10.3-uIEC3-m1281.bin
3. official alpha sd2iec-1.0.0alpha0-98-gaa8395c-uIEC3-m1281.bin
4. h2obsession's old fast-serial version uIEC-firmware-0.8.291.bin

Any idea how I can get it working again?

--
        Eric Christopherson

RETRO Innovations

unread,
Jul 8, 2016, 1:15:47 PM7/8/16
to uIEC-...@googlegroups.com
On 7/8/2016 9:08 AM, Eric Christopherson wrote:
I seem to have gotten my device into a state where I can't flash any new firmware. Right now my version string (disk status) is "73,sd2iec v1.0.0.1ALPHA0,00,00"; I believe this version resulted from me flashing something identical to commit aa8395c in sd2iec, except that I bumped the fix number to 1.
Try bumping to .2 fix level and try again.

It should not matter, but if it works, then we will have another data point to consider.

THe bootloader should flash the first file it finds that is either a dev version (all 0s for version number) or a higher version than the current one.   So, no matter what, the bootloader should take alpha firmware at all times.

Jim


I've tried flashing several other firmwares:
1. additional small modifications to aa8395c
2. official release sd2iec-0.10.3-uIEC3-m1281.bin
3. official alpha sd2iec-1.0.0alpha0-98-gaa8395c-uIEC3-m1281.bin
4. h2obsession's old fast-serial version uIEC-firmware-0.8.291.bin

Any idea how I can get it working again?

--
        Eric Christopherson
--
You received this message because you are subscribed to the Google Groups "µIEC Users Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uIEC-users+...@googlegroups.com.
To post to this group, send email to uIEC-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/uIEC-users/CADyB93C5bvNiSuqtGpjryet9RhOmZOfe4ALEEWbFoqdmW9Zm%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


-- 
RETRO Innovations, Contemporary Gear for Classic Systems
www.go4retro.com
store.go4retro.com

Eric Christopherson

unread,
Jul 8, 2016, 1:44:20 PM7/8/16
to uIEC-...@googlegroups.com
On Fri, Jul 8, 2016 at 12:15 PM, RETRO Innovations <go4r...@go4retro.com> wrote:
On 7/8/2016 9:08 AM, Eric Christopherson wrote:
I seem to have gotten my device into a state where I can't flash any new firmware. Right now my version string (disk status) is "73,sd2iec v1.0.0.1ALPHA0,00,00"; I believe this version resulted from me flashing something identical to commit aa8395c in sd2iec, except that I bumped the fix number to 1.
Try bumping to .2 fix level and try again.

It should not matter, but if it works, then we will have another data point to consider.

THe bootloader should flash the first file it finds that is either a dev version (all 0s for version number) or a higher version than the current one.   So, no matter what, the bootloader should take alpha firmware at all times.

I've already changed the FIX variable from 1 to 2, 3, and now 4. I have:

    # Define version number
    MAJOR = 1
    MINOR = 0
    PATCHLEVEL = 0
    FIX = 4
    
    # Forces bootloader version to 0, comment out or leave empty for release
    PRERELEASE = alpha0

I was under the understanding that the PRERELEASE variable here actually worked to make the version "act like" it was 0.0.0.0; but, just in case, I decided to hard code all the version numbers to 0. That didn't result in success either (with PRERELEASE commented out or not).

I've been using usb_modeswitch (Linux command) to power-cycle the hub the uIEC is hooked up to, after writing the firmware. I'm writing the firmware onto a FlashAir card I just got, via wifi. Probably something isn't behaving correctly with one of those steps in the chain; I will have to really investigate once I get home.

Slightly off the subject: what would cause the "alpha0" in the Makefile.main to get converted to all-caps (=all graphics chars when viewing files from a Commodore)? I seem to remember that the first time I flashed an alpha version, its version designation had "alpha" in lower case. Also, I wonder how one would make the version number show the Git commit, the way the current download from sd2iec.de does.
 

Jim


I've tried flashing several other firmwares:
1. additional small modifications to aa8395c
2. official release sd2iec-0.10.3-uIEC3-m1281.bin
3. official alpha sd2iec-1.0.0alpha0-98-gaa8395c-uIEC3-m1281.bin
4. h2obsession's old fast-serial version uIEC-firmware-0.8.291.bin

Any idea how I can get it working again?

--
        Eric Christopherson
--
You received this message because you are subscribed to the Google Groups "µIEC Users Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uIEC-users+...@googlegroups.com.
To post to this group, send email to uIEC-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/uIEC-users/CADyB93C5bvNiSuqtGpjryet9RhOmZOfe4ALEEWbFoqdmW9Zm%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


-- 
RETRO Innovations, Contemporary Gear for Classic Systems
www.go4retro.com
store.go4retro.com

--
You received this message because you are subscribed to the Google Groups "µIEC Users Discussion Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uIEC-users+...@googlegroups.com.
To post to this group, send email to uIEC-...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
        Eric Christopherson

Eric Christopherson

unread,
Jul 8, 2016, 2:03:49 PM7/8/16
to uIEC-...@googlegroups.com
I've been using usb_modeswitch (Linux command) to power-cycle the hub the uIEC is hooked up to, after writing the firmware. I'm writing the firmware onto a FlashAir card I just got, via wifi. Probably something isn't behaving correctly with one of those steps in the chain; I will have to really investigate once I get home.

Yeah, it was the routine I was using to upload firmware; it was including some extra HTTP request nonsense in the file itself. Sorry to ask before checking that first.

--
        Eric Christopherson

Ingo Korb

unread,
Jul 9, 2016, 5:19:14 AM7/9/16
to uIEC-...@googlegroups.com
Eric Christopherson <echrist...@gmail.com> writes:

> Slightly off the subject: what would cause the "alpha0" in the
> Makefile.main to get converted to all-caps (=all graphics chars when
> viewing files from a Commodore)?

The C64's character set (usually called PETSCII) differs from ASCII, to
a first-order approximation the upper and lower case characters are
swapped. It's annoying to correct that at compile-time with either make or
the C preprocessor, so the string is just passed along as-is.

> Also, I wonder how one would make the version number show the Git
> commit, the way the current download from sd2iec.de does.

That happens in the auto-builder script that I run on my server, it uses
"git describe" to get the number and overrides some make variables on
the command line to make sure they are compiled into the binary.

-ik

Eric Christopherson

unread,
Jul 9, 2016, 9:24:16 PM7/9/16
to uIEC-...@googlegroups.com
On Sat, Jul 09, 2016, Ingo Korb wrote:
> Eric Christopherson <echrist...@gmail.com> writes:
>
> > Slightly off the subject: what would cause the "alpha0" in the
> > Makefile.main to get converted to all-caps (=all graphics chars when
> > viewing files from a Commodore)?
>
> The C64's character set (usually called PETSCII) differs from ASCII, to
> a first-order approximation the upper and lower case characters are
> swapped. It's annoying to correct that at compile-time with either make or
> the C preprocessor, so the string is just passed along as-is.

Yes, I understand that. But I could have sworn the first time I
installed an alpha firmware, the word alpha was in lower case; that is
no longer true, so I wondered what made the difference.

>
> > Also, I wonder how one would make the version number show the Git
> > commit, the way the current download from sd2iec.de does.
>
> That happens in the auto-builder script that I run on my server, it uses
> "git describe" to get the number and overrides some make variables on
> the command line to make sure they are compiled into the binary.

Oh, that script isn't part of the repository. OK.

--
Eric Christopherson

Greg King

unread,
Jul 10, 2016, 4:34:07 AM7/10/16
to µIEC Users Discussion Group
On Saturday, July 9, 2016 at 9:24:16 PM UTC-4, Eric Christopherson wrote:
On Sat, Jul 09, 2016, Ingo Korb wrote:
> Eric Christopherson writes:
>
> > Slightly off the subject: what would cause the "alpha0" in the
> > Makefile.main to get converted to all-caps (= all graphics chars when
> > viewing files from a Commodore)?
>
> The C64's character set (usually called PETSCII) differs from ASCII; to
> a first-order approximation, the upper- and lower-case characters are
> swapped. It's annoying to correct that at compile-time with either make or
> the C preprocessor; so, the string just is passed along as-is.

Yes, I understand that. But, I could have sworn the first time I
installed an alpha firmware, the word alpha was in lower case; that is
no longer true; so, I wondered what made the difference.

That string might have been converted from upper-case ASCII to lower-case ASCII.

Eric Christopherson

unread,
Jul 12, 2016, 2:14:32 PM7/12/16
to uIEC-...@googlegroups.com
Yes, clearly. I just wasn't sure if that was done automatically as part of the make process, or if Ingo (or whoever uploaded the binary I installed) converted it outside of the process that's in the official repository.

--
        Eric Christopherson

Daniel V. Mackey

unread,
Jul 12, 2016, 5:03:38 PM7/12/16
to uIEC-...@googlegroups.com
At 04:59 PM 7/12/2016, you wrote:

Try HEX editing that string if you can find it in the file and you will get your answer.

 
> That string might have been converted from upper-case ASCII to lower-case
> ASCII.
 
Yes, clearly. I just wasn't sure if that was done automatically as part of
the make process, or if Ingo (or whoever uploaded the binary I installed)
converted it outside of the process that's in the official repository.
 
--
Eric Christopherson
Back to top
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to uIEC-users+...@googlegroups.com.

---
WWW: http://www.commodoredungeon.com

QUOTE : "A Clean bench is a sign of a weak mind."

Reply all
Reply to author
Forward
0 new messages