Author Topic: Modern day M68K development  (Read 618 times)

0 Members and 1 Guest are viewing this topic.

Offline Gribo

  • Frequent Contributor
  • **
  • Posts: 513
  • Country: ca
Modern day M68K development
« on: April 15, 2021, 01:35:57 pm »
Hello all,
 I got a task to develop test firmware for a board with a 68332 MCU, I have the PEmicro Multilink FX adapter, and would like to setup a toolchain. Sadly, Codesourcery lite is no longer available.

What are my options? I am using windows 10.
I am available for freelance work.
 


Online SiliconWizard

  • Super Contributor
  • ***
  • Posts: 6954
  • Country: fr
Re: Modern day M68K development
« Reply #2 on: April 15, 2021, 03:57:38 pm »
I have used the toolchain provided here: https://gnutoolchains.com/m68k-elf/
and it works fine.
 

Offline Gribo

  • Frequent Contributor
  • **
  • Posts: 513
  • Country: ca
Re: Modern day M68K development
« Reply #3 on: April 16, 2021, 01:12:40 pm »
Thanks for the info.
I have installed the toolchain, and got Eclipse to create a project with all the headers, now it seems I am missing some resources.
I installed version 4.8 of the toolchain.
I am available for freelance work.
 

Offline Harjit

  • Regular Contributor
  • *
  • Posts: 118
  • Country: us
Re: Modern day M68K development
« Reply #4 on: April 17, 2021, 03:32:59 pm »
There is some good information here: https://wiki.control.fel.cvut.cz/nms/cpuarch/m68k/mo_cpu2-quick-start.html

Has anyone found an inexpensive USB BDM tool? This is for a hobby project.
 

Offline bingo600

  • Super Contributor
  • ***
  • Posts: 1572
  • Country: dk
Re: Modern day M68K development
« Reply #5 on: April 17, 2021, 05:47:19 pm »
Those are classic Newlib ... DIY routines , missing.
You have to implement them your self

/Bingo
 

Offline westfw

  • Super Contributor
  • ***
  • Posts: 3462
  • Country: us
Re: Modern day M68K development
« Reply #6 on: April 18, 2021, 09:14:17 am »
Quote
it seems I am missing some resources.
newlib in its full form likes to have resources that aren't that applicable to a small embedded system.
Figure out how to use newlib-nano instead, and it should be happier!
Probably something like "--specs=nano.specs --specs=nosys.specs" in the link command (may also require that you re-build newlib...)
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf