Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. NXP struggle update: I feel immortal today

NXP struggle update: I feel immortal today

Scheduled Pinned Locked Moved The Lounge
designvisual-studiocomgraphicshardware
4 Posts 4 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H Offline
    H Offline
    honey the codewitch
    wrote on last edited by
    #1

    I broke through. Yesterday I was up against a huge number of unknowns in terms of developing against this new hardware I'm using - a 1GHz Cortex M monster by NXP. - I didn't know how to use any SPI buses aside from the first one (there are 6). - I didn't know their build system. - I didn't know their HAL packages. - Their IDE was failing on me - I didn't know how to develop raw against the chip on my board instead of developing against the board itself. (All that and I wasn't 100% sure my board even functioned well enough for the tests since it arrived with components visibly missing and the stock firmware unable to run due to a faulty or missing component) I had to tell my client that I likely wouldn't be ready with benchmark figures by next Tuesday's meeting. Today, I solved it all, and I got my figures (and they're reasonable, which means we can actually use this hardware) I'm stunned that I got through it all. I'm not really that clever, just persistent, so I figured it would take awhile. I should probably code something before this superpower wears off. :~

    Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix

    Richard Andrew x64R P 2 Replies Last reply
    0
    • H honey the codewitch

      I broke through. Yesterday I was up against a huge number of unknowns in terms of developing against this new hardware I'm using - a 1GHz Cortex M monster by NXP. - I didn't know how to use any SPI buses aside from the first one (there are 6). - I didn't know their build system. - I didn't know their HAL packages. - Their IDE was failing on me - I didn't know how to develop raw against the chip on my board instead of developing against the board itself. (All that and I wasn't 100% sure my board even functioned well enough for the tests since it arrived with components visibly missing and the stock firmware unable to run due to a faulty or missing component) I had to tell my client that I likely wouldn't be ready with benchmark figures by next Tuesday's meeting. Today, I solved it all, and I got my figures (and they're reasonable, which means we can actually use this hardware) I'm stunned that I got through it all. I'm not really that clever, just persistent, so I figured it would take awhile. I should probably code something before this superpower wears off. :~

      Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix

      Richard Andrew x64R Offline
      Richard Andrew x64R Offline
      Richard Andrew x64
      wrote on last edited by
      #2

      Congrats! What will you do for your next trick? :-D

      The difficult we do right away... ...the impossible takes slightly longer.

      N 1 Reply Last reply
      0
      • Richard Andrew x64R Richard Andrew x64

        Congrats! What will you do for your next trick? :-D

        The difficult we do right away... ...the impossible takes slightly longer.

        N Offline
        N Offline
        Nelek
        wrote on last edited by
        #3

        Richard Andrew x64 wrote:

        What will you do for your next trick?

        I think not even the witch knows it in advance :rolleyes: :-D

        M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

        1 Reply Last reply
        0
        • H honey the codewitch

          I broke through. Yesterday I was up against a huge number of unknowns in terms of developing against this new hardware I'm using - a 1GHz Cortex M monster by NXP. - I didn't know how to use any SPI buses aside from the first one (there are 6). - I didn't know their build system. - I didn't know their HAL packages. - Their IDE was failing on me - I didn't know how to develop raw against the chip on my board instead of developing against the board itself. (All that and I wasn't 100% sure my board even functioned well enough for the tests since it arrived with components visibly missing and the stock firmware unable to run due to a faulty or missing component) I had to tell my client that I likely wouldn't be ready with benchmark figures by next Tuesday's meeting. Today, I solved it all, and I got my figures (and they're reasonable, which means we can actually use this hardware) I'm stunned that I got through it all. I'm not really that clever, just persistent, so I figured it would take awhile. I should probably code something before this superpower wears off. :~

          Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix

          P Offline
          P Offline
          Phil J Pearson
          wrote on last edited by
          #4

          honey the codewitch wrote:

          I should probably code something before this superpower wears off.

          No!! Step back from the keyboard. Never code while you have a superpower. Been there, done that. When you come back to it a few arbitrary-time-periods later, you won't understand it. You'll spend ages trying to figure out why it works perfectly and then more time rewriting it so that you'll understand it next time (which you probably won't).

          Phil


          The opinions expressed in this post are not necessarily those of the author, especially if you find them impolite, inaccurate or inflammatory.

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups