NXP is really starting to expand my vocabulary
-
Now I'm going to have to start swearing in Mexican Spanish as well just to fully cover this foolery. First my $200 eval board arrives missing pieces. I'm pretty sure it was NXP and not Mouser's doing, because google turned up at least one other person with the issue, and they ordered straight from NXP. Worse, there was a bad or missing component on the board (i can't see it) that prevents the demo from running. I have a meeting coming up for which I need to have run some benchmarks on this chip and so I can't return the board yet - I don't have time to get a replacement. Luckily mouser is giving me 90 days to return it, but I think I'll just take the credit on my account instead of getting a new board. Then, heaven help me the MCUXspresso IDE just hangs installing the SDK. I posted on /r/embedded about it. The solution i was given was "When I ran into that I closed it waited a day, ran it again and it worked". I waited a day. Ran it again. It worked. *headdesk*. Internet something something. *grumble* X| :rolleyes: In the meantime I find another way to do it using VS Code, which I prefer, but I run their standalone installer, and the damned thing reboots me system with no warning. For a bit I thought it was malware and I had been faked out, but no, just a very ill behaved installer, with inadequate documentation (for NXP users out there, this isn't the main installer, but a standalone one they give you for getting this running w/ VS Code instead of MCUxpresso IDE) Then there's flashing. There are several different boot loaders, and you have to figure out which one works with your hardware configuration, and sometimes you can choose from more than one, but you have to flash a new boot loader to make the new one work, and different ones have different capabilities. Confusing! Fortunately, although I found this out after much hair pulling, the VS Code extension will detect and choose the appropriate one for your equipment, and preflashed bootloader. Finally, I get a project going. I need to figure out how to get the SPI busses working with DMA, and thank god for the examples, because google turns up almost nothing. It's amazing anyone can find their way around NXP's APIs because they aren't well documented that I can find. They do a good job of documenting the hardware and registers, but anything higher level than that, like their wrappers, aside from the examples (which fortunately, are pretty extensive) I don't see much. But now they've disabled 5 of the 6 SPI buses in code and I can't figure ou
-
Now I'm going to have to start swearing in Mexican Spanish as well just to fully cover this foolery. First my $200 eval board arrives missing pieces. I'm pretty sure it was NXP and not Mouser's doing, because google turned up at least one other person with the issue, and they ordered straight from NXP. Worse, there was a bad or missing component on the board (i can't see it) that prevents the demo from running. I have a meeting coming up for which I need to have run some benchmarks on this chip and so I can't return the board yet - I don't have time to get a replacement. Luckily mouser is giving me 90 days to return it, but I think I'll just take the credit on my account instead of getting a new board. Then, heaven help me the MCUXspresso IDE just hangs installing the SDK. I posted on /r/embedded about it. The solution i was given was "When I ran into that I closed it waited a day, ran it again and it worked". I waited a day. Ran it again. It worked. *headdesk*. Internet something something. *grumble* X| :rolleyes: In the meantime I find another way to do it using VS Code, which I prefer, but I run their standalone installer, and the damned thing reboots me system with no warning. For a bit I thought it was malware and I had been faked out, but no, just a very ill behaved installer, with inadequate documentation (for NXP users out there, this isn't the main installer, but a standalone one they give you for getting this running w/ VS Code instead of MCUxpresso IDE) Then there's flashing. There are several different boot loaders, and you have to figure out which one works with your hardware configuration, and sometimes you can choose from more than one, but you have to flash a new boot loader to make the new one work, and different ones have different capabilities. Confusing! Fortunately, although I found this out after much hair pulling, the VS Code extension will detect and choose the appropriate one for your equipment, and preflashed bootloader. Finally, I get a project going. I need to figure out how to get the SPI busses working with DMA, and thank god for the examples, because google turns up almost nothing. It's amazing anyone can find their way around NXP's APIs because they aren't well documented that I can find. They do a good job of documenting the hardware and registers, but anything higher level than that, like their wrappers, aside from the examples (which fortunately, are pretty extensive) I don't see much. But now they've disabled 5 of the 6 SPI buses in code and I can't figure ou
This always happens, when you start with a new hardware. After 10 years it goes better.
honey the codewitch wrote:
I waited a day. Ran it again. It worked.
Exactly like Qt Creator installer.
