NetBurner Community Forum

Hi, I am trying to configure J2[35] as a high z input using the following snippet of code: J2[35].function(PINJ2_35_GPIO); //External Fermat Reset J2[35].hiz(); This pin in our design is left floating but after using a scope and multimeter it looks like it either drives or is being pulled high. I've...

Hi, My system requires the ability to switch the I2C SDA pin to an output GPIO when a certain condition is met? How can one gracefully disable the peripheral and switch the pin? Beside changing the pin from PINJ2_39_SDA to a regular GPIO and setting the I2CR = 0x00, is there anything else that would...

Hi, I want to characterize some functionality of the GPIO and to make this a little easier I wanted to temporarily short two pins together without soldering them. I noticed the 26 empty locations of the JT1 header on the MOD5234 and wanted to add some headers jumper different pints together. It does...

Ah ok I misunderstood, I though it was an internal pull up. My only reason for asking this is because in the final design, the interrupt will be always be connected to signal from a device with a push-pull output stage and I wanted to avoid any bus contention but we can work around that and it shoul...

Confirmed. The pin does appear to be pulled hard to Vcc. Is there anyway to disable this pull up? Thanks!

Hi, I'm implementing a falling edge triggered irq on J2[45] of the MOD5234 board using the included pin_irq.cpp file included in the nburn directory. Specifically, I've implemented BOOL SetPinIrq( int pin, int polarity, void ( *func )( void ) ) pointing to a function that simply keeps a count of the...

Great! Thanks for the help guys

Hi, I'm currently developing some firmware for the MOD5234 using the NBEclipse environment. I'm using Git as my main source/version control. The repository currently tracks all files since at the time of creation I was not sure what files were valid to be ignored. But this has become pretty cumberso...

I would stay with your simple test app, in release mode only. Lowest number of variables. If I understand your description: 1. If you load the factory app you can see the device in with the find utitilites 2. You compile your test app, then successfully download to the device 3. When the device reb...

No break points to speak of.

The issue is definitely present in debug mode and when just running the application, some old build is programmed to the board. Seems like the regular run file isn't being regenerated after builds. I've cleaned and rebuilt the project as well with no success.