| General > General Technical Chat |
| I feel.... Dirty... |
| << < (4/8) > >> |
| VK3DRB:
Just remember how Microchip (Atmel) abandoned you during Chipageddon - no parts and no communications. ESP32's were still available from several vendors right thought. Despite any technical performance and IDE differences, what the point if you cannot get the parts? |
| MarkS:
--- Quote from: tooki on April 29, 2023, 01:43:22 pm --- --- Quote from: MarkS on April 29, 2023, 12:26:19 am --- --- Quote from: daqq on April 28, 2023, 12:22:12 pm ---If you are using an ESP32 and feel clean you should see someone about that ;) --- End quote --- :-DD Fair enough! They are more powerful than the average Atmel chip found on an Arduino, but they do leave a lot to be desired. --- End quote --- Other than more GPIOs, what are they lacking? (For typical applications.) --- End quote --- Yeah, I thought about my comment after posting. To be fair, my gripe is with CircuitPyton and not the chip. I need to get back into C/C++ programming and stop with these cutesy, "Let's make everything easier for the developer!!!!111oneone" languages/libraries. My laziness has made my life a living hell. Doing it right (C/C++) would have taken slightly longer to code, but I'd have a better grasp on why it either did or didn't work. --- Quote from: tooki on April 29, 2023, 01:43:22 pm ---Gotcha, makes sense. But would it not be better, for the long term, to choose a 3.3V capable memory chip instead? There are 3.3V-compatible versions of your chip, the SST39LF040 and SST39VF040. If you're using I2C now as a workaround, could you use an SPI Flash chip or I2C EEPROM? Then you wouldn't need to worry about large amounts of GPIOs. ESP32's have several SPI buses, so you could likely dedicate one to Flash if need be. (Or get an ESP32 model with more Flash memory to begin with?) --- End quote --- I'll be using this chip as a ROM in a retro MC68000-based project. Right now all I'm doing is trying to verify the legitimacy of the chips I bought through secondary sources. I need 30 GPIO, so I'm using two MCP23017 IO expanders to interface with the chip. Between the I2c bus, level shifters and expanders, I cannot get the timing correct. I do have several MCP23S017s, and should have used them instead of the I2c version in the first place :palm: |O, but at this point I'm burned out with this "simple" project and am just going to cut out the middleman and directly connect to the chip. |
| daqq:
--- Quote from: tooki on April 29, 2023, 01:43:22 pm --- --- Quote from: MarkS on April 29, 2023, 12:26:19 am --- --- Quote from: daqq on April 28, 2023, 12:22:12 pm ---If you are using an ESP32 and feel clean you should see someone about that ;) --- End quote --- :-DD Fair enough! They are more powerful than the average Atmel chip found on an Arduino, but they do leave a lot to be desired. --- End quote --- Other than more GPIOs, what are they lacking? (For typical applications.) --- End quote --- I know that there are areas where they are a great fit, consumer IoT in particular, but overall they leave a sour taste in my mouth. We actually use them in a bunch of stuff. The stuff I don't like: - ADC parameters, linearity and overall ADC WTF - requires a lot of support components, external memory in particular is annoying - documentation is not exactly awesome - some pinout choices that I don't like This is not to say that I won't use one where it's appropriate, but unless something really requires BLE/wifi then no way. |
| tooki:
--- Quote from: MarkS on April 29, 2023, 02:32:51 pm ---Yeah, I thought about my comment after posting. To be fair, my gripe is with CircuitPyton and not the chip. I need to get back into C/C++ programming and stop with these cutesy, "Let's make everything easier for the developer!!!!111oneone" languages/libraries. My laziness has made my life a living hell. Doing it right (C/C++) would have taken slightly longer to code, but I'd have a better grasp on why it either did or didn't work. --- End quote --- Ah! I've never tried CircuitPython, I've only ever done C/C++. --- Quote from: MarkS on April 29, 2023, 02:32:51 pm ---I'll be using this chip as a ROM in a retro MC68000-based project. Right now all I'm doing is trying to verify the legitimacy of the chips I bought through secondary sources. I need 30 GPIO, so I'm using two MCP23017 IO expanders to interface with the chip. Between the I2c bus, level shifters and expanders, I cannot get the timing correct. I do have several MCP23S017s, and should have used them instead of the I2c version in the first place :palm: |O, but at this point I'm burned out with this "simple" project and am just going to cut out the middleman and directly connect to the chip. --- End quote --- Oh I gotcha, so you're really just using the MCU as a programmer? |
| tooki:
--- Quote from: daqq on April 29, 2023, 03:04:34 pm ---I know that there are areas where they are a great fit, consumer IoT in particular, but overall they leave a sour taste in my mouth. We actually use them in a bunch of stuff. The stuff I don't like: - ADC parameters, linearity and overall ADC WTF - requires a lot of support components, external memory in particular is annoying - documentation is not exactly awesome - some pinout choices that I don't like --- End quote --- Yeah, the ADC is kinda lame! But as for external support components -- well, isn't that precisely why they sell finished modules you can just solder in? That saves all the trouble of external components, antenna design, etc. that you have to do when using the bare SoCs. Also, they do have some SoC models with integrated memory, like the ESP32-PICO-V3-02, and the ESP-S2F, -S3F, and -C3F series. Several of those, as well as the upcoming ESP32-S3-PICO-1 series, have both PSRAM and Flash integrated into the SoC. |
| Navigation |
| Message Index |
| Next page |
| Previous page |