What have I done now?

[skimask]

I can turn around and reload the other program onto the same board and it's fine???

By any chance, did one of those 'updates' include updates to PBP?

[Archangel]

So when you program and it does not work, can you read back the hex from the chip and see the information ? How do you select the programmer when you load an old hex? Is that the same way as you load a new hex? Are you sure your programmer is using the correct COM port when called by MCS ? Same programming software in both instances ? Have you tried saving the new hex and then loading it the same way as the old hex? I am just throwing out some troubleshooting ideas, no answer required.

[Hylan]

I'm still fighting with this issue and here's where I'm at.

I uninstalled everything PBP, MPASM, Micro Code Studio Plus and several other IDE's I had loaded a long time ago before getting this thing to work (with much help from everyone here on the forum). And life was good up until a week or so ago!

I then reinstalled everything today and finally got the settings worked out on the programmer. So I'm sort of back to square one and looking for ideas. I can load hex files that I created literally 3 weeks ago fine. However, when I try to recompile the pbp file, nothing!

Now when I say nothing, I mean nothing from the board with the chip. The system says that it assembles and compiles fine with no errors. Then it erases the chip, programs and verify's the load and says it programmed successfully, but does nothing.

So, to summarize. Hex file created weeks ago from a pbp file loads and works fine on chip. Exact same pbp file now, assembles, compiles and loads with no errors, but is like it's not on the chip at all. Hmmm???

The one thing I was looking at on the MELabs site: http://www.melabs.com/support/mpasm.htm
was under the xp section trying to figure out what all should be in this path block? What different things should this be point to? Just to Mpasm location, or should it be pointing to other stuff too? Mine was pointing at a whole lot of nothing, so I did at least point it at the folder where Mpasm.exe is located, but that's it right now. And no change to what I posted above.

I'm grabbing at straws here, has anyone else experienced anything like this?

[mackrackit]

Upload a working hex and a non working hex compiled/assembled from the same code so we can take a look at it. we can ckeck the fuse settings from there.

[Hylan]

Here is a working and non working hex file samples from the same code. Rename file extension to .hex

There is a noticable difference in size of the files. Also, I noticed that on the drop down on the IDC Compile button I've got a couple choices listed:
Picbasic Pro 2.50
Picbasic Pro 2.50B
Picbasic Pro 2.50L

Originally I had two listed, 2.50 and 2.50L and the 2.50L was checked. So I tried checking the 2.50 just to see what would happen and then the 2.50B appeared. I don't know what the differences in these are but thought I'd throw it out there.

[mackrackit]

For what it is worth, The config bits are the same between the two. I have not had time to look any farther yet.

[skimask]

The notworking file has 17176 bytes, the working file has 5590 bytes.
Are you sure about compiling the same program? Doesn't look like it to me...
If the 17176 file was compiled with PBPL, that might make sense since PBPL uses all 32 bit math whereas PBP doesn't.

[Acetronics2]

Hi, Hylan

any chance you post here your source code ???

just us to try to reproduce the probem ...

Alain