"TeseoSuitePro_6_1_3" suite firmware bin correct? STA8090_v4.5.12.1_D1

[Dror]

I have the "TeseoSuitePro_6_1_3" suite. It comes with installed bin files for STA8089GAT. After I flash the firmware that arrives with the tool I get the tool to start , it sees the GPS satellites with good levels but it never gets a fix. I am also able to configure it to see Galileo but still no fix. What is wrong? is it a bad firmware? The suite reports: STA8090_v4.5.12.1_D1

Also mentioning our flash device is a 128M part MX25U12835FBBI-10G

[Francesco Virlinzi]

Hi

It seems to me the system is not saving the ephemeris data in the flash, due to that with empty ephemeris you'l never get a fix (also if you see good signal levels)

Which SPI flash are you using?

Thansk

Regards

Francesco

[Dror]

We are aware that the flash we are using is not in the recommended devices list.

Our flash device is a 128M part MX25U12835FBBI-10G

Is these a way to verify or change a configuration to enable it to work?

It is strange as we are fashing the firmware on it and it is loading.

[Francesco Virlinzi]

Hi

During the booting from SPI/SQI the application enables also the flash protection to avoid corruption of the binary code.

Just for test could you try setting CDB-250 = 0x8000000A (do that in the original binary and reflash from zero)

It's the value required for MX25U1635E / MX25U1635F.

Let see if it works also for MX25U12835FBBI-10G

Hope this helps

Regards

Francesco

[Dror]

Hi Francesco,

Sorry for being a newbie here.

Could you please guide me how exactly do I set it in the original binary?

Thank YOU!

[Dror]

The SPM table for the 128M flash we use looks different than the 32M device.

See below table from 128M flash device:

[Francesco Virlinzi · Accepted solution]

In Teseo-Suite:

Menu-Tools -> FW Configuration -> Read bin image configuration

It will open a panel where you can to provide the original firmware and from that it will generate a txt file with the whole configuration (save the file like cfg.txt)

The text file is

100 -> 00

101 -> 02

...

it means CDB-100 equals 00... CDB-101 eqral 02 etc...

in the cfg.txt file change the line (CDB) 249:

it is like:

249 -> 00000001

it has to be changed in

249 -> 00000000

save the file like new_cfg.txt

Now again in the Teseo-Suite:

Menu-Tools -> FW Configuration -> Writebin image configuration

in this panel providing:

• a binary firmware
• a text configuration file (the new_cfg.txt jsut saved)

it generates a new firmware which embeds the new configuration.

reflash the new binary in the device.

Take care that I'm suggesting the CDB-249 (not 250) to totally disable the flash protection.

Let me know

CIao

Francesco

[Dror]

Hi,

You advise gave us the clues we needed.

I actually changed only CDB-250 to 00000015 and now we have a fix. CDB-249 has the default value (enabled).

Is that a good setting?

Thank you.

[Francesco Virlinzi]

Hi

This confirm the issue was related to the flash-protection.

> CDB-250 to 00000015

To be honest I was thinking to 0xA because the values for MX25U1635E/MX25U1635F

Why are you using 0x15?

> Is that a good setting?

I don't know. You are using an un-tested SQI-flash.

Personally I would suggest... keep it running for a long time.... and try also standby operations.

Just a question: why are you using an unsupported memory?

Thanks

Regards

Francesco

[Dror]

In the document "SQI flash protection application note" it is shown further down the table that Macronix MX25L3233F and similar parts, also with the T/B field, use the 0x15 value. The MSB bit has to be '0' otherwise the lower byte value is ignored (a NOTE in the firmware guide: "when enabled the value configured in B0..B30 is not used").

This was an initial design that used 1.8V i/o and the 128M flash part was readily available.

We will not use this flash in future designs.