Jump to content
tschak909

#FujiNet Testing and Bug Reporting Thread

Recommended Posts

Ok so we have you getting a printout correctly and I’ve proved the emulation correctly handles esc/p so we know the problem is how you are generating the output print file not the fujinet. 
 

So. How are you doing that? Take photos it really helps us. 

Share this post


Link to post
Share on other sites
2 hours ago, Mr Robot said:

Ok so we have you getting a printout correctly and I’ve proved the emulation correctly handles esc/p so we know the problem is how you are generating the output print file not the fujinet. 
 

So. How are you doing that? Take photos it really helps us. 

We've managed to track it down to the fact that he's using modes and fonts that aren't implemented yet. @jeffpiep is aware of it and it will be implemented. :)

 

Thanks to those of you who are kicking the tires, it's how we get all this stuff done! :)

 

-Thom

Share this post


Link to post
Share on other sites

Still having issues using the F*.COM commands in SDX. Getting errors from FMOUNT and FEJECT but both seem to work. FMOUNT the help information is missing the needed commas to make it work... and sub-directories still cannot be browsed using FLS.COM --- though I can mount an imagine in a sub-directory if I know the full path. 

 

Earlier I mentioned what appeared to be a line-ending issue --- the exact characters for the line-ending have changed but the issue is still there.

 

I would also like to bring up again that the device could be used with just SD -- but I don't see how I can get past the network config screen when I have no network to use. If it isn't a feature I think you should be. Thoughts?

 

As far as the SDX stuff --- I see everyone is busy working on many things. I just mention it again because someone has been working on this as somethings have started to work and the line endings have changed.

 

Thanks for everything!!!!

 

Share this post


Link to post
Share on other sites

Another milestone !

I tried to load some Polish games in CAS format but that doesn't seem to work , or have I misunderstood the new firmware update and it currently only is able to load cassettes and access files from them ?

Share this post


Link to post
Share on other sites
1 hour ago, Peri Noid said:

Works for me. How do you load the games? Can you point me to an exemplary one?

Thinking maybe it is the copy protection on the Polish Games , I tried Druid now from here
http://atarionline.pl/arch/D/Druid/Druid (1987)(Firebird)(GB).cas
 

  1. I don't have an SD card in my Fujinet ( is it necessary ? )
  2. on my 800XE (with an 320XE RAM expansion) it goes to BASIC
  3. on my U1MB 130XE it goes to Selftest 

Clearly there is something wrong in my approach, I'm just loading the CAS file and then press OPTION to boot it :D

Share this post


Link to post
Share on other sites

That's right, you're doing it wrong 😁

Press Option and when FN starts to mount files, press Start additionally and hold both until the machine reboots and you can hear a sound. Then press space and the second FujiNet button (activity led should come up) and after a while you should hear the block loading sound (no pilot sound though). 

  • Thanks 2

Share this post


Link to post
Share on other sites
1 minute ago, Peri Noid said:

That's right, you're doing it wrong 😁

Press Option and when FN starts to mount files, press Start additionally and hold both until the machine reboots and you can hear a sound. Then press space and the second FujiNet button (activity led should come up) and after a while you should hear the block loading sound (no pilot sound though). 

Block loading sound as I type, thanks a lot , I had tried Start-Option , ENTER but didn't know about the 2nd Fujinet button !

Share this post


Link to post
Share on other sites

We've had a user mention that they are unable to use their SD card after the latest firmware flash, the debug monitor returns the following information:

https://github.com/FujiNetWIFI/fujinet-platformio/issues/415#issuecomment-748649199

 

The error indicated here is very strange, as it should never happen (0x106 is an unsupported command)

 

-Thom

Share this post


Link to post
Share on other sites

Mine (after replacement recall) still won't hold an SIO cable in its port without me physically holding it in tight with my hand.

Too much plastic or pins too short [or too small diameter].

 

Share this post


Link to post
Share on other sites
9 hours ago, Kyle22 said:

Mine (after replacement recall) still won't hold an SIO cable in its port without me physically holding it in tight with my hand.

Too much plastic or pins too short [or too small diameter].

 

Are you pushing it in all the way? The Chelco cable I have has to be pushed in pretty hard to bottom out in the port. The other cable (labeled JAE) is a different style and goes in smooth and bottoms out nicely. Do you have another cable to try? The images below show how much gap when the cable is all the way in. Make sure yours is in that far

IMG_20210106_073918781_1.thumb.jpg.909da270391843d52c43d64d92293958.jpg

IMG_20210106_074002437_1.thumb.jpg.aba3c8b1551bd630975d7c0ef5fb5475.jpg

Share this post


Link to post
Share on other sites

I think, its the matter of pins - look at the FN and on its pins, maybe they are too short. Mine are, therefore the grip is not too reliable. Yet, seems to work.

Share this post


