Search results

  1. ToastBucket

    Assembly restart. Software work. And maybe our next SoC?

    I don’t have a lot of information in this regard, but I do have a little A15: Fetches 3 instructions per cycle Dispatches up to 6 instructions for execution Handles branch prediction, though the algorithm used is not shared (details are pretty limited but you may be able to find something)...
  2. ToastBucket

    Assembly restart. Software work. And maybe our next SoC?

    TDP is a generalized metric of average performance and efficiency. Looking at it very generally, a higher TDP indicates higher performance and lower efficiency (and of course a lower TDP indicates the opposite). However this is only a reasonable comparison between two very similar chips, as it...
  3. ToastBucket

    Assembly restart. Software work. And maybe our next SoC?

    OMAP5 product brief: https://www.ti.com/pdfs/wtbu/SWCT010.pdf The OMAP5430 offers a smaller 14x14 mm2 package with PoP LPDDR2 memory, while the OMAP5432 offers a 17x17 mm2 package with non-PoP DDR3 memory Yep this is correct. But the major heat source is those 4xA76's. So its a huge extra...
  4. ToastBucket

    Assembly restart. Software work. And maybe our next SoC?

    At that price point, I think the RK3568 is looking really good. When considering the dimensions as well, I think the RK3588 is just too big. Not exactly sure which package you went with for the OMAP5, but looks like it'd be 17mm, which means the RK3568 is worth trying, RK3588 is probably much...
  5. ToastBucket

    Assembly restart. Software work. And maybe our next SoC?

    For comparison, here's the RK3588. We would probably need to run Android for best performance here (OpenGL/Vulkan libraries will be better optimized, as well as the emulators themselves). Of course heat is going to be a challenge with either SOC.
  6. ToastBucket

    Assembly restart. Software work. And maybe our next SoC?

    I've done some work on the RK3399 and I wouldn't really recommend it. It's just ok and is not the easiest chip to work with due to the shortcuts made by RK in the base BSP. Granted I was working on an Android device using it. I can definitely say that once you can grab their interest, they are...
  7. ToastBucket

    The Future of Pyra's CPU

    Ahh I see what you mean. The SOC board connectors themselves have height differences. Itd be interesting to see if we can create any space by using a longer connector that is compatible
  8. ToastBucket

    The Future of Pyra's CPU

    A blob free life is a hard life to live.
  9. ToastBucket

    The Future of Pyra's CPU

    Ya it’s usually common practice to directly replicate the RAM part selection and layout from the EVK, but still a small mistake can cause lots of problems. At least we have OCRAM to help us debug
  10. ToastBucket

    The Future of Pyra's CPU

    Ah interesting. Probably rare because it was really difficult and expensive. What seems a bit more successful is SIPs like those made by Octavo. The packages are definitely a bit larger, but its very convenient having RAM and PMIC and everything all buttoned up for you so long as you're happy...
  11. ToastBucket

    The Future of Pyra's CPU

    RAM attached on top? You mean just the RAM on the SOC board? The height and width dimensions would affect that. RAM is pretty much never attached on top? I've seen one weird custom spin of the i.MX6 which did this, but it was hugely problematic and eventually dropped due to yield issues.
  12. ToastBucket

    The Future of Pyra's CPU

    That's good news. The RK3399 looks like an excellent candidate under the hood. Btw, the 1.51mm height includes the BGA connections. See pages 28-29 of the datasheet for package measurements.
  13. ToastBucket

    The Future of Pyra's CPU

    A while back I picked up a Maaxboard which is based on the 8M to try and evaluate general performance of the part in comparison to the OMAP5. Unfortunately the support out the door for this board is pretty bad. Since there's a good amount of work required to test this out I dropped it for now...
  14. ToastBucket

    The Future of Pyra's CPU

    Thats a bit of a bummer. With the iMX8M nano our battery life will likely go through the roof, but we'll likely be sacrificing a good amount of raw power limiting tasks like web browsing. Its hard to do a full comparison because there's a lot of differences between these core families, but a...
  15. ToastBucket

    The Future of Pyra's CPU

    4xA72s is a huge upgrade in terms of raw power from the A15s but yes they are more power hungry than other cores. It could be comparable to A15s though, they are very inefficient cores. A72s are actually part of the big cluster in a big.LITTLE combo, there’s just no LITTLE on the BCM2711. I...
  16. ToastBucket

    Pyra Mods

    Be careful with this one. Make sure the batteries you choose will be ok with the charger circuitry. I think this should be fine since they’re Li-ion but I would double check the datasheet (bq24297). You’ll also need to modify the device tree to support the New capacity so the charger circuitry...
  17. ToastBucket

    A case of polls!

    This happened to me :( huge bummer
  18. ToastBucket

    Low Latency Kernel ?

    We need more devs:p
  19. ToastBucket

    General issues regarding F2FS rootfs partition

    I mean you can always take the thing apart yourself when you get one and take a look inside :) you might be able to hack something up. But no PCIe that I’m aware of is hooked up. Could be wrong though.
  20. ToastBucket

    General issues regarding F2FS rootfs partition

    Like Grench said, it will be a long long time before the eMMC dies. Everyone seems to be very worried about this. Somewhat reasonable, but I think people are overly fearful of this. In my opinion, the performance benefits of the eMMC over the uSD (which are quite significant) outweigh the...
Back
Top