Jump to content
IGNORED

FujiNet Update Flasher Problem


Recommended Posts

Figured I'd post this here, as I'm having the same problem, but on one of the newer v1.3 FujiNets:

 

I tried holding down the A button, but it doesn't make a difference. Looking at the logs, it looks like it's still trying to enter flash mode.

 

One point I didn't make, for what it's worth, when it's trying to flash, all three lights are blinking - bright.. dim.. off.. bright.. dim... etc.

 

Link to comment
Share on other sites

48 minutes ago, tsom said:

I tried holding down the A button, but it doesn't make a difference. Looking at the logs, it looks like it's still trying to enter flash mode.

Unplug USB from the FujiNet, hold A button and plug in USB cable to FujiNet. All the lights should turn on dim. Then try to flash. If you have another cable, try it too (even though this one works with your other FujiNet). 

Link to comment
Share on other sites

38 minutes ago, mozzwald said:

Unplug USB from the FujiNet, hold A button and plug in USB cable to FujiNet. All the lights should turn on dim. Then try to flash. If you have another cable, try it too (even though this one works with your other FujiNet). 

That’s what I meant, I tried that, didn’t make a difference. I did try another cable but no go. The cable I’m using flashes my original FujiNet just fine. 

Link to comment
Share on other sites

1 minute ago, tsom said:

That’s what I meant, I tried that, didn’t make a difference. I did try another cable but no go. The cable I’m using flashes my original FujiNet just fine. 

Can you try the attached flash tool which slows the baud rate down when flashing? The FujiNet is communicating with the computer since it's showing the debug output, it's just having a problem with flashing for some reason.

FujiNet-Flasher-macos_slow.zip

Link to comment
Share on other sites

8 hours ago, mozzwald said:

Can you try the attached flash tool which slows the baud rate down when flashing? The FujiNet is communicating with the computer since it's showing the debug output, it's just having a problem with flashing for some reason.

FujiNet-Flasher-macos_slow.zip 14.14 MB · 1 download

Nope.

Using '/dev/cu.usbserial-1410' as serial port.
Starting firmware upgrade...
Getting latest firmware from fujinet.online..
FujiNet Version: 0.5.89f318f9
Version Date/Time: 2020-12-29 01:50:02
Build Date/Time: Tue Dec 29 02:53:03 UTC 2020
Connecting...[06:59:56]ets Jul 29 2019 12:21:46
[06:59:56]
[06:59:56]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[06:59:56]configsip: 0, SPIWP:0xee
[06:59:56]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[06:59:56]mode:DIO, clock div:2
[06:59:56]load:0x3fff0030,len:4
[06:59:56]load:0x3fff0034,len:5524
[06:59:56]load:0x40078000,len:16488
[06:59:56]load:0x40080400,len:4840
[06:59:56]entry 0x400806a4
.....[06:59:58]Nqƥets Jul 29 2019 12:21:46
[06:59:58]
[06:59:58]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[06:59:58]configsip: 0, SPIWP:0xee
[06:59:58]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[06:59:58]mode:DIO, clock div:2
[06:59:58]load:0x3fff0030,len:4
[06:59:58]load:0x3fff0034,len:5524
[06:59:58]load:0x40078000,len:16488
[06:59:58]load:0x40080400,len:4840
[06:59:58]entry 0x400806a4
_Serial port closed!
____....._____....._____....._____....._____....._____....._____
Unexpected error: ESP Chip Auto-Detection failed: Failed to connect to Espressif device: Invalid head of packet (0xC2)

I'll try to dig up another cable and try...

Link to comment
Share on other sites

  • 4 weeks later...
On 12/9/2020 at 9:45 AM, mozzwald said:

The board is supposed to automatically enter flash mode when you press "Flash FujiNet Firmware", but you can force it into flash mode by holding Button A (far left) when you plug in the USB cable, then run the flash tool.

This worked for me on my non-modded Atari 800XL. Thank you!

 

PROBLEM: Prior attempts (MacOS and Windows64) to use #fujinet flasher to update firmware version 0.5.8934daff failed due to: 

                "Unexpected error: ESP Chip Auto-Detection failed: Failed to connect to Espressif device: Timed out waiting for packet header"

 

SOLUTION: Forcing into flash mode by holding button-A when I plugged in the USB cable did the trick. 

 

With the older firmware my #fujinet was hanging on the "MOUNT AND BOOT" blue screen, and then dropping down into AtariOS BASIC "Ready" mode. I was unable to launch anything.

 

Now it seems to work properly as I've launched a few games from the internet. How great! 

 

 

  • Thanks 1
Link to comment
Share on other sites

  • 2 weeks later...

For anyone having trouble flashing their FujiNet device, please follow this procedure:

1. Plug FujiNet into computer with MicroUSB cable
2. Run FujiNet Flasher
3. Select COM port of FujiNet device
4. Click "Flash FujiNet Firmware" and immediately press and HOLD button A
6. Continue holding button A until you see "Erasing flash (this may take a while)", then release button A
7. Wait for it to finish flashing and you're done

 I was able to get a Windows 7 computer that could not flash any FujiNet I plugged into it and this process worked every time.

  • Thanks 1
