Search results

this is harrrrrd I can't seem to write into the USBHS_USBINTR_NAKE bit, it's almost as if it's a reserved bit, but the reference manual doesn't indicate so, USBHS_USBINTR_NAKE is bit 16 in the reference manual I have posted the problem to the Freescale/NXP forum...

I've examined every single debug message that can come out of the entire library. None of it is helpful to a developer. I'm sure this is intentional as the debug messages are supposed to help the user. I did find "if (stat & USBHS_USBSTS_NAKI) println(" NAK");" and it disabled under a #if 0...

R_DS(on) is at most 154 milliohms, sounds like 0.04659 watts of heat with 550mA The low end of the current limit is 0.65A so thermal shutdown should happen at 155C, that's pretty hot. The derating curve in the datasheet only tops out at T_J of 125C I'm looking at a SOT-23-3 MOSFET datasheet...

I'm writing some code to control a mirrorless camera using PTP (picture transfer protocol), writing a class to inherit from USBDriver. I own a Beagle USB analyzer and from what I see, the camera gives an annoying amount of NAKs after any command transfer (libusb would timeout/io-error on any...

I used a Teensy 3.2, taking full advantage of the CAN peripheral and the FlexCAN library, as well as FastLED and several others. More detailed in my own blog, including more of my notes on UX, and all of my open source files (code, CAD, etc)...

Absolutely true But in my experience if you wrote something from scratch, and added functionality little by little, and tested each addition, your final project will still work. If you finished your project and then enabled garbage collection after, things can break, and it becomes a pain to...

In the Teensy 3 code currently, specifically file mk20dx128.c , there is a line SCB_VTOR = 0; // use vector table in flash this is causing problems when it is used with a bootloader I wrote, because "user app" has its own vector table, my bootloader sets SCB_VTOR to the new location before...

thanks xxxajk I have already started to write my own malloc that handles this, it is basically the same idea you have, my code will ensure that the boundary of my struct meets the boundary of the two SRAM regions I will test it and report back (edit: maybe a simpler solution is to just check...

by the way volatile uint32_t* foo; foo = (volatile uint32_t*)(0x1FFFFFFF - 4); *foo = 0x12345678; works without crashing I plan on resolving the issue by making sure that the end of my struct to meet the end of the SRAM region. It will be a very dirty hack but it's a temporary fix. A...

Maybe, but my "freeRam" diagnostic reports about 8000 bytes between stack bottom and heap top.

I am not aware if that is a feature of GCC I am getting these faults for other operations on various members of the structure. What if my code makes GCC forget it's a struct member? There are many situations that could cause my scenario.

On Teensy 3, there is 16 KB of RAM available total, according to the reference manual, the SRAM is split into SRAM_L and SRAM_U The Teensy 3 linker script simply states that RAM (rwx) : ORIGIN = 0x1FFFE000, LENGTH = 16K I have a bit of code that will malloc a piece of memory, by sheer...

Hi, I'm the guy behind this http://eleccelerator.com/usbxlater-preview/ Anyways, I used a STM32F chip in that hardware because I needed two USB ports for the PS3 However, for the PS4, I only need one USB OTG port. Kinetis chips are cheaper than STM chips so I'm debating to save a few dollars...