Jump to content

Midibox64 vs ain64_din128_dout128


8O
 Share

Recommended Posts

I'm making steady (read: slow  ;)) progress on my midibox project, and have now reached the point where I really have to dive into the software side a little.

The problem is that I'm still having loads of issues getting asm compiling on Mac OSX (C compiling works fine). I currently have the midibox64 code (latest version) running nicely on my PIC, but now that I want to start changing the code it looks like I need to change to a C-based application. So, I'm thinking ain64_din128_dout128_v2b is the closest thing in C, compared to midibox64 code. Is this a correct assumption?

Anyone else been in this same situation? I am guessing there is no C version of the midibox64 application itself, is there...?

Thanks in advance for any advice!

Link to comment
Share on other sites

The problem is that I'm still having loads of issues getting asm compiling on Mac OSX (C compiling works fine).

Well, that makes little sense, because a C compile makes .ASM files, which are then assembled in the same way as a native ASM app... care to share some error messages etc?

ain64_din128_dout128_v2b is the closest thing in C, compared to midibox64 code. Is this a correct assumption?

Err yeh I think so. Of course it's missing lots of MB64's fancy features.... What's your goal?

I am guessing there is no C version of the midibox64 application itself, is there...?

Nope.

Link to comment
Share on other sites

Cheers for the fast reply folks.

Stryd_one, here's my earlier thread on trying to get assembly stuff to compile on OSX: http://www.midibox.org/forum/index.php/topic,11858.0.html

The goal is an Ableton Live controller with 24 DIN, 2 AIN (pots), 24 DOUT - that's my first attempt which is more of a test run. After that, trying some encs in AIN too... Pretty basic stuff  ;D

Edit: the goal of the code modifications I want to do is to change the info that's displayed on the LCD. I am using a 2x8 LCD (don't ask why ;D) and would like to modify the code a little so that the useful information gets displayed in the first 8 characters...

Edit2: oh, and also modifying the code to add DOUT control of a serial input latched driver...

Link to comment
Share on other sites

There's no info in that thread.... There's a short snippet of some error messages, but not a lot, and that predates TK pointing out that you need to change to the new structure. In your post it seemed that you were using half old half new..

Try complete logs of the compile process for both a C and an ASM app, and also the output of the --version switch of each of your tools (make, sed, gpasm, sdcc, etc)

You'll lose the menus if you drop the MB64, you'll want to customise the C app to have your own... We need more info about your controller's function.

Link to comment
Share on other sites

Ok, that's my homework - will get busy getting logs to post. Will get back to you...

Since posting that other thread, I've been regularly checking here:

http://www.midibox.org/dokuwiki/application_development

http://www.midibox.org/dokuwiki/how_to_use_xcode2_as_ide_on_a_mac

http://www.midibox.org/dokuwiki/installing_gputils_and_sdcc_on_osx

...but haven't seen any changes for a new structure. Am I looking in the right place?

I've also lost the links for the skeleton codes (e.g. http://ucapps.de/mios/sdcc_skeleton_v1_9a.zip - is a 404)... am I going crazy, or have they moved somewhere outside the realms of the ucapps search...?

Link to comment
Share on other sites

The skeleton links in the forum are obsolete, it's now part of the mios_base package

This is the latest state: http://www.midibox.org/forum/index.php/topic,11882.0.html

However, I think that something is wrong with your MacOS installation. Which gputils package did you install?

The command "gpasm --version"

should return "gpasm-0.13.5 beta" (or later)

Best Regards, Thorsten.

Link to comment
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...
 Share

×
×
  • Create New...