Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Hardware requirements

...

Info

If you have an existing Bitstream in Slot 1 it will be started instead the loaded Bitstream by xc3sprog. But you can skip this by holding key NO SCROLL while transferring the Bitstream, so that it stops in the Flash Menu on restart. Then you can just press key RUN/STOP to boot normally the loaded Bitstream without trying to load from the Flash menu.

...

  1. Make sure the MEGA65 is connected to your PC (by USB cable) and turn it on (keep it on for the further steps)

  2. Head to https://www.ftdichip.com/Drivers/D2XX.htm and download the most top D2XX driver from the list Currently Supported D2XX Drivers : Windows / x64 (64-bit) -> 2.12.36.4 (or just highest version available)

  3. In the Device Manager of Windows there are two unknown devices marked red (labeled as Universal Serial Bus controllers). You need to install drivers for both devices:

    1. Choose search on my computer for new drivers

    2. Choose the location of the downloaded D2XX drivers from step 2

    3. Choose/install the Serial Converter B

  4. After driver installation for both devices two red marked Ports (COM & LPT) will appear. You also need to install the drivers for them. Proceed the same way described in step 3.

  5. If none of the devices are no more marked red everything should be fine. You’re ready now to connect the MEGA65 to your PC by M65Connect. More details on : Connect PC to MEGA65

...

Info

On starting up M65Connect the first time on opening the SD Card Manager you will get a popup window asking for permission of for some specific folders and/or LAN access. You should give those grants in order to access the named folders and/or LAN connection.

...

  1. Start Linux and open a Terminal window

  2. Add your user to this group by typing: sudo usermod -a -G dialout,plugdev <username>
    while <username> represents your Linux user name. You can also use $USER for the active user.

  3. You NEED to relogin or restart Linux to take effect of these changes!