asm to hex

[graham]

Hi, I've got my hardware working but I can't find anything on how to edit an asm file and save it as a hex. I've googled it and downloaded mplab and tried to follow the instuctions and got lost, can anyone point me in the right direction?

[latigid on]

Hopefully this helps:

http://www.midibox.org/dokuwiki/doku.php?id=windows_toolchain_core&s[]=msys

also, what is your OS/MIDIbox app etc.?

[graham]

I'm using windows 10 and have built a midi cv converter all the menus work but the Aout ng board needs to the asm file to be changed, this is where 'im stuck. thanks for your reply

[graham]

I looked at the link but it not sure what I'm looking for?

[graham]

I've built the hardware and programmed the PICs and loaded hex files from mios studio all ok but stuck on editing and saveing an asm file to a hex to load into the core.

[latigid on]

You have to setup the build environment on your computer. Follow the instructions given on the wiki page. Then run MSYS, point the path to the directory containing your .asm and run the "make" command. This converts the coded file into a hex ready for transmitting using MIOS Studio.

[latigid on]

You could also try the following:

not sure if it's different for MIOS8.

[graham]

Ive found the wiki page but cant find anything on a build environment? thanks for your help

[graham]

I thought it would be simple to convert an asm file to hex but it appears to be out of my depth.

[latigid on]

Have you done everything written on the page? Come back when you have.

[latigid on]

Just now, graham said:

I thought it would be simple to convert an asm file to hex but it appears to be out of my depth.

Come now, don't be lazy! You're so close! Otherwise the MBCV will sit around wondering what it could have done with its life.

[graham]

Been trying to use MPLAB followed some youtube videos to create a new project but when I try to build it I get the following

 