Link to post
Share on other sites

The JAE connector is the best holding itself into the Fujinet port. The Lotharek SIO cables are the worst regarding that (great build, excellent quality, right flexibility) one of my favorites to use all the time, except when it comes to Fujinet. It is like the female contacts based on the "spring" design "spring out" the pins and disconnect the cable.

 

 

  • Like 1

Share this post


Link to post
Share on other sites

It is almost if not just as loose as the first one.

I'm running a complicated system. I NEED that SIO port not to pop loose.

 

This must be SOLID connection.

 

Share this post


Link to post
Share on other sites
On 12/15/2020 at 2:30 AM, MrFSL said:

Still having issues using the F*.COM commands in SDX. Getting errors from FMOUNT and FEJECT but both seem to work. FMOUNT the help information is missing the needed commas to make it work... and sub-directories still cannot be browsed using FLS.COM --- though I can mount an imagine in a sub-directory if I know the full path. 

 

Earlier I mentioned what appeared to be a line-ending issue --- the exact characters for the line-ending have changed but the issue is still there.

 

I would also like to bring up again that the device could be used with just SD -- but I don't see how I can get past the network config screen when I have no network to use. If it isn't a feature I think you should be. Thoughts?

 

As far as the SDX stuff --- I see everyone is busy working on many things. I just mention it again because someone has been working on this as somethings have started to work and the line endings have changed.

 

Thanks for everything!!!!

 

 

I'm having an interesting time experimenting with the F*.COM tools in SDX.  I've spotted what appears to be a symptom of the issue with FLS.COM when viewing the contents of subdirectories, as mentioned by @MrFSL.

 

If I run

FLS 1

I get the top-level directory listing from my SD card, but

FLS 1,ROMS

gives an SIO ERROR instead of the list of files in the ROMS directory.

 

Looking at the serial output, the subdirectory name in the FLS command has an 0x01 character appended.

[20:30:49]CF: 70 f7 00 00 68
[20:30:49]sioFuji::sio_process() called
[20:30:49]ACK!
[20:30:49]Fuji cmd: OPEN DIRECTORY
[20:30:49]<-SIO read 256 bytes
[20:30:49]ACK!
[20:30:49]Opening directory: "ROMS", pattern: ""
[20:30:49]::dir_open {0:1} "ROMS", pattern ""
[20:30:49]::dir_open actual path = "ROMS"
[20:30:49]ERROR!
[20:30:49]
[20:30:49]CF: 70 f7 00 00 68
[20:30:49]sioFuji::sio_process() called
[20:30:49]ACK!
[20:30:49]Fuji cmd: OPEN DIRECTORY
[20:30:49]<-SIO read 256 bytes
[20:30:49]ACK!
[20:30:49]Opening directory: "ROMS", pattern: ""
[20:30:49]::dir_open {0:1} "ROMS", pattern ""
[20:30:49]::dir_open actual path = "ROMS"
[20:30:49]ERROR!

If I append a ctrl-A character right at the end of the ROMS subdirectory name in the FLS command, I get a subdirectory listing and no error.  But there are now obviously two control characters appended to the ROMS directory name.

[20:31:10]CF: 70 f7 00 00 68
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: OPEN DIRECTORY
[20:31:10]<-SIO read 256 bytes
[20:31:10]ACK!
[20:31:10]Opening directory: "ROMS", pattern: ""
[20:31:10]::dir_open {0:1} "ROMS", pattern ""
[20:31:10]::dir_open actual path = "ROMS"
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 24 00 8b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]::read_direntry "Action! (1983)(ACS).car"
[20:31:10]->SIO write 36 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 24 00 8b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]::read_direntry "Atari LOGO (1983)(Atari).car"
[20:31:10]->SIO write 36 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 24 00 8b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]::read_direntry "Basic XE v4.1 (1985)(OSS)(US).car"
[20:31:10]->SIO write 36 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 24 00 8b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]::read_direntry "Basic XL v1.03 (1983)(OSS)(US).car"
[20:31:10]->SIO write 36 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 24 00 8b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]::read_direntry "Homebase (1982)(Citibank)(US).car"
[20:31:10]->SIO write 36 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 24 00 8b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]::read_direntry "MAC-65 v1.01 (1984)(OSS)(US).car"
[20:31:10]->SIO write 36 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 24 00 8b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]::read_direntry "OSS Cart Bundle &amp; SDX AtariMax.rom"
[20:31:10]->SIO write 36 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 e4 06 00 5b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: SET DIRECTORY POSITION
[20:31:10]::dir_seek {0:1} 6
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 80 00 e7
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=128)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]::read_direntry "OSS Cart Bundle &amp; SDX AtariMax.rom"
[20:31:10]->SIO write 128 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 24 00 8b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]::read_direntry "PILOT (1981)(Atari)(US).car"
[20:31:10]->SIO write 36 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f6 24 00 8b
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:31:10]::dir_nextfile {0:1}
[20:31:10]Reached end of of directory
[20:31:10]->SIO write 36 bytes
[20:31:10]COMPLETE!
[20:31:10]
[20:31:10]CF: 70 f5 00 00 66
[20:31:10]sioFuji::sio_process() called
[20:31:10]ACK!
[20:31:10]Fuji cmd: CLOSE DIRECTORY
[20:31:10]COMPLETE!

