MultipleMonomials
Member

OK! I added the MAC address code and confirmed that it's reading the OTP MAC addr correctly. I also figured out what's up with the TLS socket example; once this patch is merged it should work correctly. Another one...

Ooh yeah good point about the MAC address! I'll add that to the pull request shortly. Unfortunately, Mbed OS currently does not support USB host mode in any shape or form. It's a bummer, I know, I don't know why...

Yeah, that's what I get too, and I do see it on the 1050 EVK as well. I can try to debug through it in the next couple days, it looks like it's dying in the ASN.1 parse function?

Exciting news! I have spent the last couple days working on a Teensy 4.1 port, including Ethernet support, and have just about got it running! I am able to send and receive packets on the network, and I can use the...

As an update, I went ahead and merged the latest USB fix into mbed-ce master branch, so you won't need to use any special branches anymore. The next thing I want to do is add upload method support, so that the build...

AHA! I just made a major step forward. Using this branch, I can now get the USB device to enumerate. It still cannot print text, but it's a lot closer to working. Turns out that I goofed when I fixed the ncache...

I checked in the debugger on my dev kit. The line handle->deviceCallback(handle, kUSB_DeviceEventBusReset, NULL); goes to usb_status_t USBPhy_DeviceCallback(usb_device_handle handle, uint32_t event, void...

Paul, thank you for the debugging help! Much appreciated. I did a bit of checking and figured out how to put together the setup that you need. First, change mbed_app.json to disable USB and enable the UART console: ...

wwatson, I think you might have had an issue with checking out the latest master branch. I can see that that line is fixed in the GitHub repo here. Try this (from the mbed-ce-hello-world directory): cd mbed-os...

Create a pull request compiling all the fixes found so far: https://github.com/mbed-ce/mbed-os/pull/130

You downloaded it from here right? If so I'm not really sure what's up, the only thing I can think of is that it's a false detection and you'll need to either add an exclusion for that file or get a different/older...

Does it say something like "Windows SmartScreen has protected your PC"? If so, there's a hidden button on that dialog that allows you to proceed. I think you have to click More Info first.

Update: Also added in teensy model identifier to the linker script. Also, I did some more checking, and you guys are right. The CMake code I posted for setting the optimization level doesn't work -- it turns out...

Aha! I solved the mystery with the core clock. Turns out someone changed the generated clock_config.c file, so the comments were no longer accurate. The punch line is, they didn't even do it properly -- after the...

Being really honest, I'm not sure I'll be able to make much headway on the USB issue anytime soon. While I have experience with many MIMXRT peripherals and with Ethernet (will try and port the Teensy 4.1 ETH PHY driver...

In CMake, optimization is controlled by the CMAKE_BUILD_TYPE variable. There are three types available in Mbed OS: Debug, which builds with no optimizations and enables debug symbols Develop, which enables -Os...

This is an awesome guide! Want me to give you edit access to the Mbed wiki so you can improve the instructions there?

> Needed thew space before the '=' operator. Oops, pushed a fix! Odd, that worked with whatever version of ld I have... > The Ninja build command is not automatically being run. I have to run it separately. Is...

Aha! I was able to reproduce and diagnose a crash when activating BufferedSerial on pins D1 and D0 using my MIMXRT1050 dev kit. It turns out that, for some reason, the original Mbed port didn't define interrupt...

Ah, I figured out the mystery of the ncache initialization crashing. Turns out that you were right, that section specifically was still being put into the SEMC due to some weird linker script hijinks. I combined it...

> tried PwmOut test on D12 -- i get the "mbed dead" blink pattern Oh I know what's causing that, looks like the original Mbed port for the dev board didn't include a mapping for that pin, because it isn't accessible...

What I would like to try is, edit mbed_app.json in the hello world project and change it to: { "target_overrides": { "*": { "platform.stdio-baud-rate": 115200, ...

Awesome work, guys! Great to hear that it is booting, maybe a JTAG won't be needed after all. I completely forgot that Mbed's fault handler also has an 8 blink pattern <facepalm>. > TARGET_MIMXRT1050 code assuming...

The only thing I did notice is, the Teensy bootdata.c file has this: const uint32_t ImageVectorTable = { 0x432000D1, // header (uint32_t)&Reset_Handler,// program entry 0, // reserved 0, // dcd...

Hmm, I took a look through the boot stuff in the hex file (IVT + flash config + vector table) and I didn't see anything that screamed out at me as being wrong. Addresses for various things match the map file and are in...

Thanks a ton for giving it a shot, guys! Home from work now so I will check this out. > Seems like the mbed T4.0 code is derived from the 1050 Yep, that's correct. It's based on Mbed's 105x HAL layer, plus boot...