Search results

Without DWARF/unwind tables, you're going to have a very hard time creating a backtrace, I'm afraid. You could back up the entirety of the stack and send that over on next reboot for analysis on the PC, but other than that, it's mostly wishful thinking going to keep investigating though, may...

You have the stack pointer and you can use the compiler option -funwind-tables -- this was the working plan. More than that requires a disassembler and dwarf info on elf.

We're just drooling at the prospects of the new Teensy haha, I'm super excited

I know, but I may expand on it when I get time (need to do some experiments on the ITM/ETM)

I have other priorities ATM but if I get some time this weekend I'll see about hammering away at generating dump files. A shame about the USB issue, though. Would be a massive help when rapid fire debugging (but I ended up just moving my teensy closer so pushing the button isn't that bad haha)

Hmm, buydisplay has a preassembled 1963 7".. I may give that a go, thanks for the suggestion. As my application is just a GUI, I don't really see it pertinent to have super fast update rates, but I'm always down to play with more displays (esp. since my cat mostly murdered mine)

There are a lot of moving parts which is why I agree it could be suspect. However: I've had quite a bit of success using SPI with several of the fault handlers (and even USB serial, even though I'm still unable to engage the USB program mode -- weird!) -- my display I .. display .. the error...

The code isn't horrible, it's just clearly pumped out quickly. I've turned it (their RA8875 lib) into a gruesome abomination of what theirs originally is, and then shoved an abstraction layer on top of that so I can use it on my PC (because my cats are assholes and shattered the resistive touch...

It's still a WIP -- I'm actively working on hammering away at it (my ARM asm knowledge is very slim, but I'm working on it!) but will definitely share once it gets in a more usable state. If I do want to use SD card to shove dump files, I'll have to make sure it's not in an inconsistent state...

Hi! I'm not sure if this is the right question to ask, but I currently implement a hard fault function to do a (WIP) crash trace dump, but after the dump I'd like to re-enable USB interrupts so I can re-flash the Teensy during my unending while loop. Another interesting, but less important...

I ended up having to create a driver to use my PC to render for testing because the RA was just so slow lmao (and it doesn't even support scissor rects? ew!) While not unlikely, I feel the requirements to get NXP on your side do enough to prevent clones; and the level of support provided by...

Some people just like eating more than cinnamon toast crunch :rolleyes: The dual core nature of the new MCU means we can rather easily offload software emulation of various protocols like UART/SPI/etc on the other (GPIO) pins if we need to, without adversely affecting other code. The more heavy...

It would be interesting to see a Teensy variant with more pins exposed (e.g. a teensy 5.2?) The NXP chips have so many capabilities limited by the smol formfactor of the Teensy. While good for 99% of usecases, I'd for instance accept a larger teensy (a chonky?) to get access to, for instance...

Whoa... The GPU2D capability looks like loads of fun to play with

Update since I can't edit my post(?) -- The WINC1500 WiFi module I'm using seems to behave despite the RA8875 not being tristate and there has been no issues after running both in tandem for ~an hour (just outputting WiFi scan results to screen) -- so if anyone else runs into this issue with...

Aw man, double checked the solder joint and I'm not shorting it, that would've been a huge relief. At this point I might just order another teensy, would prefer that to using an additional chip to babysit the rude display driver -- esp. since I intend on shoving some of the SOIC8 PSRAM to house...

I think my pin may just be foobarred :( So I don't have to wait for a replacement to ship, does anyone have a suggestion on "soft coding" a circumvention for the non tristate SPI board I'm interacting with? For instance, could I do something really dumb like swap my MISO1 pin back and forth...

I'm aware -- SPI not functioning is how I figured out this was happening in the first place I'm using the blink sketch here -- look how wonky the signal is. For reference, here's blink on pin 14:

Hi! I'm seriously enjoying my 4.1, but I've run into a bit of a conundrum. My pin 13 is very noisy and only goes up a couple millivolts (confirmed via scope) when I set it to HIGH. This is particularly problematic because SCK is on this pin and I need to use both SPIs (as I'm reserving SPI1 to a...