If you were Registered and logged in, you could reply and use other advanced thread options
|
Posted by Joe on January 12, 2007, 12:26 am
I am right now using bascom, or, should I say, trying to, which, even
on this forum was touted by some to be the best. Well, I've been
struggling with it for almost 3 days now, and it just won't send the
program to my chip. Of course bascom does not support the trial
version. There is one lady who has been trying to help me, but to no
avail. I have tried everything I can think of. I can compile the code
ok, but then I cannot send it to the chip thru bascom. An error message
shows up and stays on screen for all of about 60 milliseconds. I know
because in order to read it, I had to use my dv camera and record the
screen, and then play it back frame by frame. The error message just
says to see the log above. Trouble is, there is no log above. So far I
have only been able to send it using avrstudio. It uses the hex file,
but even that's not so reliable. It kind of works when it feels like
it.
So I seek the advice of those who have probably been there and done
that.
TIA,
Joe
|
|
Posted by Don McKenzie on January 12, 2007, 1:50 am
Joe wrote:
> I am right now using bascom, or, should I say, trying to, which, even
> on this forum was touted by some to be the best. Well, I've been
> struggling with it for almost 3 days now, and it just won't send the
> program to my chip. Of course bascom does not support the trial
> version. There is one lady who has been trying to help me, but to no
> avail. I have tried everything I can think of. I can compile the code
> ok, but then I cannot send it to the chip thru bascom. An error message
> shows up and stays on screen for all of about 60 milliseconds. I know
> because in order to read it, I had to use my dv camera and record the
> screen, and then play it back frame by frame. The error message just
> says to see the log above. Trouble is, there is no log above. So far I
> have only been able to send it using avrstudio. It uses the hex file,
> but even that's not so reliable. It kind of works when it feels like
> it.
>
> So I seek the advice of those who have probably been there and done
> that.
>
> TIA,
> Joe
your subject:
Re: Can anyone recommend a basic compiler for atmel avr that actually works?
sounds like you are saying the compiler doesn't work, when it is the
download that isn't working. This may well be your fault, or a
programmer hardware fault, and not Bascom. As you say, it is unreliable
using avrstudio.
Suggest you check your hardware settings, and get advise from the user
group, before you condemn this product. They will give you support, even
on the demo software.
Don...
--
Don McKenzie
E-Mail Contact Page: http://www.dontronics.com/e-mail.html
Crystal clear, super bright OLED LCD (128x128) for your microcontroller.
Simple serial RX/TX interface. Many memory sizes.
http://www.dontronics-shop.com/product.php?productid 460
|
|
Posted by Joe on January 12, 2007, 9:01 am
Don McKenzie wrote:
> Joe wrote:
> > I am right now using bascom, or, should I say, trying to, which, even
> > on this forum was touted by some to be the best. Well, I've been
> > struggling with it for almost 3 days now, and it just won't send the
> > program to my chip. Of course bascom does not support the trial
> > version. There is one lady who has been trying to help me, but to no
> > avail. I have tried everything I can think of. I can compile the code
> > ok, but then I cannot send it to the chip thru bascom. An error message
> > shows up and stays on screen for all of about 60 milliseconds. I know
> > because in order to read it, I had to use my dv camera and record the
> > screen, and then play it back frame by frame. The error message just
> > says to see the log above. Trouble is, there is no log above. So far I
> > have only been able to send it using avrstudio. It uses the hex file,
> > but even that's not so reliable. It kind of works when it feels like
> > it.
> > So I seek the advice of those who have probably been there and done
> > that.
> > TIA,
> > Joe
> your subject:
> Re: Can anyone recommend a basic compiler for atmel avr that actually works?
> sounds like you are saying the compiler doesn't work, when it is the
> download that isn't working. This may well be your fault, or a
> programmer hardware fault, and not Bascom. As you say, it is unreliable
> using avrstudio.
> Suggest you check your hardware settings, and get advise from the user
> group, before you condemn this product. They will give you support, even
> on the demo software.
> Don...
> --
> Don McKenzie
> E-Mail Contact Page: http://www.dontronics.com/e-mail.html
> Crystal clear, super bright OLED LCD (128x128) for your microcontroller.
> Simple serial RX/TX interface. Many memory sizes.
> http://www.dontronics-shop.com/product.php?productid 460
Hello Don,
Yes, that is exactly what I am saying, and your response is
predictable. Just like the girl on the forum told me. You may want to
have a look at the forum, under the topic. "need help with first
program". There was only one person who tried to help, she's from
Denmark, you probably know her or have seen her posts.
It's 2 pages long of going back and forth between her and I over the
past 3 days and nights.. Photos of different screens, and finally I was
able to record, using a dvcam, the error message I get when i try to
"send the program to chip" . I couldn't screen print it because it only
stays up there for 60 to 70 milliseconds and disappears. It doesn't
tell me much anyway. We finally came to the conclusion that what is in
my programmer is indeed a mega8515, not a AT90S8515.
To date, no one else has been willing to help. I talked with an app
engineer from Atmel yesterday, and he said not to worry, that as long
as avrstudio4 can program the hex code that bascom generates, then what
is the problem? OK, well he is right, but the key words there are "as
long as avrstudio can program using the hex code".
Just going out on a limb here, but I am assuming you are a reseller of
bascom?
Joe
|
|
Posted by Huey on January 12, 2007, 10:18 am
nuisancewildlife@earthlink.net says...
> > Joe wrote:
> > > I am right now using bascom, or, should I say, trying to, which, even
> > > on this forum was touted by some to be the best. Well, I've been
> > > struggling with it for almost 3 days now, and it just won't send the
> > > program to my chip.
Taking the first step is often a difficult one. It requires everything
to go right from beginning to end. Even the typical simple "first
blink" type of program can be a bit tough to get to happen. There are
often to many variables in the process that can affect the outcome.
Somewhere in your chain of processes is a broken or weak link. It can
often be frustrating to find that link.
Simplified, you create object/hex code from source, then transfer that
to the microcontroller. In this case the source is BASIC that BASCOM
converts to a hex file. The source could just as easily be C or assembly
with other tools.
The STK500 is the hardware used to transfer the hex file to the chip.
That could also be other hardware - the AVRISP, or even a homebrew
parallel port programmer.
It appears that the weak link is the interaction of BASCOM and the
STK500. Sounds very much like BASCOM is able to compile your source to a
hex file. And also that you have had at least some success with using
AVR Studio to transfer the hex file to the processor.
BASCOM's main job is to compile BASIC source to a hex. Sounds like that
is happening. BASCOM needs to know what chip to compile for, so that it
can manage the memory locations for flash and RAM for the specific
target. (And use the correct ports/peripherals.) There are settings in
the compiler and in the source code that can define the target chip and
the clock frequency for the target. Those need to be correct to
correctly generate the hex file.
BASCOM doesn't talk directly to the STK500, but provides a way to
connect to the STK500 using the program (AVR Studio) that is installed
with the STK500. When things are set up right, it is very convenient
that a button push in the BASCOM IDE will get the compile and program
your target chip. Sometimes getting this convenient feature set up
correctly can be troublesome. (That might be were your trouble lies.)
If you set aside this for a moment, you might be able to confirm at
least that you have generated a hex file correctly by using AVR Studio
and the STK500 to program your chip from the hex file. If you can
confirm that some steps of your process work correctly, then it will be
easier to identify the weak link and get all of the steps to work in
concert.
Give BASCOM a chance. It is a very good program. The problems that you
are having appear to be in getting BASCOM linked to the programmer that
you purchased (the STK500). This is, by-the-way, the same thing that I
went through with BASCOM and the AVRISP that I use. BASCOM was
generating the hex file and I could use AVR Studio to program the chip.
Once I knew that both ends of the process worked correctly, then I was
able to resolve getting the two major steps correctly linked.
|
|
Posted by Joe on January 12, 2007, 12:17 pm
Huey wrote:
> nuisancewildlife@earthlink.net says...
> > > Joe wrote:
> > > > I am right now using bascom, or, should I say, trying to, which, even
> > > > on this forum was touted by some to be the best. Well, I've been
> > > > struggling with it for almost 3 days now, and it just won't send the
> > > > program to my chip.
> Taking the first step is often a difficult one. It requires everything
> to go right from beginning to end. Even the typical simple "first
> blink" type of program can be a bit tough to get to happen. There are
> often to many variables in the process that can affect the outcome.
> Somewhere in your chain of processes is a broken or weak link. It can
> often be frustrating to find that link.
> Simplified, you create object/hex code from source, then transfer that
> to the microcontroller. In this case the source is BASIC that BASCOM
> converts to a hex file. The source could just as easily be C or assembly
> with other tools.
> The STK500 is the hardware used to transfer the hex file to the chip.
> That could also be other hardware - the AVRISP, or even a homebrew
> parallel port programmer.
> It appears that the weak link is the interaction of BASCOM and the
> STK500. Sounds very much like BASCOM is able to compile your source to a
> hex file. And also that you have had at least some success with using
> AVR Studio to transfer the hex file to the processor.
> BASCOM's main job is to compile BASIC source to a hex. Sounds like that
> is happening. BASCOM needs to know what chip to compile for, so that it
> can manage the memory locations for flash and RAM for the specific
> target. (And use the correct ports/peripherals.) There are settings in
> the compiler and in the source code that can define the target chip and
> the clock frequency for the target. Those need to be correct to
> correctly generate the hex file.
> BASCOM doesn't talk directly to the STK500, but provides a way to
> connect to the STK500 using the program (AVR Studio) that is installed
> with the STK500. When things are set up right, it is very convenient
> that a button push in the BASCOM IDE will get the compile and program
> your target chip. Sometimes getting this convenient feature set up
> correctly can be troublesome. (That might be were your trouble lies.)
> If you set aside this for a moment, you might be able to confirm at
> least that you have generated a hex file correctly by using AVR Studio
> and the STK500 to program your chip from the hex file. If you can
> confirm that some steps of your process work correctly, then it will be
> easier to identify the weak link and get all of the steps to work in
> concert.
> Give BASCOM a chance. It is a very good program. The problems that you
> are having appear to be in getting BASCOM linked to the programmer that
> you purchased (the STK500). This is, by-the-way, the same thing that I
> went through with BASCOM and the AVRISP that I use. BASCOM was
> generating the hex file and I could use AVR Studio to program the chip.
> Once I knew that both ends of the process worked correctly, then I was
> able to resolve getting the two major steps correctly linked.
Hello Huey,
Thank you very much for the reply. You are quite correct. Bascom is
compiling the program. BTW, this program was supplied to me by one of
the users on the mse forum, and has been confirmed to work.
When I discovered that bascom could not send the program to the chip, I
just went into avrstudio to see if maybe something was different, or
wrong, and it was quite by accident that I ended up with avrstudio
asking for a hex file, so I supplied it with the hex file that had been
generated by bascom, and with one click, the chip was erased, and
programmed with the new file. Presto! Like magic.
So I am still fumbling, although not so much in the dark anymore. I
shall continue this pursuit now based upon your words of encouragement,
and I will find the problem of why bascom is not able to send the
program to the chip.
Now a question for you: Is the program supposed to be in a certain
location for bascom to find it, because I put it into my "robotics
folder", and had to specify the location to avrstudio, so what I am
wondering is that maybe bascom doesn't know where to look?
Thank you for the info,
Joe
|
Page 1 of 4 1 2 3 > last >>
Related Posts
Latest Posts
|
|
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map
> on this forum was touted by some to be the best. Well, I've been
> struggling with it for almost 3 days now, and it just won't send the
> program to my chip. Of course bascom does not support the trial
> version. There is one lady who has been trying to help me, but to no
> avail. I have tried everything I can think of. I can compile the code
> ok, but then I cannot send it to the chip thru bascom. An error message
> shows up and stays on screen for all of about 60 milliseconds. I know
> because in order to read it, I had to use my dv camera and record the
> screen, and then play it back frame by frame. The error message just
> says to see the log above. Trouble is, there is no log above. So far I
> have only been able to send it using avrstudio. It uses the hex file,
> but even that's not so reliable. It kind of works when it feels like
> it.
>
> So I seek the advice of those who have probably been there and done
> that.
>
> TIA,
> Joe