ESP8266 Community Forum

- Fri Sep 12, 2014 5:24 pm #504

Please let me know if you spot errors.

sure, watch pin16 and 24, these are GPIOs on current chip revision.

Reset was as well not properly connected.

Pin 8 is Deep-Sleep Wakeup or GPIO, so yes it can be connected together with reset,
but i think if there is sleep mode one could use it without doing reset every time.

Edit: file deleted, see my post below

Last edited by tinhead on Sat Sep 13, 2014 6:17 am, edited 2 times in total.

I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.

- Fri Sep 12, 2014 5:38 pm #505

symbol/footprint organization is very sane - there're cases of same chip packed in different packages, making a symbol tied to a package is proprietary short-sightedness which is ok for a software which tries to put limits on users, but would be ridiculous for open-source software - even if it was done like that, someone would soon submit patch to untie unrelated entities to allow their free recombination and free ideas flow.

Having an additional mandatory step for some unusual case is stupid in the first place.

The best symbol/footprint/3D model/Spice model organization is in Altium

Cannot say much about back annotation - there's something in kicad for it, I didn't have to use it for typical hobby projects, it's not inconvenient to switch to schematics and add a resistor or connector there, and see it pop up in layout.

It is just one example: there are so many missing features in there that I cannot use it even for my hobby stuff. But maybe I am biased because I am used to Protel99, Altium, Orcad, PCAD, etc.

Anyway, it's all excuses, that just show which line of thought vendors use when stick to closed proprietary stuff - they're just too lazy and inert to try something else, even if there're good reasons too. And that's well mirrored by community, who wants be given open stuff, but doesn't really want to nudge to eat own dogfood and try and learn open stuff consistently.

It is not a vendor or community problem: it is a natural human behavior to stick to what everybody says is good for you and act as sheeps. It is just so comfortable not to have to think

Hacking on such new cute module as ESP8266 is a nice chance to give it a try - to find open replacement for IDA, to work on hackable compiler, or at least start hacking on GCC whatever it is currently (not very hackable), try Kicad for schematics/layout, etc. YMMV.

GCC is far from the right tool when it comes to MCUs: on Cortex ARM for example, not being able to remove unused data or functions in an object file without putting each one into its own individual section is insane and a major cause of bloat. I am not talking about rocket science compiler optimization here: just good sense

Ok, back to the original subject, feel free to convert it to KiCad if you want, but I don't have time nor interest to do it myself, I am just to busy right now.

- Sat Sep 13, 2014 6:24 am #508 attached Eagle schematic and pcb. I can not post reference design files as they under NDA, but i created almost 1:1 copy in Eagle. It is very small, 4layer PCB. Note, the schematic is copy of what Squonk made, i only changed some components to match layout. I'm not Eagle user, so there is some inconsistency between schematic and pcb, so someone with Eagle experience should fix them and repost proper files.

You do not have the required permissions to view the files attached to this post.

I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.

- Sat Sep 13, 2014 7:44 am #509 You need to plan for a shield if you want FCC modular approval.

Where I get my modules