Search Results

Search results 1-20 of 52.

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Hello CodeRunner, Using multiple interfaces really is as easy as adding another interface in your IP_X_Config() . One thing to take care of: Please make sure that you add the real port Ethernet driver first as most of these drivers expect to be interface #0 for internal simplicity and performance. Drivers like IP over USB however are written in a way so they can be added at any position in such a combination. Best regards, Oliver

  • Hello SilentDawn, I will try to answer this in short as you are basically not under a valid SUA due to not having a license and you only use (parts of) an eval package. 1. IP_Init() which is the main init function to call will call IP_X_Config() and afterwards the init callback of the driver. 2. The driver calls the BSP_IP_API callbacks (that have been hooked in during IP_X_Config()) as necessary to handle non-generic hardware layer stuff like installing an ISR callback from inside the driver. 3…

  • Hello SIlentDawn, Thank you for your notes regarding the wrong case include names. This has already been addressed in newer evaluation packages and is scheduled to be fixed whenever we release an updated evaluation package for this hardware in the future. Regarding the library error that you experience: This is a project for Rowley Crossworks and references a Kinetis simulator library that is simply not available with Embedded Studio. Overall this project does not seem like the best choice as a …

  • Hello SilentDawn, If you have a look at e.g. the IP_MQTT_CLIENT_Publisher.c sample, you should be able to identify the structure IP_MQTT_CLIENT_TRANSPORT_API and the actual socket abstraction in various static functions above it (between file header and the IP_MQTT_CLIENT_TRANSPORT_API location). The Quote: “static const IP_MQTT_CLIENT_TRANSPORT_API _IP_Api = { _Connect, _Disconnect, _Recv, _Send }; ” _IP_Api is then assigned via IP_MQTT_CLIENT_Init() to a context. From here on only the context …

  • Hello Alex, Sorry for the late reply. I have discussed your request internally. You are right that we do not use the fast block programming mode (without self erase of the block). If I remember correctly this was an intentional decision. As simple as STM8 devices might be, there are different variations about how the program memory behaves and in early tests we had way less problems with the standard block programming (with auto-erase) than with the fast mode. In addition to this we experienced …

  • Hello Jim, Sorry about the late reply. I assume that your first combination of samples did not work has to do with the following line: Quote from CodeRunner: “OS_SetPriority(OS_GetTaskID(), 255); ” This is basically only meant to set the current task to its highest prio possible if there is nothing more to do aka only short checking of the link state and maybe LED toggling. Without seeing the complete setup I assume you ended up with some kind of prio deadlock in your application setup. Basicall…

  • Hello Alexander, Sorry about the late response. The problem here is actually the real programming speed that the Flash gets programmed internally. In the beginning of the product we experimented with other features like RAM code programming where we put a multiple of a page into the RAM and then program it via a code that we also download into RAM for direct CPU->Flash programming. However this turned out to still result in very slow programming speeds with almost no advantage over the actual SW…

  • Answered via mail. Summary: Flasher stand-alone power supply in the project settings was enabled by the customer by accident. Additional information: Quote: “The project settings override the Flasher default state (that is what you set with power on/off perm). Please also note that if power is enabled from your project, the power gets enabled during the stand-alone operation and is disabled at the end of the stand-alone operation. The Flasher does not return to its default state. ” Best regards,…

  • Dear glaukos, Let me start with a very short explanation on how non-blocking sockets work, although this should be generic to all network stacks that offer some kind of BSD socket interface API. Sockets follow a basic principle of three return values only: - > 0: Number of bytes processed. - = 0: Connection closed or no error in calls that make no sense to return a number of bytes such as bind(). - < 0: Error. More details about this error state can be retrieved using getsockopt(hSock, 0, SO_ERR…

  • Hi Pete, Different file types might be treated different by your browser. It might happen that your browser's cache will serve an old CSS file instead of the new one. Are you sure the new one gets delivered by the server or if it is even requested ? Typically modern browser come with some sort of debug features where you can monitor the network events and how long they take. This is often called "developer tools" in the browser and will help you testing for these kind of problems. Best regards, …

  • Hello Pete, Sorry about the late reply. Quote from dynapb: “1. Do I need to "compile" the .htm, .css, .gif files with m.bat/cc.bat/Bin2C.exe? ” Only if you want to use the ReadOnly filesystem by placing your files in your flash. Quote from dynapb: “2. Can I just put the files in a "File System" and use them like a typical website? ” Using a real filesystem is possible as well and in this case you can simply place your files onto your FS media. The emWeb shipment comes with FS glue layers for Win…

  • Hi Pratheesh, Sorry for the delay but I think you already received my vacation note from one of my colleagues. Quote from Pratheesh P: “1. Does BTL_ImageCreator can combine 4 Images including EMLOAD?” The purpose of the BTL Image Creator is to prepare ONE firmware image for direct flashing instead of updating via emLoad. Optional it can be combined with emLoad itself for direct flashing. It is not meant to combine multiple firmware images. Of course you can first combine multiple firmware images…

  • Answered via support mail. Closed due to custom hardware specific configuration.

  • Hi Pratheesh, The PrepareFW tool is designed to read in a single file only. However this file may contain several memory regions with gaps. These gaps will be preserved as gaps if they are big enough (more than a couple of bytes) to avoid an unnecessary region overhead in the output. To combine multiple files you can easily use J-Flash from our J-Link Software and Documentation Pack, available for download from here: segger.com/downloads/jlink/ J-Flash can even be be used via command line argume…

  • Hi Pratheesh, Good to hear you were able to figure out what is going on. However, if I understand your solution correct it has a potential risk to end up in another problem. You wrote that you are no longer disabling interrupts (done in BTL_NET_ExitCPU()) before jumping into the firmware. emLoad will switch the vector table to the firmware before executing the jump. If for any reason an interrupt fires between the switch of the vector table (VTOR register) and initial setup of interrupts in the …

  • Hello Pratheesh, I had a look over the CMSIS files included in your project. The following is a list of things that will most likely not work in this setup: 1. You are using a minimal CMSIS SystemInit(): The one in use resets registers for CPU clock configuration regardless of their previous state. You could try to use the CMSIS files shipped with emLoad/embOS as running on a reset setup with the minimum base clock is most likely not what you want anyhow. As I have already written in my last mai…

  • Hi Stefan, But please be aware that SO_RCVBUF only means a limitation of the socket buffer in bytes. This will not prevent you from wasting packet buffers for like 1 byte UDP packets. We will check what we can do about an optional, additional NumPackets limitation for UDP/RAW Rx socket buffers. Stay tuned. Regards, Oliver

  • Dear Stefan,Quote from stefan.waldschmidt: “Could my observation be correct? Can this situation occur?” The short answer here is yes, if the PacketBuffer configuration is insufficient and/or does not match the configuration of the SocketBuffer. By default an UDP SocketBuffer is configured to hold up to 2048 bytes. This can be changed for a socket via setsockopt(SO_RCVBUF). The PacketBuffer configuration of the system should be prepared to handle the situation where the complete size of the Socke…

  • Quote from MATA82: “Yes erase chip is enable. So you're saying that the serial erasing procedure is much faster?” Yes, serial (standalone mode) is always faster than PC mode as it eliminates latencies caused by PC interfaces. Delay from Ethernet is typically lower than USB but standalone operation eliminates it completely. For programming we are already using an optimized procedure by loading bigger chunks to the Flasher that will then be processed like in standalone mode. For erasing the device…

  • Dear MATA82, I assume you have enabled Erase Chip in the production settings, is this correct ? Either way in standalone mode the Flasher can operate much more efficient as he does not have to wait for instructions from the PC. Especially an erase operation for the whole chip can take way more time as the sectors are erased one by one and the sectors/blocks of STM8 devices are very small (64 or 128 bytes). If you do not rely on an empty Flash for your application (expecting 0x00 in the flash whi…