#avr Logs

Nov 24 2019

09:27 AM [1]MrMobius is now known as MrMobius
12:00 PM gonzo11: Hello, I remember that in a 8086 you had the Code Segment where you had access to the processor instructions of your code. that's not available in an avr, right?
12:01 PM gonzo11: i.e. can an avr dump through serial a section of the code?
12:09 PM cehteh: its havard architecture data and isntructions reside in different address spaces, but there are operations to read (and write, if permitted) the flash
01:18 PM gonzo11: ok thanks
02:23 PM guanche: hey guy, does microchip use to reward error reporting on their datasheets? :D I wouldn't mind receiving a couple of atmegas for all I've found
02:24 PM guanche: I've been literally pulling my hairs out with a hvpp, and it wasn't until I changed BS2 pin to mimic the fuse-bit doctor that it worked, while in the datasheet a completely different pin is mentioned for such function
02:24 PM guanche: that, among many other errors found regarding the "documentation" of the whole thing
02:25 PM mouseghost: huh
02:34 PM cehteh: yeah datasheets have sometimes stupid bugs, its good when you know a few more and can use your imagination whats really going on
02:36 PM guanche: I guess I'd have ended up posting on avrfreaks and somebody would have come up with the solution
02:37 PM guanche: I seem to infer the protocol was closed, and then they opted for relasing it at some point, what I don't understand it's why so many errors on the datasheet regarding this
02:38 PM guanche: I mean, how it comes nobody ever wrote atmel to let them know so they could correct them
02:39 PM cehteh: microship revised some datasheets and added some errors .. sometimes oblivious copy paste errors
02:40 PM cehteh: i guess the let some low paied workers do that job
02:42 PM guanche: well, at least for this, one would need to build a high-voltage programmer following the datasheets, or either have a deep understanding so it's not needed, but seeing avrfreaks is such a friendly comunity, apparenty in close touch with atmel (back in the days), these big mistakes seem strange
02:49 PM guanche: as I don't have copies of original atmel's datasheets I cannot know who introduced the errors
02:49 PM guanche: I wouldn't be suprised if microchip deliberately introduced them to sell more programmers
02:54 PM vmt: the solution is to stop using avr-crap
02:56 PM mouseghost: https://www.maximintegrated.com/en/design/technical-documents/app-notes/1/187.html
02:56 PM mouseghost: i dont quite understand that thing lol
02:59 PM mouseghost: ahmm, so logical 1 is pulled low?
03:00 PM mouseghost: is that with anything electronics related, btw?
03:00 PM mouseghost: well, anyways, isnt that 'search algorithm' a bit illogical?
03:01 PM mouseghost: if 2 devices on a bus are 0 and 1 in their roms, isnt and always 0 in that case?
03:01 PM mouseghost: either complement or not?
03:02 PM guanche: to use stm32 vmt?
03:13 PM mouseghost: stm32 looks hard
06:00 PM rue_mohr: no
06:00 PM rue_mohr: its just a bunch of extra code to turn things on you want to use