I also tried appending a ctrl-A and ctrl-B to the subdirectory name in the FLS command and still get a successful directory listing.  In fact,

FLS 1,ROMS <followed by all 26 ctrl-A to ctrl-Z characters>

still results in a successful listing of the ROMS subdirectory.

[20:48:52]
[20:48:52]CF: 70 f7 00 00 68
[20:48:52]sioFuji::sio_process() called
[20:48:52]ACK!
[20:48:52]Fuji cmd: OPEN DIRECTORY
[20:48:52]<-SIO read 256 bytes
[20:48:52]ACK!
[20:48:52]Opening directory: "ROMS	
[20:48:52]", pattern: ""
[20:48:52]::dir_open {0:1} "ROMS	
[20:48:52]", pattern ""
[20:48:52]::dir_open actual path = "ROMS	
[20:48:52]"
[20:48:52]COMPLETE!
[20:48:52]
[20:48:52]CF: 70 f6 24 00 8b
[20:48:52]sioFuji::sio_process() called
[20:48:52]ACK!
[20:48:52]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:48:52]::dir_nextfile {0:1}
[20:48:52]::read_direntry "Action! (1983)(ACS).car"
[20:48:52]->SIO write 36 bytes
[20:48:52]COMPLETE!
[20:48:52]
[20:48:52]CF: 70 f6 24 00 8b
[20:48:52]sioFuji::sio_process() called
[20:48:52]ACK!
[20:48:52]Fuji cmd: READ DIRECTORY ENTRY (max=36)
[20:48:52]::dir_nextfile {0:1}
[20:48:52]::read_direntry "Atari LOGO (1983)(Atari).car"
[20:48:52]->SIO write 36 bytes
[20:48:52]COMPLETE!
<etc>

Also, I have just noticed that running the command as

FLS 1,ROMS/

appears to result in future FLS calls giving a 138 error until an FMALL is called to remount the drives.

 

Geoff

 

Edit:  Annoyingly, all the ctrl-characters that were in the code snippets seem to have been purged when I submitted the message.  But they are clearly visible in the serial out log in the flasher utility.  Now it looks like I've just pasted lots of ordinary looking log output just for the sake of it! :roll:

Edited by GreyHobbit
Important control characters were stripped from the code snippets, making the explanation look incorrect

Share this post


Link to post
Share on other sites

Edit:  Annoyingly, all the ctrl-characters that were in the code snippets seem to have been purged when I submitted the message.  But they are clearly visible in the serial out log in the flasher utility.  Now it looks like I've just pasted lots of ordinary looking log output just for the sake of it! :roll:

 

you can always attach the logs and files....or send a picture... or

Share this post


Link to post
Share on other sites
On 1/12/2021 at 9:49 PM, tschak909 said:

If you want to see the source code for these utilities, look here:

https://github.com/FujiNetWIFI/fujinet-config-tools

 

-Thom

 

Thanks Thom

 

I had a look at the code and the main.c source for fls, fnet, ndel, ndir, nmkdir, nren & nrmdir all have a loop

for (i=1;i<=argc;i++)

 which should be 

for (i=1;i<argc;i++)

This tries to process an extra parameter that causes corruption at the end of the argument string being stored in buf[].

 

What is the proper way to submit code changes to the project?  Do I commit them to a new branch and push that to the github repo, then raise a pull request to get it approved?

 

Geoff

 

Share this post


Link to post
Share on other sites
33 minutes ago, tschak909 said:

Precisely.

 

Thank you, so much. :)

 

-Thom

 

Sorry for submitting those pull requests one file at a time, I couldn't get my IDE to push them all to a new branch in one go! :)

Share this post


Link to post
Share on other sites

Thanks for the merges. Curious, was there a reason you did each tool change as a separate pull req? :)

 

Ah ok, you answered it. So long as I know what was happening.

 

-Thom

 

Edited by tschak909

Share this post


Link to post
Share on other sites

Hey all!

 

Just received my FujiNet 1.3 in an XL type case. My SIO cable will not stay plugged into the back of the FujiNet. It just springs out. Unfortunately, I only have one SIO cable. I've tried both ends of the cable.

 

I've pushed hard, so I know that the cable won't go any farther in. It seems like the pins on the FujiNet are too short or the socket is too deep.

 

Any idea how I can work around this?

Share this post


Link to post
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.

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...