hello i am really a newbie(an electronics student) and i have to use at85c51snd3b but i dont know how to set uvision for it. there is no proper target in device database. But uVision tells it supports.
actually i am supposed to built an mp3 player. i'll really appreciate any help for it. (at85c51snd3b1 does not include an built in mp3 decoder and i have to implement it by my own way. but again i have no idea about mp3 decoding(but i know about DSPs and microcontroller, and i am good at programming)
thx a lot for any help
they might be prepared to view this as an "investment" and lend (or even give) you (or your college) the kit.
or you may be fortunate enough that they will not and you will not use Atmel, but a decent brand instead.
Erik
Erik,
At the risk of being flamed for being off-topic, why are you so anti-Atmel...?
Just curious... Dave.
why are you so anti-Atmel...? Just curious...
When Atmel came out with the first flash based '51s I found a silicon bug in a revision somewhere around rev 'g'. I told my then management that we could not use the Atmel chip and they wrote Atmel "when is this going to be fixed?". Atmel wrote back "there is no such bug, we can not take bug reports from imcompetent (my emphasis) people into consideration". You can imagine what such a statement from a big company did to my relationship with management (I was told to do the impossible; use the chip since there was no bug). Now, lo and behold, somewhere around revison 's' what i had reported appeared in the errata.
Now you know.
PS I have been forced to work with Atmel since (inhereited projects) and the sluggishness in 'admitting bugs' is still there. Maybe now that the Perlegos'es are gone that will change, we have to see. The trade press commenting on the power shift has mentioned that, according to Perlegos Atmel could do no wrong.
We have had "non-existing" bugs with Microchip chips.
We have had a large number of "non-existing" bugs in Wavecom GSM modules. They have a number of times claimed that the bugs where in our software. The only strange thing is of course than when they 6 months later releases new firmware, the errors suddenly disappears in our software, while new problems arrives. The new problems often disappears in yet newer firmware, just to be replaced by a new set of strange - but not existing! - bugs.
Borland lost most of it's market share when they got controlled by ties and suddenly stopped admitting to bugs.
Quite a lot of companies have shown a bad track record. There is nothing else that is as effective when it comes to getting their customers to migrating to alternative products/solutions.
To this day, my only irritation with Atmel is their extremely poor simulation of their AVR chips. Getting a 3GHz Prescott to manage about 1MHz simulation speed of a trivial AVR core without almost any peripherial support can only be seen as a tour-de-force of bad programming.
my absolute rejection of all things Atmel is not based solely on their 'delay' in issuing errata. While that is bad enough, my total ire is due to them (in the pre e-mail days) writing my management "there is no such bug, we can not take bug reports from imcompetent (my emphasis) people into consideration". That they are idiots is one thing, but calling me one just because they [do not want to take the time to check]/[will not admit] a bug is a quite different story.
"my total ire is due to them (in the pre e-mail days) writing my management 'there is no such bug, we can not take bug reports from imcompetent (my emphasis) people into consideration'"
I wonder if that was written by a Francophone, and they didn't actually mean it as badly as a native English speaker would take it...?
It is quite obvious that some Atmel documents are written in French, and the translation into English leaves a lot to be desired.
I wonder if that was written by a Francophone
could be, after all Chauvin who gave name to Chauvinism, was French.
Chauvinism: 2. Prejudiced belief in the superiority of one's own gender, group, or kind: