Firebee/BaS_gcc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

correct directory contents info

Browse Source
This commit is contained in:
Markus
2020-06-24 07:55:49 +02:00
committed by GitHub
parent 2155af8a15
commit 24b4eae02f
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@@ -25,11 +25,14 @@ BaS_gcc aims to fully supports native EmuTOS + native FreeMiNT on the FireBee.
- checkout a copy of the BaS_gcc sources to your local machine - checkout a copy of the BaS_gcc sources to your local machine
- make sure you have a suitable gcc toolchain available. This could be either an m68k-atari-mint toolchain or an m68k-elf gcc toolchain (see switches in the toplevel Makefile). - make sure you have a suitable gcc toolchain available. This could be either an m68k-atari-mint toolchain or an m68k-elf gcc toolchain (see switches in the toplevel Makefile).
- type "make". The build should finish without errors - type "make". The build should finish without errors (just warnings about code not finished yet)
- for the FireBee, you'll find a flashable file (bas.s19) in the firebee directory - for the FireBee, you'll find a flashable file (bas.s19) in the firebee directory
- for the m5484lite board files will reside in the m5475evb directory - for the m5484LITE evaluation board are in the m5484lite directory
- for the m5475evb board files will reside in the m5475evb directory
- for the m54455 FreeScale evaluation board, files (not functional yet) are in the respective directory - for the m54455 FreeScale evaluation board, files (not functional yet) are in the respective directory
- ram.s19 files are meant for testing. They are suitable for direct download to RAM (instead of flashing them). This saves wear on the flash chips and improves development turnaround
## How to flash: ## How to flash:
These files can be flashed with either Didier Méquinon's flasher available from the firebee.org home page or any BDM hardware (urgently recommended as this is the only "parachute" available if something goes wrong during flashing). Personally, I'm using a parallel P&E flash solution that came with my m5484lite board and the BDM tools from here: https://sourceforge.net/projects/bdm/ since they are supported under Linux (my favorite) and also support the TBLCF (another, USB based open source BDM solution). See the firebee.org home page for more information. These files can be flashed with either Didier Méquinon's flasher available from the firebee.org home page or any BDM hardware (urgently recommended as this is the only "parachute" available if something goes wrong during flashing). Personally, I'm using a parallel P&E flash solution that came with my m5484lite board and the BDM tools from here: https://sourceforge.net/projects/bdm/ since they are supported under Linux (my favorite) and also support the TBLCF (another, USB based open source BDM solution). See the firebee.org home page for more information.