Debug build of project `C:\Users\gra\Desktop\New folder\tes.mcp' started. Preprocessor symbol `__DEBUG' is defined. Sun Dec 10 12:08:04 2017 ---------------------------------------------------------------------- Make: The target "C:\Users\gra\Desktop\New folder\setup_j5_enabled.o" is out of date. Executing: "C:\Program Files (x86)\Microchip\MPASM Suite\MPASMWIN.exe" /q /p18F452 "setup_j5_enabled.asm" /l"setup_j5_enabled.lst" /e"setup_j5_enabled.err" /d__DEBUG=1 Error[105]   C:\USERS\GRA\DESKTOP\NEW FOLDER\SETUP_J5_ENABLED.ASM 95 : Cannot open file (Include File "src/main.inc" not found) Error[129]   C:\USERS\GRA\DESKTOP\NEW FOLDER\SETUP_J5_ENABLED.ASM 96 : Expected (END) Halting build on first failure as requested. ---------------------------------------------------------------------- Debug build of project `C:\Users\gra\Desktop\New folder\tes.mcp' failed. Preprocessor symbol `__DEBUG' is defined. Sun Dec 10 12:08:04 2017 ---------------------------------------------------------------------- BUILD FAILED

[graham]

Have abandoned MPLAB and read the 

Quick Start Guide Toolchain Setup

I can load the asm file in wordpad and edit and save it but which program do I need from those listed to create the Hex file from the ASM?

[graham]

I have downloaded docuwiki seems to be a collection of files, dont know what to do with any of them.

[latigid on]

Just now, graham said:

I can load the asm file in wordpad and edit and save it but which program do I need from those listed to create the Hex file from the ASM?

MSYS

[graham]

I have MSYS, when I run it it brings up a screen like CMD but with a flashing $, don't know what to do with it? thanks again for your reply, I've ltterally spent about 5 hours reading last night and 3 this morning going round in circles and feeling totally dejected as to how I cant do a simple task

[latigid on]

in MSYS

cd %PATH%

is the command to change directories, where %PATH% is the location of your .asm

ls

lists the directories and files

cd can be run for one folder at a time, using ls to see what else is there

cd C: //opens C: drive

or as a path

cd C:\2487\trunk\apps\controllers\midibox_ng_v1

 

In your case, use cd until you are in the correct folder, then run make. If you have set up the dependencies and system variables correctly, your .asm will be used to build a .hex. If you haven't followed the other instructions to setup the system properly you get no file and a list of error messages.

[graham]

Thanks again for your reply.

I've called my asm file test and saved it straight to C drive to make it easier.

i then typed cd C: //

now after the green writting it says /c

$ 

so I think I'm at the C directory and i typed

make setup

but got the message

make: ***  No rule to make target "test. stop.

 

[latigid on]

I suggest to unzip all of the files here http://www.ucapps.de/mios/midibox_cv_v1_3.zip

into something easy like C:\CV\

you would then navigate as 

cd C:\CV

make

perhaps you just have the asm in which case there is no command available. All of the subfolders (src etc.) are required to build a hex.

[graham]

Wow thanks, that was it, I was just putting the asm file on its own. I didnt realise you needed the other folders

make has generated a hex file from my wordpad edited asm

I am so happy I've tried most of the weekend, thanks for your help and perseverance 

this is the hardest thing I've done 

building the midibox seq3 was easier

I guess I'm more of a hardware person thanks once again.

Graham

[latigid on]

Well done! I hope the customisations worked okay. Let's see some build photos of the MBCV!

Best,
Andy

[graham]

you would laugh at the constuction, all on bits of boards my seq 3 is even worse, lots of ribbon cables hard wired and the switches are from an old IBM pc keyboard, works beautifully though, now I can integrate the d to a board on it now I know how to edit asms, thanks to you, I'll put some pics up,  and thanks again, Graham

[Noise-Generator]

I'm at the point now to have to change some stuff, too.

The official procedure looks very complex and I can't really understand why there is a mplab and there is source code in asm, and can't just edit and compile an asm file, and I think it's because I have to include the files in the project and the question is where...and I don't know why this should be so hard.

I don't want to reprogram mios, I just want to change some lines in the code...

[Antichambre]

6 hours ago, Noise-Generator said:

I'm at the point now to have to change some stuff, too.

The official procedure looks very complex and I can't really understand why there is a mplab and there is source code in asm, and can't just edit and compile an asm file, and I think it's because I have to include the files in the project and the question is where...and I don't know why this should be so hard.

I don't want to reprogram mios, I just want to change some lines in the code...

Hey! This is 20 years thing! TK did it like that for the people who don't know how to program and flash on the PIC. So he created a MIDI bootloader.(Yes there's a bootloader ;)
During some times the PIC was sold with the BL already flashed, then there was no need of a programmer, only a MIDI interface was necessary cause the MIOS8 and the App layer are uploadable with the MIOS Studio, the .hex file! Which is sent as SysEx to the PIC.
I was a bit lost too at the beginning, without any ASM knowledge. But I tried, failed, succeed, and finally learnt a lot more than I expected.
Most of the people don't want to change a line in the code, they just want a working machine after have building it.
Conclusion if you want to change some lines in the code, you must be interested in mios8 and what it is.
Follow the procedures, try, after a few steps, you will see everything lights up. ;)

BR
Bruno

[Noise-Generator]

21 hours ago, Antichambre said:

Hey! This is 20 years thing! TK did it like that for the people who don't know how to program and flash on the PIC. So he created a MIDI bootloader.(Yes there's a bootloader ;)
During some times the PIC was sold with the BL already flashed, then there was no need of a programmer, only a MIDI interface was necessary cause the MIOS8 and the App layer are uploadable with the MIOS Studio, the .hex file! Which is sent as SysEx to the PIC.
I was a bit lost too at the beginning, without any ASM knowledge. But I tried, failed, succeed, and finally learnt a lot more than I expected.
Most of the people don't want to change a line in the code, they just want a working machine after have building it.
Conclusion if you want to change some lines in the code, you must be interested in mios8 and what it is.
Follow the procedures, try, after a few steps, you will see everything lights up. ;)

BR
Bruno

Yes, I do understand this, it's no accusing, it's complaining ;)

It's not easy to understand and research this in a few minutes, it does need a lot of research...and you don't get the answers easy.

Sooner or later I must do this, just would be nice to have all the 4 rows of my LCD, now. There is just nothing atm I would change with the inputs.