flok
Reaction score
0

Latest activity Postings About

    • flok
      flok replied to the thread SD card corruptions.
      True. Ok it now works. On the Teensy4.1 and when verified on the pc. Thanks for your help.
    • flok
      flok replied to the thread SD card corruptions.
      Oh indeed. I now do not get an error. It's not clear to me though which one to use when arm_dcache_delete or arm_dcache_flush. For write I do now both before the file.write() call. I verified the contents of the sd card on my pc but the data is...
    • flok
      flok replied to the thread SD card corruptions.
      Hi JMarsh! Something like? arm_dcache_delete(data, n_bytes_to_read); size_t bytes_read = file.read(data, n_bytes_to_read); rc = bytes_read == n_bytes_to_read; if (rc) {...
    • flok
      Hi, I think I'm doing something wrong but I can't figure out what. The situation is that if I write a block of data to the SD-card and then read it back again, then parts of the written data are missing (some parts are then all 0x00) or it is...
    • flok
      flok replied to the thread iSCSI target.
      Yes, it is in the ESP32 microcontrollers folder. I have to rename that folder (will do so now but it may take a bit). I just renamed that folder from ESP32 to microcontrollers. It uses platformio. So pio run -t upload -e Teensy4_1 should...
    • flok
      flok replied to the thread iSCSI target.
      In this graph you see that iTEENSY quickly goes to 10MB/s, maxing out the Ethernet connection: Thus in theory the Teensy4.1 should be able to reach higher speeds even (if it would have Gb Ethernet).
      • 1709384769882.png
    • flok
      flok replied to the thread iSCSI target.
      Hi, Remote storage is usually a NAS or a SAN. A NAS is where you access data by files. p:\\diary.pdf or so. A SAN is accessed via a protocol like iSCSI, FC and others. A client ("initiator") then requests blocks of data like how it does from a...
      • 1709384238780.jpeg
    • flok
      flok posted the thread iSCSI target in Blog Project Submission.
      I always wanted to write an iSCSI target since I worked (professionally) with IBM iSCSI boxes (iSCSI is used to communicated with SAN systems. It allows blocks of data to be transferred to client systems.). I finally got around doing so. There...
      • 1709370155496.png
    • flok
      flok replied to the thread backtrace.
      Paul, thank you for the clarification! I got it all working now (mostly; but enough for my proof of concept).
    • flok
      Hi, How can I get a backtrace? Not neccessarily in a debugger, just via serial. Addresses are enough (I can get line numbers and such via e.g. ~/.platformio/packages/toolchain-gccarmnoneeabi-teensy/bin/arm-none-eabi-addr2line -e...
    • flok
      F.w.i.w.: after, say, 50 flashes it becomes unreliable. Like not always booting up. Only reflashing it helps then, sometimes after 2 or 3 times.
    • flok
      I did in my second post (the reply to myself). Looks like something still goes wrong (when doing tcp/udp interleaved), but I'm investigating it.
    • flok
      I fixed it: the compile problems with QNEthernet were due to conflicts with a board-package version. Yes, with QNEthernet the networking problems are gone. Nice! Please close the ticket :) (now the SD card does not seem to work?!)
    • flok
      That's problematic: .pio/libdeps/Teensy4_1/QNEthernet/src/lwipopts.h:208:36: error: expected identifier before numeric constant 208 | #define TCP_MSS 1460 /* 536 */ | ^~~~
    • flok
      Hmmm, in some cases it still doesn't work.
    • flok
      Found something: this problem does not happen (with the little example program in my 2nd post) in teensyduino 1.158.0, only in 1.159.0.
    • flok
      I shrunk the program a bit and it still shows the problem: #include <NativeEthernet.h> #include <NativeEthernetUdp.h> EthernetServer *server { nullptr }; EthernetUDP *handle { nullptr }; uint8_t mac[6] { 0x12, 0x34, 0x56, 0x78, 0x9a...
    • flok
      Hi, Thanks. It did change the behaviour indeed. It looks like it now works altough one time I did not even pressed reset and it already started flashing (or maybe the reset button is very sensitive and I did not notice that I was touching it...
    • flok
      Hi, I'm trying to port an application of mine to the teensy 4.1. Compiling and linking is no problem but networking is problematic (for me at least :) ). I have two sockets: one listens on a UDP port one listens on a TCP port What I then do...
    • flok
      Hi, Received my Teensy 4.1 in the mail today. Looks good! Flashing fails every 1st time though (2nd succeeds, 3d fails, 4th succeeds etc) Configuring upload protocol... AVAILABLE: jlink, teensy-cli, teensy-gui CURRENT: upload_protocol =...
    • flok
      I eventually got it to work: there was a stray fopen left in my code somewhere.
    • flok
      Were you be able to fix this problem? I'm seeing it as well: /home/folkert/.platformio/packages/toolchain-gccarmnoneeabi-teensy/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld...
    • flok
      flok replied to the thread c++17 std::optional.
      (for google) add: platform_packages = platformio/framework-arduinoteensy@^1.159.0 build_flags = -std=gnu++17 build_unflags = -std=gnu++14 to platformio.ini.
    • flok
      flok replied to the thread c++17 std::optional.
      Oh wait, it is already available yet as I'm using platformio not available directly to me. I'll see if I can change that.
    • flok
      Hi, I'm trying to port an application of my from the ESP32/RP2040 to the Teensy 4.1 platform. It uses std:: optional but that does not seem to be supported? Any plans to do so? Thanks!
  • Loading…
  • Loading…
Back
Top