Link to comment
Share on other sites

  • 5 months later...

Hi just to add to this thread, Ive just received my 2nd Fujinet 1.5 but this time i bought an XE version for the 130 XE and my previous one is the XL version.

I went to update the XE version and i kept getting this error Using 'COM3' as serial port.
Starting firmware upgrade...
Getting latest firmware from fujinet.online..
FujiNet Version: 0.5.bbbb9f96
Version Date/Time: 2021-07-17 23:14:15
Build Date/Time: Sat Jul 17 23:40:30 UTC 2021
Connecting........_____....._____....._____....._____....._____....._____....._____
Unexpected error: ESP Chip Auto-Detection failed: Failed to connect to Espressif device: Timed out waiting for packet header

 

The blue light would slowly flash on the XE version but then reported this error? So i had to force the Fujinet in to flash mode which then works great. So when updating the XL version as soon as i clicked the flash firmware on the flasher the Fujinet went straight in to flash mode and updated.

 

So in future i think i might have to force the XE version in to flash mode pressing the A button whilst plugging in the usb cable to the Fujinet?

 

I got worried when i kept getting the error? But all is ok and both Fujinets are up to date :)

Link to comment
Share on other sites

version 1.5 should be version 1.5 regardless of what enclosure it is housed in... are we re-arranging something to but it in a different style case? I wasn't aware of that being the situation.  Could be interesting to note the differences of internal fixes/bodges/ or chip manufacturers... would be nice to pin down what's making these differences.

Link to comment
Share on other sites

9 hours ago, Back2skooldaze said:

So in future i think i might have to force the XE version in to flash mode pressing the A button whilst plugging in the usb cable to the Fujinet?

This will always put the FujiNet into flashing mode and you can do it if needed. It's interesting that you have to do this with one v1.5 and not the other. Are you using the same USB cable & computer to flash both FujiNets? Makes me think there's a (minor) hardware issue, but it if you can flash by force, then it should be ok.

7 hours ago, _The Doctor__ said:

version 1.5 should be version 1.5 regardless of what enclosure it is housed in... are we re-arranging something to but it in a different style case? I wasn't aware of that being the situation.  Could be interesting to note the differences of internal fixes/bodges/ or chip manufacturers... would be nice to pin down what's making these differences.

Case makes no difference on the guts. All the differences between versions have been and still are on the Wiki in addition to the README files for each version in the fujinet-hardware repo.

  • Like 1
Link to comment
Share on other sites

as pointed out the guts should be identical, the case is purely aesthetics. If they are acting differently, then the build of the PCB may have differences in the chips/components the vendor has used... so knowing which is working as it should and which is not needs the comparison so it may be tracked down as to what is causing the issue.

Link to comment
Share on other sites

  • 1 month later...

Hi,

 

we tried to update an actual Funjinet (1.5). One unit was no problem, another unit first doesn´t go into update mode.
We forced entering update-mode by pressing "A"-button and powering up fujinet.
Then we can update it, but after update, the last message in the console-window looks like this:

Leaving...
Hard Resetting...
Done! Flashing is complete!

 

Connected to the XLs SIO-plug again, the computer doesn´t boot the Fujinet-software anymore...


Updating another Fujinet, the message looks like this:

Leaving...
Hard Resetting...
Done! Flashing is complete!

Showing logs:
[15:38:07]
[15:38:07]
[15:38:07]--~--~--~--
[15:38:07]FujiNet 0.5.ba2f6751 2021-07-27 12:03:04 Started @ 4
[15:38:07]Starting heap: 4054556
[15:38:07]PsramSize 3917592
[15:38:07]himem phys 4456448
[15:38:07]himem free 4456448
[15:38:07]himem reserved 262144
[15:38:07]Detected Hardware Version: 1.1-1.5
[15:38:07]Enabled Safe Reset Button C
[15:38:07]SPIFFS mounted.
[15:38:07]E (1134) vfs_fat_sdmmc: sdmmc_card_init failed (0x107).
[15:38:07]SD mount failed with code #263, "ESP_ERR_TIMEOUT"
[15:38:07]fnConfig::load
[15:38:07]Load fnconfig.ini from spiffs
[15:38:07]fnConfig::load read 264 bytes from config file
[15:38:07]SPIFFS Config Storage: Enabled
[15:38:07]fnConfig::load read 264 bytes from SPIFFS config file
[15:38:07]WIFI_EVENT_STA_START
[15:38:07]disk UNMOUNT
[15:38:07]disk MOUNT
[15:38:07]ATR MOUNT
[15:38:07]mounted ATR: paragraphs=5760, sect_size=128, sect_count=720, disk_size=0
[15:38:07]Creating a default printer using FS_SPIFFS storage and type 1
[15:38:07]SSH client initialized.
[15:38:07]ModemSniffer::ModemSniffer(FS_SPIFFS)
[15:38:07]SIO SETUP
[15:38:07]Set HSIO baud from 0 to 67431 (index 6), alt=68209
[15:38:07]Available heap: 3965864
[15:38:07]Setup complete @ 457 (453ms)

