TheBackShed.com

Forum Index : Microcontroller and PC projects : Help with MMEDIT uploading file to target

Author

Message

sawasdee01
Newbie

Joined: 23/12/2016
Location: United Kingdom
Posts: 33

Posted: 07:50pm 29 May 2019

Copy link to clipboard

Print this post

Hi,

I have recently transferred a few .bas files from my desktop pc to a laptop, so that I can work on a couple of projects whilst I travel.

Both machines use Win 10 and the .bas files loaded perfectly onto their respective PIC32 and STM32 targets, using MMEDIT, on my desktop.

However, neither the PIC32 or the STM32 .bas files load from MMEDIT, when using the laptop.

I am very certain that the com port settings are correct, because the MMEDIT Chat works perfectly, with both targets.

On first glance, it would appear that I have got MMEDIT into some strange mode, where it tries to load .bas files onto either the Flash Chip (STM32) or the SD Card (PIC32) - but, for the life of me, I can't find where this setting is, or what I have done. More specifically:-

The PIC32 upload fails with a "SD Card not configured" warning

The STM32 upload fails with a "Flash not enabled" warning

I have tried de-installing MMEDIT and re-installing it, but the same thing keeps happening.

I have checked to ensure that I don't have something else running in the background - such as MMFile or Teraterm.

Interestingly, I can successfully load and run the .bas files on both targets by using standalone Teraterm XMODEM and the XMODEM RECEIVE command.

Additionally, if I use the MMEDIT 'Set Clock on Load' setting, the clock gets set perfectly on both targets - but the upload still fails.

My guess is that it must be either something that I have done to MMEDIT, or MMEDIT has got broken, somehow.

I would be hugely grateful for any help with this item.

Best wishes to all.

Sawasdee

Phil23
Guru

Joined: 27/03/2016
Location: Australia
Posts: 1667

Posted: 10:11pm 29 May 2019

Copy link to clipboard

Print this post

Not sure if that I'm saying is 100% correct or not; that's for Jim...

But I don't think MMedit actually uploads your BAS file; what it actually tries to upload is another file it creates.

Maybe it could be an issue relating to the creation/permissions on that file.

I think the file is created here, C:\Users\Phil\AppData\Local\CCom\MMedit.

To facilitate Crunch, removal of blank lines etc.

There's a lastfile.bas & lastfile.baz in my directory above.

Assume it's the BAZ file which will be sent as it shows as processed with Crunch etc.

Cheers.

TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 6283

Posted: 06:04am 30 May 2019

Copy link to clipboard

Print this post

If you want to reload MMEdit, I suggest you delete the settings folder as well in case there is a rouge setting at play.
The folder is something like
"C:\Users\Phil\AppData\Local\CCom\MMedit"

Also, make sure that you have the correct device and firmware version selected.
Trying to upload to a MX170 when MMEdit things it's a MM+ will not go well.

Jim

VK7JH
MMedit

sawasdee01
Newbie

Joined: 23/12/2016
Location: United Kingdom
Posts: 33

Posted: 06:26am 30 May 2019

Copy link to clipboard

Print this post

First of all - a huge 'thank you' to Phil23

While I have not 100% solved the problem, yet - I am now firmly on the right path (arf arf).

For the benefit of other Win10 users that might have the same issue, I have discovered:-

The MMedit file to which Phil23 alluded was in the Program Files(86)\CCom\MMedit directory on my Windows 10 PC.

My initial and unsuccessful attempts at fixing the issue centred around moving the location of ~ \CCom\MMedit to a different path (by de-installing and then re-installing MMedit).

I have achieved a fix to the problem by de-installing MMedit from my Win10 standard User Account and then re-installing MMedit into my Win10 Administrator Account - ie I have to log in as Administrator to use MMedit.

Bizarrely, MMedit used to work perfectly in my standard User Account - so this would appear to be a new issue - perhaps brought about by recent Win 10 updates.

Interestingly, when I log in to the standard User Account and go to the ~ \CCom\MMedit directory and check the properties of the MMedit directory, I see that the directory attributes are marked as 'Read Only'.

Once I am over the more immediate hurdle of getting my projects up and running again, I will try fiddling with the directory attributes, so that I can return to using the safer standard User Account.

Again, many thanks to Phil23

Sawasdee

sawasdee01
Newbie

Joined: 23/12/2016
Location: United Kingdom
Posts: 33

Posted: 06:33am 30 May 2019

Copy link to clipboard

Print this post

Thanks Jim,

Looks like our posts crossed over. I think that I am now heading in the right direction - but a big 'thumbs up' for MMedit, without which Micromite (etc) would be a shadow of itself.

Sawasdee

Print this page

To reply to this topic, you need to log in.