Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

RE: Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

haakonsh — Mon, 16 Apr 2018 08:35:59 GMT

I do not think this is related to SES in any way, but rather the commands, responses, etc that is used to interface with the display.

RE: Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

MikeLemon — Sat, 14 Apr 2018 20:31:14 GMT

Arghh this is something I wrote to preform a little test for the display the same algorithm(display commands) work with the arduino thing but not in SES.

This is simply going no where, please close that case.

RE: Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

haakonsh — Fri, 13 Apr 2018 08:49:03 GMT

If you can read the device ID you are in communication with the display. I suggest you either find another driver for the display(that does not target arduino), or write one from scratch yourself.

RE: Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

MikeLemon — Fri, 06 Apr 2018 13:19:48 GMT

Ahmmm quite a delay almost became irrelevent....

Anyways that is the datasheet if that somehow helps but I'm afraid that's something in the code that I miss.

Anyway not sure here's the link to the OLED driver datasheet:

cdn-shop.adafruit.com/.../SSD1306.pdf

RE: Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

haakonsh — Fri, 06 Apr 2018 07:50:05 GMT

Do you have a datasheet for the OLED screen?

RE: Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

MikeLemon — Sun, 25 Mar 2018 05:36:29 GMT

[quote userid="13562" url="~/f/nordic-q-a/32469/migrating-from-arduino-to-nrf32-platform-using-the-ses-ide-and-twi-interface-oled-display/125487"]Can you read the shields device ID?[/quote]

Yes Of course like I said at the beginning I just don't understand why that function doesn't work physically according to that code. the arduino POC algorithm that got converted to SES with the nrf52832 just doesn't work as expected or is it just me not ready understanding that TWI read function properly.

RE: Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

haakonsh — Thu, 22 Mar 2018 09:42:02 GMT

I'm not suggesting that you actually start by checking every transistor, etc. What you need to do is to start slow. Can you read the shields device ID?

RE: Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

MikeLemon — Mon, 19 Mar 2018 15:38:18 GMT

Hello haakonsh,

I've went through the Nordic docs countless times and make sure the specific components work with with that particular setup(Used arduino nrf52832 extensions and ST LINK V2 to program it even on my custom PBCs) the tutorial are not helpful either just explaining about how to setup the more complex stuff which I'm sure are easy when you get to that stage after you understand the basics and common idiology of this platform,

Now going through every transistor that makes the IC and programming useful is not that useful either sins it simpley take way too many years I don't have.

So for now I'm just striking that particular problem to be able to move more easily hopefully and integrate the rest and then add the more complex BLE,low power part of the software.

RE: Migrating from arduino to NRF32 platform Using the SES IDE and TWI interface OLED display

haakonsh — Mon, 19 Mar 2018 10:37:36 GMT

Hey Mike,

I'm glad that you've taken the BIG step into embedded engineering. I know It seems incredibly daunting right now as the transition from the Arduino world into the embedded realm is the developer/maker/tinkerer/students equivalent to the Ice-bucket challenge.

As you have probably noticed nothings seems to "work out of the box" and minuscule changes to seemingly unrelated code have disastrous consequences. Fear not, we've all been there (still am to some degree). The learning curve is steep, there is so much to learn, and you'll not know where to start. I will try to give you some advice and directions.

First off, you cannot focus entirely on you end goal, you need to take baby steps otherwise you will lose motivation and quit.

You need to realize that a "simple" task of transmitting a single byte over I2C/TWI is a very complex operation dependent on a lot of variables, and if you make any assumptions along the way you will regret it later. My job is to chase down the root causes of our customers problems and I know from painful experience how an assumption like: "BTW there's no way it's a wiring problem since I'm using it with a shield and checked that the MCU can read it with the TWI_scanner example", will ruin your week/month. You need to know that the physical signal is transmitted and received correctly. To do that you need a digital analyzer. We've got a Saleae Logic Pro at every desk because we use them frequently, they are easy to use and they're good enough debug data lines at <10MHz.

There ARE defective products, no matter how simple or complex. Any product will have some small percentage(Parts Per Million) of units that have some sort of defect. It might be our MCU, or the OLED screen, or a power transistor on the OLED board, or a capacitor, or an inductor, or a connector, etc.

Once you have verified that something works as intended you can take a few moments and appreciate the fact that you are one step closer to your end goal, then start on the next step. Testing and verification is a critical component of engineering and it automatically breaks down tasks into small components.

Secondly, you will have to read, a lot. The nRF52832 Product Specification, the OLED display's datasheet, the nRF5 SDK v14.2.0 documentation and its API Reference, and code. Lots and lots of code. You will have to learn embedded C programming to understand what is going on inside the libraries and drivers.

You will find our tutorials at https://devzone.nordicsemi.com/tutorials. I suggest you delay doing anything BLE related until you have a better grasp of how to use our SDK documentation, libraries and examples.

Thirdly, you need to use some form of a Version Control system. I suggest Git for programming. This way you can modify your code and not have to worry about ruining your code base or project files. The Segger Embedded Studio project file itself is stored in clear-text which means that it can be processed and saved in Git.

Now to answer your questions:

SDK14.2/examples/peripheral/TWI or TWIM. Use this example as a base to begin with. You might want to switch to another base as you gain more knowledge.
Version control, version control, version control. Commit often, write good commit messages, use branches.

Cheers,

Håkon.