GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — PineStore announcement : the current flash chip is EoL, a new one will be used for future PineTime batches · Issue #2096 · InfiniTimeOrg/InfiniTime

PineStore announcement : the current flash chip is EoL, a new one will be used for future PineTime batches #2096

New issue
Copy link
New issue
Copy link
Closed
#2097
Closed
PineStore announcement : the current flash chip is EoL, a new one will be used for future PineTime batches#2096
#2097
Copy link
Labels
external flash

Description

@JF002
JF002
opened on Jul 21, 2024
Issue body actions

Verification

  • I searched for similar issues (including closed issues) and found none was relevant.

Introduce the issue

I've just received this information from TL Lim from PineStore : the current SPI flash memory chip (XTX XT25F32B) is EoL (end of life) and will be replaced by another one : BY25Q32ESWIG.

Here is the datasheet : BY25Q32ESWIG-03.A.02.00372.pdf

The only change expected on the software point of view are the JEDEC IDs :

Chip Manufacturer Memory type Density
XTX XT25F32B 0x0B 0x40 0x16
BY25Q32ESWIG 0x68 0x40 0x16

PineStore asked me to provide them with a new firmeware that supports this new chip.

Feel free to forward this announcement to all firmware developers that might be interested to support this new flash chip!

Preferred solution

At first sight, no change should be necessary in InfiniTime, since it does not check the IDs (it only logs the value, but does not fail if they are not the ones that were expected).

However, the SPI flash driver in the bootloader will most probably fail since those IDs are specified and checked at boot time.

Since the bootloader is a very critical part of the project, please feel free to cross-check my analysis and also test and provide feedback when a new version of the bootloader will be available :)

Version

1.14.0

Activity

  1. JF002
    added
    external flash
    on Jul 21, 2024
  2. JF002
    closed this as completedin #2097on Aug 5, 2024
  3. SteveAmor commented on Aug 28, 2024

    @SteveAmor
    SteveAmor
    on Aug 28, 2024
    Contributor
    More actions

    Do you think there are going to be any issues with people who receive one of these new PTs and flash the bootloader to use WASPOS and then use the process/file to flash back to Infinitime?

  4. JF002 commented on Sep 1, 2024

    @JF002
    JF002
    on Sep 1, 2024
    CollaboratorAuthor
    More actions

    @SteveAmor This is a very good question! According to TL Lim and my observations, the new chip behaves exactly the same way than the old one, so no code change should be needed except if the bootloader/reloader checks the chip IDs of the memory chip.
    Do you know if this announcement has reached the WaspOS development team?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    external flash

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.