> That's why I'm still looking for Olin's files. According to an earlier
> post from Olin, maybe they might be found on Philip's PC. And maybe
> Philip, when he is back in real life (that is, on the PIClist :-) ), could
> confirm this...
"I'm not asleep! I'm jes', erm.. restin' me eyes, guv'ner!"
First off, the latest EasyISP firmware is on my website. Version 9/10
protocol support is the next thing on the to-do list; ETA some time next
week.
URL: <http://www.philpem.me.uk/elec.php>
[ yes, it's all PHP now, but the .htm links should still work ]
> Oh well, doesn't MC test their own tools ??
I'd be inclined to say.... No.
Later.
--
Phil. | Acorn Risc PC600 Mk3, SA202, 64MB, 6GB, philpemKILLspamphilpem.me.uk | ViewFinder, 10BaseT Ethernet, 2-slice, http://www.philpem.me.uk/ | 48xCD, ARCINv6c IDE, SCSI
... If it ain't broke, break it and charge for repair.
____________________________________________
Any interests to extend the Pickit 1 firmware and the PC host software? :)
Compare to Wisp628, it is similar in price and support USB. It is also
made by Microchip and will be supported by Microchip for basic
functionality.
If we populated the PICKit 1 with the optional RS232 and replace the 16C745
with the new PIC18F USB part, I see even a possibility to have similar
function of MPLAB ICD2.
>Date: Tue, 30 Nov 2004 00:00:08 GMT
>From: Philip Pemberton <.....philpemKILLspam.....dsl.pipex.com>
>
>First off, the latest EasyISP firmware is on my website. Version 9/10
>protocol support is the next thing on the to-do list; ETA some time next
>week.
>URL: <http://www.philpem.me.uk/elec.php>
> [ yes, it's all PHP now, but the .htm links should still work ]
>
>> Oh well, doesn't MC test their own tools ??
>
>I'd be inclined to say.... No.
>
>Later.
>--
>Phil. | Acorn Risc PC600 Mk3, SA202, 64MB,
----- Original Message -----
From: "Chen Xiao Fan"
> Hi, the website is down now. :(
>
> Any interests to extend the Pickit 1 firmware and the PC host software?
:)
> Compare to Wisp628, it is similar in price and support USB. It is also
> made by Microchip and will be supported by Microchip for basic
> functionality.
>
> If we populated the PICKit 1 with the optional RS232 and replace the
16C745
> with the new PIC18F USB part, I see even a possibility to have similar
> function of MPLAB ICD2.
>
> Xiaofan
>
Huh? Optional RS232? The unpopulated parts on board are part of a snap-off
development board, not electrically connected to the 16C745 at all. And
although I haven't read the datasheets in detail to compare them, the
16C745 and the new 18F USB parts have such vastly different specs I would
*not* expect them to have the same pinout. By the time a person works
around those issues, what have you saved?
FWIW, I was disappointed when I first received my PICKit1 and discovered
that it wouldn't program other parts. Seemed to me like microchip missed an
opportunity there. It seemed to me that the hardware did everything
necessary for most or all of the FLASH PICs (I don't think Vpp is strong
enough for the EEPROM parts) If only the PC software and firmware supported
it....
Hmm. Try it again - from some places it runs a little slow, then once your
machine picks up the DNS data, it speeds up.
> Any interests to extend the Pickit 1 firmware and the PC host software? :)
> Compare to Wisp628, it is similar in price and support USB. It is also
> made by Microchip and will be supported by Microchip for basic
> functionality.
No chance. I don't do USB, and adding RS232 to the PICkit would be
prohibitively expensive anyway.
> I found that it did not work in Windows 98SE which is what I have
> now at work. Maybe I can try to learn this at home.
Read the instructions on the Easyprog website. You have to configure the
development environment manually in Win98.
> But I see a lot of batch file there in the com directory and it
> is a bit scary. Olin, just wondering why not using something
> like make (makefile)?
Batch files are more fun ;D
Later.
--
Phil. | Acorn Risc PC600 Mk3, SA202, 64MB, 6GB, RemoveMEphilpemTakeThisOuTphilpem.me.uk | ViewFinder, 10BaseT Ethernet, 2-slice, http://www.philpem.me.uk/ | 48xCD, ARCINv6c IDE, SCSI
... All you folks do not exist. My sysop types all this stuff in.
____________________________________________
Chen Xiao Fan wrote:
> I found that it did not work in Windows 98SE which is what I have
> now at work.
Right. The automated installation procedure will make quite a mess on Win9x
systems, just like the documentation says.
> But I see a lot of batch file there in the com directory and it
> is a bit scary. Olin, just wondering why not using something
> like make (makefile)?
BAT files are the lowest common denominator that I know will work on all
machines. Most things rebuild within a few seconds so its not a big deal.
However, nothing is stopping you from creating your own makefiles. If that
is too much hassle you can have all your money back.
*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com
____________________________________________
At 11:18 PM 11/29/2004, Chen Xiao Fan wrote:
>Hi, the website is up again now. I download the source code and
>the EmbedInc development environment.
>
>I found that it did not work in Windows 98SE which is what I have
>now at work. Maybe I can try to learn this at home.
Read - very carefully - the special instructions for installation under
Win98SE. Pay particular attention to the part that says how to work with
the file while the automated installer is stalled while waiting for user
input. Note that it is important that the automated installer remain
stalled! After dealing with the files, kill the automated installer
process - don't allow it to continue.
I found Olin's instructions easy to follow and I can testify that the
environment works on both Win98SE installations that I've tried it on.
Celebrating 20 years of Engineering Innovation (1984 - 2004)
.-. .-. .-. .-. .-. .-. .-. .-. .-. .-
`-' `-' `-' `-' `-' `-' `-' `-' `-'
Do NOT send unsolicited commercial email to this email address.
This message neither grants consent to receive unsolicited
commercial email nor is intended to solicit commercial email.
Okay, it works in Windows XP with no problem and the BAT files
are not so difficult to adapt as well after reading the document
from Jan-Eric (the PDF file, Ch6) and Ch8 tells us how to use
MAKE. Thanks Jan-Eric and Olin.
It seems I do need to manually register %MPLABDir% in the XP
environment. The %EMBEDINC% and %PATH% are installed with
the installer.
Xiaofan
>Date: Tue, 30 Nov 2004 07:58:26 -0500
>From: TakeThisOuTolin_piclistEraseMEspam_OUTembedinc.com (Olin Lathrop)
>
>Chen Xiao Fan wrote:
>> I found that it did not work in Windows 98SE which is what I have
>> now at work.
>
>Right. The automated installation procedure will make quite a mess on
Win9x {Quote hidden}
>systems, just like the documentation says.
>> But I see a lot of batch file there in the com directory and it
>> is a bit scary. Olin, just wondering why not using something
>> like make (makefile)?
>
>BAT files are the lowest common denominator that I know will work on all
>machines. Most things rebuild within a few seconds so its not a big deal.
>However, nothing is stopping you from creating your own makefiles. If that
>is too much hassle you can have all your money back.
> Okay, it works in Windows XP with no problem and the BAT files
> are not so difficult to adapt as well after reading the document
> from Jan-Eric (the PDF file, Ch6) and Ch8 tells us how to use
> MAKE. Thanks Jan-Eric and Olin.
Hi.
Nice that you found the PDF !
Just note that it hasn't been updated for a while.
I think Olin have made at least one major update since
I made this PDF from his plain text based docs...
I'll see when there is time to make an update. I've been
forced to focus on "real" customers who pays "real" money
lately... :-)
I would say it will not work right out of the box under Win98SE
(after copying the EMBEDINC directory to your hard drive and setting
the environment variable %embedinc% and adding %embedinc%\com
to the %path% and rebooting).
For example, in the batch file src_get.bat, we have the following:
"cd /d %embedinc%\src\%1".
/d is not a valid switch in Windows 98SE. Since I installed to
the C:\embedinc, I can change that to "cd /d %embedinc%\src\%1".
I tried to add the following to Autoexec.bat.
rem For EMBEDINC PIC DEV
set embedinc=c:\embedinc
set path=%embedinc%\com;%path%
set MPLABDir=C:\Progra~1\MPLABI~1\MCHIP_~1
A simple run of the following returns quite some errors.
C:\embedinc\com>call src_ins_aspic pic std_def
File not found
File not found
Invalid switch - /D (can be fixed)
File not found
std_def.ins.aspic
Am I missing something obvious here?
Xiaofan
>Date: Tue, 30 Nov 2004 12:37:51 -0700
>From: Dwayne Reid <RemoveMEdwaynerTakeThisOuTplanet.eon.net>
>
>I found Olin's instructions easy to follow and I can testify that the
>environment works on both Win98SE installations that I've tried it on.
>
>dwayne
____________________________________________
Chen Xiao Fan wrote:
> I would say it will not work right out of the box under Win98SE
> (after copying the EMBEDINC directory to your hard drive and setting
> the environment variable %embedinc% and adding %embedinc%\com
> to the %path% and rebooting).
>
> For example, in the batch file src_get.bat, we have the following:
> "cd /d %embedinc%\src\%1".
>
> /d is not a valid switch in Windows 98SE.
Yes, you are right. Changes were recently made to the build scripts that
use features not found in the Win9x command shell. The PIC build
enviornment no longer runs on Window 9x. The web site has been updated
accordingly.
*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com
____________________________________________
I think the problem for Olin's Pic Development Environment
with Windows 98SE are with the two batch files (src_get.bat
and src_getfrom.bat). I do not have a simple fix for that
since I am not so good at Batch file.
To build EasyIsp in Win98, I have choose to modified the following
4 batch files instead and modified build_wispezp_expic.bat to
use the modified batch files. Please note I remove lots
of the advance features of the original batch files. The
tools have to be installed in C:\ as well since "cd /d" is not
working in Win98.
Anyway, Olin does not support Win98 and I do not think it is a
good idea to do it in Win98. My company will probably move
to Windows XP Professional next year.
Maybe Jan-Eric can update the documentation on how to use
Olin's tools using Make.
Xiaofan
1)
rem my_src_ins_aspic.bat
@echo off
cd %embedinc%\src\%1
set tabs= -tabs 10 18 30 31
copya (cog)source/%1/%2.ins.aspic
echo %2.ins.aspic
prepic %2.ins.aspic
2)
rem my_src_aspic.bat
@echo off
echo %2.aspic
cd %embedinc%\src\%1
set tabs= -tabs 10 18 30 31
copya (cog)source/%1/%2.aspic
asmpic (cog)src/%1/%2.aspic /c- /o+
3)
rem my_src_libpic.bat
@echo off
cd %embedinc%\src\%1
set tabs=
copya (cog)source/%1/%2.mlist
echo %2.mlist
if exist %2.lib del %2.lib
if exist %2.libpic del %2.libpic
>Date: Wed, 1 Dec 2004 08:54:20 -0500
>From: olin_piclistEraseME.....embedinc.com (Olin Lathrop)
>
>Chen Xiao Fan wrote:
>> I would say it will not work right out of the box under Win98SE
>> (after copying the EMBEDINC directory to your hard drive and setting
>> the environment variable %embedinc% and adding %embedinc%\com
>> to the %path% and rebooting).
>>
>> For example, in the batch file src_get.bat, we have the following:
>> "cd /d %embedinc%\src\%1".
>>
>> /d is not a valid switch in Windows 98SE.
>
>Yes, you are right. Changes were recently made to the build scripts that
>use features not found in the Win9x command shell. The PIC build
>enviornment no longer runs on Window 9x. The web site has been updated
>accordingly.
> To build EasyIsp in Win98, I have choose to modified the following
> 4 batch files instead and modified build_wispezp_expic.bat to
> use the modified batch files. Please note I remove lots
> of the advance features of the original batch files.
When I installed Olin's envir, I also heavily modified the
"glue" (BAT files). Anyway, the real value in Olins environment
is in the macros and the preprocessor, not in the BAT files
as such.
> The tools have to be installed in C:\ as well since "cd /d" is not
> working in Win98.
>
> Anyway, Olin does not support Win98 and I do not think it is a
> good idea to do it in Win98. My company will probably move
> to Windows XP Professional next year.
Right, working with W98 seems a total waste of time, not only
becuse Olin doesn't support it, but in general...
> Maybe Jan-Eric can update the documentation on how to use
> Olin's tools using Make.
Of course I "could". :-)
If it will happen, is a totaly other matter...
Oh I understand that. Maybe I can try to do that but I only
know a bit of Make or maybe I can get help from my two brothers
who are software engineers now.
Of course I'd prefer Olin to put up a official Makefile
template. :)
>Date: Thu, 2 Dec 2004 10:26:00 +0100 (CET)
>From: "Jan-Erik Soderholm" <EraseMEjan-erik.soderholmtelia.com>
>
>When I installed Olin's envir, I also heavily modified the
>"glue" (BAT files). Anyway, the real value in Olins environment
>is in the macros and the preprocessor, not in the BAT files
>as such.
>
>
>Right, working with W98 seems a total waste of time, not only
>becuse Olin doesn't support it, but in general...
>
>> Maybe Jan-Eric can update the documentation on how to use
>> Olin's tools using Make.
>
>Of course I "could". :-)
>If it will happen, is a totaly other matter...
>
>Regards,
>Jan-Erik.
Chen Xiao Fan <RemoveMExiaofanEraseMEEraseMEsg.pepperl-fuchs.com> wrote:
> Oh I understand that. Maybe I can try to do that but I only
> know a bit of Make or maybe I can get help from my two brothers
> who are software engineers now.
>
> Of course I'd prefer Olin to put up a official Makefile template. :)
I doubt Olin will do that.
The attached Makefile will build Olin's HAL project.
I posted this a long time ago, but here it is again.
It should be pretty obvious how to modify it for other projects -- it's
mainly a matter of replacing the HAL_OBJS lines with the right list of
object files, fixing up the names in the link step, and creating all the
correct source dependencies at the bottom.
Note: I use my own preprocessors ahead of Olin's. APP1 implements a set
of flow control structures (if/then/else, loops of various types) that
automate the generation of most labels internal to functions. APP2 takes
care of inserting all of Olin's DBANKIF macros ahead of symbol references
that need them. It also smashes the indentation to match Olin's coding
standard. As long as you don't create files with an ".app" extension,
these won't get in your way.
Thanks Dave for posting the Makefile. I also agree with Jan-Eric
that maybe I should stick to the batch file approach and using
Windows XP. Anyway more important is the content of the macros.
>Date: Fri, 3 Dec 2004 09:32:54 +0100 (CET)
>From: "Jan-Erik Soderholm" <RemoveMEjan-erik.soderholmspam_OUTKILLspamtelia.com>
>Hi.
>You can very well build your project without using any
>make tool at all. Most normal projects builds rather quick
>on a reasonable new PC anyway...
>
>Jan-Erik.
>Date: Thu, 02 Dec 2004 20:09:03 -0800
>From: Dave Tweed <RemoveMEpicTakeThisOuTspamdtweed.com>
>
>The attached Makefile will build Olin's HAL project.
>I posted this a long time ago, but here it is again.
>
>It should be pretty obvious how to modify it for other projects -- it's
>mainly a matter of replacing the HAL_OBJS lines with the right list of
>object files, fixing up the names in the link step, and creating all the
>correct source dependencies at the bottom.
d1o265.telia.com>
