Jump to content

mozzwald

Members
  • Content Count

    547
  • Joined

  • Last visited

Everything posted by mozzwald

  1. I can only recommend the fixed version. You'll never know if you have problems until you try flashing and I've had to replace enough FujiNet's to know that it's a problem. I would prefer the no-fix version not be sold at all to prevent unhappy users. The fix should not be very difficult for someone who can assemble smd boards.
  2. Firmware is updated with option to mount READ or READ/WRITE
  3. A new firmware update is available at https://fujinet.online/download FujiNet Version: 0.5.24da0c96 Version Date/Time: 2021-04-10 00:41:00 Build Date/Time: Sat Apr 10 20:25:46 UTC 2021 Tweaks: * Add option to mount READ or READ/WRITE from webui Please do not respond to this thread. If you have an issue, start a new post in the FujiNet subforum, open an issue on the github tracker or ask for assistance in Discord chat.
  4. v1.3 had a hardware bug (my fault) that caused issues with flashing the firmware. There is a fix that should be applied to the v1.3 boards (ask your vendor). v1.5 is released with the fix and some other minor tweaks. Changes are listed in the hardware repo readme, but they don't really describe the fix, just the component changes. There will be a v1.6 with more minor changes: added SD Card detect pin and better SIO voltage measurement, neither issue hinder functionality in older versions. As for stock on fujinet.online, I build small batches of each revision when I have time and put them up for sale. You can signup to get notified via email from the product page but I don't know when I will be making more so could be a while
  5. It's probably either not being detected or you have a permissions problem. You could try another usb cable and also check this https://stackoverflow.com/a/47114909.
  6. Clicking the Serial Port dropdown shows nothing? I think on macs the serial port shows up as /dev/cu*something*, can you check if it appears there from terminal: ls /dev/cu*
  7. A new firmware update is available at https://fujinet.online/download FujiNet Version: 0.5.564cc6ca Version Date/Time: 2021-04-09 00:10:01 Build Date/Time: Fri Apr 9 00:59:12 UTC 2021 New Stuff Just For You: * More FTP improvements * Ability to browse hosts and mount disk images from the web ui: Please do not respond to this thread. If you have an issue, start a new post in the FujiNet subforum, open an issue on the github tracker or ask for assistance in Discord chat.
  8. I've changed my resistor divider to 1.2k & 2k which puts the high voltage around 3.125 volts. My bench power supply and DMM confirmed good results. A new firmware update was just pushed with updated calculation for v1.6 hardware. I also added debug output that shows what is being used as the voltage reference calibration: efuse, two-point or default. When you get a moment, could you swap your resistors and give it a test? Thanks!
  9. A new firmware update is available at https://fujinet.online/download FujiNet Version: 0.5.5d1bd4af Version Date/Time: 2021-04-05 21:27:01 Build Date/Time: Wed Apr 7 00:40:33 UTC 2021 New Bits: * Improved FTP support * SIO voltage calculation for v1.6 hardware Please do not respond to this thread. If you have an issue, start a new post in the FujiNet subforum, open an issue on the github tracker or ask for assistance in Discord chat.
  10. I did some digging into the SIO voltage issue and found a fancy chart showing the ADC voltage curve. The top end levels off so the reported voltage on the high end will be wrong. I wonder if we change the voltage divider to be lower and adjust the calculation then maybe get a closer result. I also added a 0.1uF capacitor as suggested on the linked page but it made no difference. FWIW, the page also talks about the calibration value and I confirmed my esp32 has the efuse burned from the factory with a default value of 1064 which is indeed being used instead of the 1100 default. I think most if not all FujiNets in the wild should have this value burned in them since they are probably all newer modules.
  11. I've implemented SD Card detection via interrupt in the latest firmware update if you could please test it. If the card is removed, Fujinet will safe reset. If card insertion is detected it will start the SD Card service (it does not mount any disk slots, but the card is available to use with config/config tools).
  12. A new firmware update is available at https://fujinet.online/download FujiNet Version: 0.5.879c407c Version Date/Time: 2021-04-02 01:14:21 Build Date/Time: Fri Apr 2 02:07:10 UTC 2021 All the new things: * modem: +++ now drops to command mode instead of disconnect * modem: implement ATO command to re-enter modem mode from command mode * hardware: implement SD Card detection for hardware version v1.6 and up. Card removal resets the fujinet, insertion starts the SD card service. * Updated fnc-tools Please do not respond to this thread. If you have an issue, start a new post in the FujiNet subforum, open an issue on the github tracker or ask for assistance in Discord chat.
  13. Nope Can you paste the actual error from the build?
  14. A new firmware update is available at https://fujinet.online/download FujiNet Version: 0.5.c3a06184 Version Date/Time: 2021-03-26 00:42:49 Build Date/Time: Fri Mar 26 01:02:36 UTC 2021 New Bits: * Disabling CONFIG from the webui enables auto mounting of configured slots during FujiNet bootup * New hardware version detection functions * Bugfix: Change TNFS payload size Please do not respond to this thread. If you have an issue, start a new post in the FujiNet subforum, open an issue on the github tracker or ask for assistance in Discord chat.
  15. Can you capture some debug output with the FujiNet connected to a computer and run the flash tool from https://fujinet.online/download? Connect Fujinet to the computer, run the tool, press serial debug output button, then press RESET button on the FujiNet. During bootup the FujiNet tries to mount the card and shows error output if it fails.
  16. A quick search and I found this https://github.com/chrisridd/LDAPClient which is for esp32 Arduino. Would need some modification to make it work on PlatformIO. Whatever you decide to use, make sure it works cross platform. Something like OpenLDAP instead of Active Directory. Maybe they are compatible with each other, I don't know.
  17. The release firmware from fujinet.online is built on Linux.
  18. Nope, not possible. Besides, you can just watch the debug output in the flash tool. It tells you if it fails or shows you the FujiNet boot messages if success. It even shows progress while flashing
  19. There's a lot of information on the wiki https://github.com/FujiNetWIFI/fujinet-platformio/wiki
  20. I'll see about testing this again and see if I can get it to work. When I tried it before I was using a breadboard. I pushed a 'silent' firmware update this evening with the new hardware version check so just run the flash tool to get it. If you have the pull up on IO12 you should see v1.6 hardware version in the boot messages. Nothing uses the card detect pin yet though.
  21. It's much easier now. In config, just try to mount a .cas file which will automagically put it in slot 8. then hold OPTION and START to load it. dang, Thom beat me to it
  22. I wonder if we even need to reset. Maybe we can just unmount anything that was on the SD card then detect the new card. Try loading a cassette image from FujiNet. There's a few on the FujiNet.online TNFS server
  23. awesome, glad you got it working Last night I bodged in a 10K pullup like so: and did some testing with the firmware. I had to use the esp32's internal pull up/down resistors to check if there was a pull up on IO12. There are some new functions to get the hardware version that is run at bootup and to check for the safe reset button C. We will have to figure out what to do with the card detect, but at least now we can determine if it's available or not. I can't remember what the problem was, but I had issues when trying to run MOTOR thru the 74LS07 so I left it directly connected with the pull down. If you test it and it works, let me know and I'ill give it another go.
  24. The button has a pull up resistor to 3.3V and when the button is pressed it is connected to GND. The firmware checks if the button is connected to GND. It should only show this message if you have pressed the button. I don't see how the TNFS timeout can cause the button to be detected as pressed. I have had plenty of TNFS timeouts and never seen this happen which leads me to believe there is a hardware problem. Try powering the FujiNet from USB while testing the TNFS copy and see if that helps any.
×
×
  • Create New...