It seems that the broken unit doesn´t start again after updating...

 

What can we try to revive the device?

 

Sleepy

Link to comment
Share on other sites

3 hours ago, Sleepy said:

Hi,

 

we tried to update an actual Funjinet (1.5). One unit was no problem, another unit first doesn´t go into update mode.
We forced entering update-mode by pressing "A"-button and powering up fujinet.
Then we can update it, but after update, the last message in the console-window looks like this:


Leaving...
Hard Resetting...
Done! Flashing is complete!

 

Connected to the XLs SIO-plug again, the computer doesn´t boot the Fujinet-software anymore...


Updating another Fujinet, the message looks like this:


Leaving...
Hard Resetting...
Done! Flashing is complete!

Showing logs:
[15:38:07]
[15:38:07]
[15:38:07]--~--~--~--
[15:38:07]FujiNet 0.5.ba2f6751 2021-07-27 12:03:04 Started @ 4
[15:38:07]Starting heap: 4054556
[15:38:07]PsramSize 3917592
[15:38:07]himem phys 4456448
[15:38:07]himem free 4456448
[15:38:07]himem reserved 262144
[15:38:07]Detected Hardware Version: 1.1-1.5
[15:38:07]Enabled Safe Reset Button C
[15:38:07]SPIFFS mounted.
[15:38:07]E (1134) vfs_fat_sdmmc: sdmmc_card_init failed (0x107).
[15:38:07]SD mount failed with code #263, "ESP_ERR_TIMEOUT"
[15:38:07]fnConfig::load
[15:38:07]Load fnconfig.ini from spiffs
[15:38:07]fnConfig::load read 264 bytes from config file
[15:38:07]SPIFFS Config Storage: Enabled
[15:38:07]fnConfig::load read 264 bytes from SPIFFS config file
[15:38:07]WIFI_EVENT_STA_START
[15:38:07]disk UNMOUNT
[15:38:07]disk MOUNT
[15:38:07]ATR MOUNT
[15:38:07]mounted ATR: paragraphs=5760, sect_size=128, sect_count=720, disk_size=0
[15:38:07]Creating a default printer using FS_SPIFFS storage and type 1
[15:38:07]SSH client initialized.
[15:38:07]ModemSniffer::ModemSniffer(FS_SPIFFS)
[15:38:07]SIO SETUP
[15:38:07]Set HSIO baud from 0 to 67431 (index 6), alt=68209
[15:38:07]Available heap: 3965864
[15:38:07]Setup complete @ 457 (453ms)

It seems that the broken unit doesn´t start again after updating...

 

What can we try to revive the device?

 

Sleepy

The error code above seems to indicate that the SDMMC slot may have a connection problem. possibly cold solder joint?

 

-Thom

Link to comment
Share on other sites

1 minute ago, Sleepy said:

All three LED are still glowing after the update process.

 

Last message in console window is "showing logs:"

 

Sleepy

That indicates it did not flash properly. I'm guessing this is the same usb cable and computer you used to flash the other one? If so, then I'd say it's a problem with the fujinet. You could try another cable and computer to rule that out

Link to comment
Share on other sites

  • 1 month later...

Guys - I just completed a build of a 576 Fijunet + Cart prototype.  I used the following ESP module - https://www.amazon.com/gp/product/B07RL95M5B

It states the following specs:

  • Main Chip: ESP32-D0WD
  • Flash: 16MB SPI flash
  • PSRAM: 8MB PSRAM
  • Antenna: IPEX Antenna
  • Module: SMD

However, the flasher gives me the following error:

Using 'COM5' as serial port.
Starting firmware upgrade...
Getting latest firmware from fujinet.online..
FujiNet Version: 0.5.ba2f6751
Version Date/Time: 2021-07-27 12:03:04
Build Date/Time: Mon Aug 16 01:45:57 UTC 2021
Connecting....
Detecting chip type... ESP32
Connecting...

Chip Info:
 - Chip Family: ESP32
 - Chip Model: ESP32D0WDQ5 (revision 1)
 - Number of Cores: 2
 - Max CPU Frequency: 240MHz
 - Has Bluetooth: YES
 - Has Embedded Flash: NO
 - Has Factory-Calibrated ADC: YES
 - MAC Address: 24:6F:28:4C:7F:88
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
 - Flash Size: 4MB
 - Firware path: fujinet.online
 - Flash Mode: dio
 - Flash Frequency: 40MHz
Erasing flash (this may take a while)...
Unexpected error: Error while erasing flash: Timed out waiting for packet content

 

Why is is reporting no flash?  Do you think I received  counterfeit / bogus device?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...